After upgrade to Proxmox 3.2 Windows 7 x64 VM BSOD on reboot

M

MarcelRoelofs

New Member
Feb 17, 2014
10
0
1
After upgrading one of the servers in my cluster to Proxmox 3.2, all Windows 7 x64 VMs on this host consistently BSOD upon rebooting with INTERRUPT_EXCEPTION_NOT_HANDLED. This does not happen after a shutdown, nor does a Windows 8.1 x64 VM exhibit this behavior on reboot.

The VMs have the virtio scsi and network drivers 0.1-74 installed, balloon device has been disabled. I noticed that with 3.2 I got two serial devices for free in all Windows VMs, although they all had problems because they weren't configured. Disabling nor configuring them had any influence on the BSODs.

Any idea what to do about this?

Cheers,
Marcel Roelofs
 
what version the VirtIO SCSI pass-through controller you have? (check via device manager inside windows).

just to note, I do not see this issue here.
 
Last edited:
I did some further experimentation today. Originally I had the CPU type set to 'host' for ultimate speed. After I changed it back to default (kvm64), that seemed to resolve the issue. So apparently, the virtio drivers (version 61.65.104.7400) have a problem with the specific host CPU (Intel(R) Xeon(R) CPU E5-1650 v2) that the cluster runs on.

Cheers,
Marcel
 
Same Problem here with CPU Type set to Host (Dual Xeon X5650). My VMs are Windows 7 64x and Windows 2008R2. I think the problem was at 0.1.65, too. This version was installed yesterday and i got 2 reboot BSOD, now it's 0.1.74.

pveversion -v
proxmox-ve-2.6.32: 3.1-121 (running kernel: 2.6.32-27-pve)
pve-manager: 3.1-45 (running version: 3.1-45/b282dec2)
pve-kernel-2.6.32-27-pve: 2.6.32-121
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-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.5-1
pve-cluster: 3.0-12
qemu-server: 3.1-15
pve-firmware: 1.1-2
libpve-common-perl: 3.0-14
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-19
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-6
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-4
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-1

greets tom
 
Hey guys,

same problem here with virtio-0.1.74 and a Windows Server 2008 r2. But i have no problems before i installed the Microsoft Patches from 11.03.2014.

root@node1# pveversion -v
proxmox-ve-2.6.32: 3.2-121 (running kernel: 2.6.32-27-pve)
pve-manager: 3.2-1 (running version: 3.2-1/1933730b)
pve-kernel-2.6.32-27-pve: 2.6.32-121
pve-kernel-2.6.32-26-pve: 2.6.32-114
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-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.5-1
pve-cluster: 3.0-12
qemu-server: 3.1-15
pve-firmware: 1.1-2
libpve-common-perl: 3.0-14
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-19
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-6
vzctl: 4.0-1pve5
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-4
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-1

greets martin
 
Hi,

same here with Windows 2008 VM and processor type "host". Using kvm64 works.
Host is a HP ProLiant DL360 G5. 2 x Intel(R) Xeon(R) CPU E5440 @ 2.83GHz

# pveversion -v
proxmox-ve-2.6.32: 3.2-121 (running kernel: 2.6.32-27-pve)
pve-manager: 3.2-1 (running version: 3.2-1/1933730b)
pve-kernel-2.6.32-27-pve: 2.6.32-121
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-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.5-1
pve-cluster: 3.0-12
qemu-server: 3.1-15
pve-firmware: 1.1-2
libpve-common-perl: 3.0-14
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-19
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-6
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-4
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-1


Regards
Frank
 
My Win 2k8 r2 running in exactly the same error when i´m using "host" as cpu mode.

@spirit: yes i restartet the node after the kernel update.
 
@spirit > yes i did Update and restart the host after update ( the problem come when use [Host] as CPU
@Stroker89 > you are right same for me
 
HI guys i believe i fixed the hang on start. First tests looks very good. No BSOD after restarting the Windows machine several times. I changed the SCSI Controller Type under "Options" from "Default (LSI 53C895A)" to "VIRTIO".
 
Stroker89 said:
HI guys i believe i fixed the hang on start. First tests looks very good. No BSOD after restarting the Windows machine several times. I changed the SCSI Controller Type under "Options" from "Default (LSI 53C895A)" to "VIRTIO".
Click to expand...

as far I known, the default lsi controller is not supported (no driver) in windows 2008.

But if you are not using scsi drives in your vm, the scsi controller is not enabled. (lsi or virtio-scsi)
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom