Win 2003 x64 crashes (network related?)

grandthief · Jun 23, 2012

Hi to all!
I have a problem with Win 2003 x64 SP2 guest os on proxmox 2.1
My server configuration is Intel S5000PSL, 2xIntel Xeon e5345 CPU's, 16 Gb DDR2 Ram
I have two VM's with win 2003 x64 - one with the virtio network adapter (also i used intel e1000 - nothing changed - it continues to fall in BSOD), and second with rtl8139
The first VM just fall in BSOD sometimes - interval between BSOD's changes from 3 hours to 6 days.WinDbg says, that BSOD caused by afd.sys driver.
The second VM periodically lose the connection to the outside - i can't disable/enable the adapter and need to reboot vm.
output of pveversion for additional information:

Code:

root@vsvr:~# pveversion -v
pve-manager: 2.1-1 (pve-manager/2.1/f9b0f63a)
running kernel: 2.6.32-12-pve
proxmox-ve-2.6.32: 2.1-68
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-12-pve: 2.6.32-68
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.8-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.7-2
pve-cluster: 1.0-26
qemu-server: 2.0-39
pve-firmware: 1.0-16
libpve-common-perl: 1.0-27
libpve-access-control: 1.0-21
libpve-storage-perl: 2.0-18
vncterm: 1.0-2
vzctl: 3.0.30-2pve5
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-9
ksm-control-daemon: 1.1-1

What i can do to stop this?

tom · Jun 23, 2012

looks not Proxmox VE related (just google for BSOD caused by afd.sys driver)

but you can try latest virtio anyways. http://people.redhat.com/vrozenfe/build-29/

grandthief · Jun 23, 2012

tom said:
looks not Proxmox VE related (just google for BSOD caused by afd.sys driver)

but you can try latest virtio anyways. http://people.redhat.com/vrozenfe/build-29/

Ok, but how you can explain that with e1000 adapter i already have random crashes, which i can't see on virtualbox or VMWare?
*P.S. - Also install drivers, which you specify.'ll write a post if anything goes wrong.

tom · Jun 24, 2012

BSOD can have multiple reasons. as I wrote, looks not virtio related.

grandthief · Jun 27, 2012

And another BSOD - caused by afd.sys again.
And, also, it's not problem of virtio drivers - it's problem of proxmox or one of components, which it uses - because of on Virtualbox with these drivers nothing happen - system have uptime > 3 days.
*Any variants to solve problem or i need to go to Virtualbox o sm else?

spirit · Jun 27, 2012

Hi,I'm using a lot of win2003 sp2 x64 vms without any problem.

can you post your vm config ?

cat /etc/pve/qemu-server/XXX.conf

spirit · Jun 27, 2012

you can also try to tune the network registry

http://www.linux-kvm.org/page/WindowsGuestDrivers/kvmnet/registry

Marvin · Jun 27, 2012

have you looked at this?
http://support.microsoft.com/kb/958752

grandthief · Jun 27, 2012

spirit said:
Hi,I'm using a lot of win2003 sp2 x64 vms without any problem.
can you post your vm config ?

cat /etc/pve/qemu-server/XXX.conf

Code:

root@vsvr:~# cat /etc/pve/qemu-server/100.conf
bootdisk: virtio0
cores: 4
ide0: local:100/disk1.raw,cache=writeback
ide1: local:100/disk2.raw,cache=writeback
ide2: none,media=cdrom
memory: 8192
name: rfserv
net0: virtio=00:50:70:02:32:76,bridge=vmbr0
onboot: 1
ostype: wxp
sockets: 1
root@vsvr:~#

spirit said:
you can also try to tune the network registry

http://www.linux-kvm.org/page/WindowsGuestDrivers/kvmnet/registry

*I used those values, and have crashes, now i uses another values (smaller than those) and OS still crashing

Marvin said:
have you looked at this?
http://support.microsoft.com/kb/958752

*Yes, i already install this update and i had a BSOD after 2 hours of work after installation of this update
*

Marvin · Jun 27, 2012

spirit · Jun 28, 2012

did you have tried with writethrough or direcysync for you disk ?

grandthief · Jul 1, 2012

spirit said:
did you have tried with writethrough or direcysync for you disk ?

No, I used only no cache and writeback configuration.Also, i don't think that source of these problem lies in disk-cache params because of it's don't crashes on rtl8169 (on this card network fail to works after 1-2 days)

Yan Vugenfirer · Sep 11, 2012

Hello,

I found this thread by accident while googling. I am the maintainer of virtio-win drivers (https://github.com/YanVugenfirer/kvm-guest-drivers-windows) and although those crashes doesn't seams to be virtio-win specific would like to look at the dump files anyway.

Can you send me minidumps to yvugenfi (at) redhat.com or the location of full zipped dumps ?

Thanks,
Yan Vugenfirer.

spirit · Sep 12, 2012

Yan Vugenfirer said:
Hello,

I found this thread by accident while googling. I am the maintainer of virtio-win drivers (https://github.com/YanVugenfirer/kvm-guest-drivers-windows) and although those crashes doesn't seams to be virtio-win specific would like to look at the dump files anyway.

Can you send me minidumps to yvugenfi (at) redhat.com or the location of full zipped dumps ?

Thanks,
Yan Vugenfirer.

Thank Yan, you can also keep me in touch (aderumier@odiso.com), if we need to add some patches to proxmox.

demon · Dec 10, 2012

Yan Vugenfirer said:
Hello,

I found this thread by accident while googling. I am the maintainer of virtio-win drivers (https://github.com/YanVugenfirer/kvm-guest-drivers-windows) and although those crashes doesn't seams to be virtio-win specific would like to look at the dump files anyway.

Can you send me minidumps to yvugenfi (at) redhat.com or the location of full zipped dumps ?

Thanks,
Yan Vugenfirer.

Hello, Yan.

Can you look at my dumps please? I have the simular problem (unexpected randomly BSOD). And every time varios errors in minidumps.
If you agree i'l send it to your mail

___________ Strings from dump win2k3
.............
SYSTEM_SERVICE_EXCEPTION (3b)
.....................

DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: SemSvc.exe (here in some cases PROCESS_NAME: chrome.exe ...and so on)
CURRENT_IRQL: 0
.................
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: afd!AfdIssueDeviceControl+1a8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: afd
IMAGE_NAME: afd.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 45d69cac
STACK_COMMAND: .cxr 0xfffffadf26333f60 ; kb
FAILURE_BUCKET_ID: X64_0x3B_afd!AfdIssueDeviceControl+1a8
BUCKET_ID: X64_0x3B_afd!AfdIssueDeviceControl+1a8

___________ Strings from dump win2k8
....................
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
....................
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT_SERVER
BUGCHECK_STR: 0x7E
PROCESS_NAME: System (.......)
CURRENT_IRQL: 0

................
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: afd
IMAGE_NAME: afd.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4db03d26

demon · Dec 10, 2012

Yan Vugenfirer said:
Hello,

I found this thread by accident while googling. I am the maintainer of virtio-win drivers (https://github.com/YanVugenfirer/kvm-guest-drivers-windows) and although those crashes doesn't seams to be virtio-win specific would like to look at the dump files anyway.

Can you send me minidumps to yvugenfi (at) redhat.com or the location of full zipped dumps ?

Thanks,
Yan Vugenfirer.

Hello.

The same problem with BSOD on windows 2003 x64 and windows 2008 x64
Could you look at my minidumps and help

(sorry for my English)

Strings from minidump 2003
.....................
SYSTEM_SERVICE_EXCEPTION (3b)
.....................
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: SemSvc.exe (here some time PROCESS_NAME: chrome.exe or other)
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffffadf28a8d049 to fffff80001026d90
.................
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: afd!AfdIssueDeviceControl+1a8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: afd
IMAGE_NAME: afd.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 45d69cac
STACK_COMMAND: .cxr 0xfffffadf2598ad50 ; kb
FAILURE_BUCKET_ID: X64_0x3B_afd!AfdIssueDeviceControl+1a8
BUCKET_ID: X64_0x3B_afd!AfdIssueDeviceControl+1a8
..........................

spirit · Dec 11, 2012

demon said:
Hello.

The same problem with BSOD on windows 2003 x64 and windows 2008 x64
Could you look at my minidumps and help (sorry for my English)

Strings from minidump 2003
.....................
SYSTEM_SERVICE_EXCEPTION (3b)
.....................
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: SemSvc.exe (here some time PROCESS_NAME: chrome.exe or other)
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffffadf28a8d049 to fffff80001026d90
.................
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: afd!AfdIssueDeviceControl+1a8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: afd
IMAGE_NAME: afd.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 45d69cac
STACK_COMMAND: .cxr 0xfffffadf2598ad50 ; kb
FAILURE_BUCKET_ID: X64_0x3B_afd!AfdIssueDeviceControl+1a8
BUCKET_ID: X64_0x3B_afd!AfdIssueDeviceControl+1a8
..........................

Can you try last drivers ?
http://people.redhat.com/vrozenfe/build-48/

demon · Feb 1, 2013

spirit said:
Can you try last drivers ?
http://people.redhat.com/vrozenfe/build-48/

With buld-48 the same problem

For now I have
6 minidumps 2003 x64
and
11 minidumps 2008 r2 x64
from 01/01/2013 till now (01/02/2013)

I can send/post this files if it help solve the problem.

tom · Feb 1, 2013

just to note, latest fedora virtio drivers are here: http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/

demon · Feb 1, 2013

tom said:
just to note, latest fedora virtio drivers are here: http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/

I'll try, thanks a lot

Win 2003 x64 crashes (network related?)

Renowned Member

Proxmox Staff Member

Renowned Member

Proxmox Staff Member

Renowned Member

Distinguished Member

Distinguished Member

Renowned Member

Renowned Member

Renowned Member

Distinguished Member

Renowned Member

Yan Vugenfirer

Guest

Distinguished Member

New Member

New Member

Distinguished Member

New Member

Proxmox Staff Member

New Member