Hello,
Since about a few months back our Windows Server 2008 VM's keep getting random BSOD's(see screen below)
Often when we reset the VM we keep getting that same BSOD. Migrating the VM to a different PVE node somethings allows the VM to boot. When even this doesn't work we change some settings like CPU's and maybe the VM then does boot. There is no clear solution to make the VM boot again. Sometimes we just keep on resetting the VM until it works again. We are using the following version of proxmox each with the same problem:
2.6.32-29-pve
3.10.0-4-pve
3.10.0-5-pve
The newest:
3.10.0-7-pve
Note that even a fresh installation of windows has the same problem. We suspect the problem started the first time we had a Windows VM on PVE version 3.10 and higher. Can anyone help me debug this problem?
Thanks in advance!
Since about a few months back our Windows Server 2008 VM's keep getting random BSOD's(see screen below)
Often when we reset the VM we keep getting that same BSOD. Migrating the VM to a different PVE node somethings allows the VM to boot. When even this doesn't work we change some settings like CPU's and maybe the VM then does boot. There is no clear solution to make the VM boot again. Sometimes we just keep on resetting the VM until it works again. We are using the following version of proxmox each with the same problem:
2.6.32-29-pve
3.10.0-4-pve
3.10.0-5-pve
The newest:
3.10.0-7-pve
Code:
proxmox-ve-2.6.32: 3.3-147 (running kernel: 3.10.0-7-pve)
pve-manager: 3.4-1 (running version: 3.4-1/3f2d890e)
pve-kernel-3.10.0-7-pve: 3.10.0-27
pve-kernel-2.6.32-37-pve: 2.6.32-147
pve-kernel-2.6.32-29-pve: 2.6.32-126
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-2
pve-cluster: 3.0-16
qemu-server: 3.3-20
pve-firmware: 1.1-3
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-31
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.1-12
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1
Note that even a fresh installation of windows has the same problem. We suspect the problem started the first time we had a Windows VM on PVE version 3.10 and higher. Can anyone help me debug this problem?
Thanks in advance!
Last edited: