Upgrade to 3.4 Windows 2008 R2 BSOD at boot

[mcmyst]

Hi,

I am having a big problem since upgrade from 3.2 to 3.4, when I try to start a Windows Server 2008 R2 it won't boot and show me a BSOD with this message:
*** STOP : 0x0000005D

I have found this thread, and I have tested every args pointed in the thread but nothing works:
args: -cpu kvm64,+nx
args: -cpu kvm64,+cx16
args : -cpu kvm64,+lahf_lm
args: -cpu kvm64,+lahf_lm,+cx16

I have also tried to cpu Host but it won't boot...

PVE Version:

pveversion -v
proxmox-ve-2.6.32: 3.4-166 (running kernel: 2.6.32-43-pve)
pve-manager: 3.4-11 (running version: 3.4-11/6502936f)
pve-kernel-2.6.32-29-pve: 2.6.32-126
pve-kernel-2.6.32-43-pve: 2.6.32-166
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-3
pve-cluster: 3.0-19
qemu-server: 3.4-6
pve-firmware: 1.1-5
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-34
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.2-14
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1

I can't go back to Proxmox 3.2 so I am stuck with that !

Any help is appreciated .

 

[Richard]

Hi,

I am having a big problem since upgrade from 3.2 to 3.4, when I try to start a Windows Server 2008 R2 it won't boot and show me a BSOD with this message:
*** STOP : 0x0000005D

Also Proxmox 3.4 is almost outdated in the meantime - why not upgrading to 4.1?

The above message indicated a with virtualized hardware - I think there is a good chance to get rid of this problem with 4.1 which has a new (improved) kernel, new qemu-kvm etc.

On the other hand: windows is very sensible regarding hardware changes, even if it´s a virtual one. I would upgrade to Proxmox VE 4.1 and if the problem persists reinstall Windows. The data from the old virtual disk you will be able to read in your new Windows then.

 

[spirit]

If you don't use openvz, you can try to use pve-kernel-3.10

 

[Jeff Wadsworth]

I noticed this same BSOD with Windows 2008 R2 when using Proxmox 4.1 within a virtual environment (ie: Oracle VirtualBox). Once Proxmox 4.1 was installed on an actual server/workstation, it was fine.