Windows Server 2012 R2 and 0x0000005D Error

rengiared · Sep 27, 2013

hi,

i have troubles installing Windows Server 2012 R2 on an actual PVE System.
Every time the VM boots from the win2k12r2 iso i get the following error: (immediately after the windows logo appears the first time)

Code:

Your PC needs to restart.
Please hold down the power button.
Error Code: 0x0000005D

as soon as i change the cpu type from "default (kvm64)" to e.g. "sandy bridge" it boots right through to the install-menu.

i this on your radar so this could work with the default cpu type in the near future?

Code:

root@pve01:~# pveversion -v
proxmox-ve-2.6.32: 3.1-111 (running kernel: 2.6.32-24-pve)
pve-manager: 3.1-14 (running version: 3.1-14/d914b943)
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-24-pve: 2.6.32-111
pve-kernel-2.6.32-16-pve: 2.6.32-82
pve-kernel-2.6.32-17-pve: 2.6.32-83
pve-kernel-2.6.32-14-pve: 2.6.32-74
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-23-pve: 2.6.32-109
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.0-2
pve-cluster: 3.0-7
qemu-server: 3.1-4
pve-firmware: 1.0-23
libpve-common-perl: 3.0-6
libpve-access-control: 3.0-6
libpve-storage-perl: 3.0-13
pve-libspice-server1: 0.12.4-2
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.0-2

thanks in advance

eislon · Oct 19, 2013

I also see the same thing.
Probably MS has build a check in on cpu code?

Nakata · Oct 29, 2013

same here

Code:

root@pve01:~# pveversion -v
proxmox-ve-2.6.32: 3.1-109 (running kernel: 2.6.32-23-pve)
pve-manager: 3.1-3 (running version: 3.1-3/dc0e9b0e)
pve-kernel-2.6.32-23-pve: 2.6.32-109
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.0-1
pve-cluster: 3.0-7
qemu-server: 3.1-1
pve-firmware: 1.0-23
libpve-common-perl: 3.0-6
libpve-access-control: 3.0-6
libpve-storage-perl: 3.0-10
pve-libspice-server1: 0.12.4-1
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.0-2

spirit · Oct 29, 2013

I found this:
http://social.technet.microsoft.com...54a/compatibility-problem-with-kvm64-cpu-type

"Windows 8.1 requires CMPXCHG16B
This also causes failures for Virtualbox:
http://4sysops.com/forums/topic/windows-server-2012-r2-on-virtual-box-error-0x000000c4/
try if you can activate this feature for KVM."

So maybe it's a missing cpu flag on default kvm64, I'll try to find more informations

e100 · Oct 29, 2013

There is some related info here: https://bugs.launchpad.net/qemu/+bug/921208

One suggestion was to try:

Code:

-cpu kvm64,+nx

spirit · Oct 29, 2013

ok, it's missing the +cx16 cpuflag in default kvm64.

I'll make a patch to enable it for windows 8.1

spirit · Oct 29, 2013

e100 said:
There is some related info here: https://bugs.launchpad.net/qemu/+bug/921208

One suggestion was to try:

Code:

-cpu kvm64,+nx

this is unrelated, it was for win7.

for windows8.1, can you try to add in vm config:

args : -cpu kvm64,+cx16

Nakata · Oct 29, 2013

args : -cpu kvm64,+cx16 seems not helping,
But Windows 2012 R2 (SW_DVD5_Windows_Svr_Std_and_DataCtr_2012_R2_64Bit_English_Core_MLF_X19-05182.ISO) is booting fine with CPU set to qemu64

are there any possible future problems with changing CPU to qemu64 ?
or lack of performance or any other cons ?

Fibo · Oct 29, 2013

Nakata said:
args : -cpu kvm64,+cx16 seems not helping,
But Windows 2012 R2 (SW_DVD5_Windows_Svr_Std_and_DataCtr_2012_R2_64Bit_English_Core_MLF_X19-05182.ISO) is booting fine with CPU set to qemu64

Same for me. After fights with kvm64 and SandyBridge, qemu64 was the solution. (FR_FR version)

Will be glad to read comments about performance.

spirit · Nov 1, 2013

Hi, can you try with

args : -cpu kvm64,+lahf_lm

Seem to be the missing flag in kvm64 cpu type

blackpaw · Nov 13, 2013

