Windows 2008 sp2: Bluescreen

[frantek]

Hi,

I've a KVM-VM with Windows 2008 sp2. Mainly this VM works but on a irregular base (2 to 8 weeks) it bluescreens with no visible reason. Other Linux and Windows XP VMs on this system work flawlessly. What can I do to solve this problem?

VM:

name: MS-Exchange2008
vlan0: rtl8139=B2:99:A3:0F:58:68
ostype: w2k8
memory: 8192
sockets: 1
boot: ca
freeze: 0
cpuunits: 2000
acpi: 1
kvm: 1
onboot: 0
cores: 2
ide0: vg0:vm-106-disk-1
bootdisk: ide0

System:

uname -a
Linux bs01 2.6.35-2-pve #1 SMP Mon Aug 8 07:25:00 CEST 2011 x86_64 GNU/Linux

pveversion -v
pve-manager: 1.9-26 (pve-manager/1.9/6567)
running kernel: 2.6.35-2-pve
proxmox-ve-2.6.35: 1.8-13
pve-kernel-2.6.32-4-pve: 2.6.32-33
pve-kernel-2.6.35-1-pve: 2.6.35-11
pve-kernel-2.6.35-2-pve: 2.6.35-13
qemu-server: 1.1-32
pve-firmware: 1.0-14
libpve-storage-perl: 1.0-19
vncterm: 0.9-2
vzctl: 3.0.29-3pve1
vzdump: 1.2-16
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.15.0-1
ksm-control-daemon: 1.0-6

 

[tom]

you need to dig deeper on the windows bluescreen, without any info no one can tell anything.

your run an outdated version of Proxmox VE, update to latest 1.9, see http://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_to_1.9

 

[frantek]

Thanks for your reply.

you need to dig deeper on the windows bluescreen, without any info no one can tell anything.

Next time I will do a screen shot.

your run an outdated version of Proxmox VE, update to latest 1.9, see http://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_to_1.9

Oh, ok, thanks, I will do the update.

 

[frantek]

This is the blue screen.

 

[e100]

Did you get updated running the latest 2.6.32 kernel and installed all of the latest Windows updates?

If so, first thing I would check is ram using memtest86+
If not, do the upgrade and see if the problem persists.

 

[frantek]

I'm on 2.6.35-2-pve, not 32

 

[e100]

I would suggest switching to the latest 2.6.32 kernel.

 

[holgihero]

What windows drivers do you use? How do you connect to drive and network?
We had a Win2008 Server also showing blue screens from time to time. We went away from virtio lan and io back to IDE and E1000 network. The server is stable now...

Regards, Holger

* This should have been going to frantek, sorry

 

[frantek]

Again a bluescreen with BAD_POOL_HEADER as usual.

@e100: Why 2.6.32 kernel. Can you give reasons?

@holgihero: Hardware:

- IDE
- rtl8139

@tom: Updates done:

pve-manager: 1.9-26 (pve-manager/1.9/6567)
running kernel: 2.6.35-2-pve
proxmox-ve-2.6.35: 1.8-13
pve-kernel-2.6.32-4-pve: 2.6.32-33
pve-kernel-2.6.35-1-pve: 2.6.35-11
pve-kernel-2.6.35-2-pve: 2.6.35-13
qemu-server: 1.1-32
pve-firmware: 1.0-14
libpve-storage-perl: 1.0-19
vncterm: 0.9-2
vzctl: 3.0.29-3pve1
vzdump: 1.2-16
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.15.0-2
ksm-control-daemon: 1.0-6

 

[tom]

Again a bluescreen with BAD_POOL_HEADER as usual.

@e100: Why 2.6.32 kernel. Can you give reasons?

...

you still run 2.6.35, outdated. update to latest stable 2.6.32, see also http://pve.proxmox.com/wiki/Proxmox_VE_Kernel

 

[frantek]

OK, changed to 2.6.32 ... lets see - but one strange things happened:

The HP P410 devices usually name like this /dev/cciss/c0d0p1 got normal "sd" devices. In my case the server didn't boot because /dev/cciss/c0d0p1 was "renamed" to /dev/sda1. Can some one please point me to some background information about this?