Windows Server 2012 R2 and 0x0000005D Error

R

rengiared

Renowned Member
Sep 8, 2010
96
0
71
Austria
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
 
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
 
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 ?

 
Last edited:
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
Click to expand...
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 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 !
Click to expand...

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.
 
Last edited:
It fully installed and is working fine.
Spice Drivers won't install (unsupported version), but I guess that is a problem for redhat.
 
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
 
Last edited:
Ah, I thought you meant in the guest. Weird that not having it set on the host caused this problem in the guest.
 
You must log in or register to reply here.
Top Bottom