spirit said:
Hi, can you try with

args : -cpu kvm64,+lahf_lm

Seem to be the missing flag in kvm64 cpu type

Whereabouts does one set this?

Thanks.

m.ardito · Nov 13, 2013

blackpaw said:
Whereabouts does one set this? Thanks.

you should edit the .conf

Marco

Nakata · Nov 13, 2013

m.ardito said:
you should edit the .conf

Marco

but remember, any change, like connecting iso or change description of VMS will delete those flags from config

spirit · Nov 13, 2013

Hi,
I would like to known if" -cpu kvm64,+lahf_lm "

fix the problem or not, to make an offical patch for proxmox.

Thanks !

blackpaw · Nov 13, 2013

spirit said:
Hi,
I would like to known if" -cpu kvm64,+lahf_lm "

fix the problem or not, to make an offical patch for proxmox.

Thanks !

That seems to have done the trick for me spirit, I:

- Created a fresh 20012 R2 VM

- Verified it was continually rebooting on startup from the iso

- Stopped it

- added "args : -cpu kvm64,+lahf_lm" to the .conf file.

- Its now letting me going through the installer.

Thanks for the fix.

blackpaw · Nov 13, 2013

It fully installed and is working fine.
Spice Drivers won't install (unsupported version), but I guess that is a problem for redhat.

mat02 · Dec 2, 2013

Hello,
Today I've tried to install Windows Server 2012R2 Standard x64 on my Proxmox server and even trying flags mentioned earlier I still get bootloop with 0x000000C4 error (I'm not 100% sure if it is always the same error code, because it's rebooting so quickly :/ ).
My setup is HP DL360G5 with Xeon 5120 (2x 1.86GHz) and 10GB of RAM.
Here's my config:

Code:

root@proxmox:~# cat /etc/pve/qemu-server/107.conf
args: -cpu qemu64,+sep,+cx16,+lahf_lm
cores: 2
ide0: local:107/vm-107-disk-1.qcow2,format=qcow2,size=80G
ide2: local:iso/winsrv.iso,media=cdrom
memory: 1024
name: WinSrv2k12R2
ostype: win8
sockets: 1

Here's my pveversion log:

Code:

root@proxmox:~# pveversion -v
proxmox-ve-2.6.32: 3.1-114 (running kernel: 2.6.32-26-pve)
pve-manager: 3.1-24 (running version: 3.1-24/060bd5a6)
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-19-pve: 2.6.32-95
pve-kernel-2.6.32-24-pve: 2.6.32-111
pve-kernel-2.6.32-16-pve: 2.6.32-82
pve-kernel-2.6.32-25-pve: 2.6.32-113
pve-kernel-2.6.32-22-pve: 2.6.32-107
pve-kernel-2.6.32-26-pve: 2.6.32-114
pve-kernel-2.6.32-23-pve: 2.6.32-109
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.0-2
pve-cluster: 3.0-8
qemu-server: 3.1-8
pve-firmware: 1.0-23
libpve-common-perl: 3.0-9
libpve-access-control: 3.0-8
libpve-storage-perl: 3.0-18
pve-libspice-server1: 0.12.4-2
vncterm: 1.1-6
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.1-1

Best regards
Mateusz

UPDATE:
After changing cpu type to host it stops on 0x0000005d error code :/

UPDATE and SOLVED:
I've realized that I had No-Execute Memory Protection disabled in BIOS and that caused Bootloop. I've enabled it and... christmas came earlier this year ;D

blackpaw · Dec 11, 2013

mat02 said:
I've realized that I had No-Execute Memory Protection disabled in BIOS and that caused Bootloop. I've enabled it and... christmas came earlier this year ;D

How did you do that?

mat02 · Dec 11, 2013

I've enabled it in my host's BIOS (it was disabled on my HP DL360 G5 server :/).

blackpaw · Dec 11, 2013

Ah, I thought you meant in the guest. Weird that not having it set on the host caused this problem in the guest.

Windows Server 2012 R2 and 0x0000005D Error

Renowned Member

Renowned Member

Renowned Member

Distinguished Member

Renowned Member

Distinguished Member

Distinguished Member

Renowned Member

New Member

Distinguished Member

Renowned Member

Famous Member

Renowned Member

Distinguished Member

Renowned Member

Renowned Member

New Member

Renowned Member

New Member

Renowned Member