Windows Server 2012 R2 and 0x0000005D Error
- Thread starter rengiared
- Start date
Sorry to revive this old thread but I just ran across this issue and wanted to share my solutions.
If I set my CPU type to SandyBridge (what the host has) the Win 2012 iso boots up ok and so does Win 2012.
If I leave CPU set to default and add this to the conf file the Win 2012 iso boots ok but I did not test this with running the installed Win 2012.
spirit, I remember some talk on pve-devel about adding a win8.1 option, was that accepted?
If I set my CPU type to SandyBridge (what the host has) the Win 2012 iso boots up ok and so does Win 2012.
If I leave CPU set to default and add this to the conf file the Win 2012 iso boots ok but I did not test this with running the installed Win 2012.
Code:
args: -cpu kvm64,+lahf_lm,+cx16spirit, I remember some talk on pve-devel about adding a win8.1 option, was that accepted?
yes, the lahf_lm has been added to win8 ostype one month ago. (I'm not sure it's already in pve-no-subscription repository)
I was reading that qemu already had the cx16 flag:
http://pve.proxmox.com/pipermail/pve-devel/2013-October/009079.html
Was that cx16 flag added to the newer version?
The 2012 ISO would only boot when I added both flags, I tried both individually.
The patch add only lahf_lm to kvm64 cpu model
https://git.proxmox.com/?p=qemu-server.git;a=commit;h=4dc339e7b4d0f4aa1756263ec889104de182994d
cx16 is already enabled by default in kvm64
see qemu source here for default cpu flags:
http://git.qemu.org/?p=qemu.git;a=b...a8c7160b673e75d546cc5beeed0740d9ea910;hb=HEAD
I'm having trouble locating the exact spot where we edit this .conf file at? Is it here: etc/pve/qemu-server/<VM number>.conf
Anytime we try to access this folder we get a permission denied message. I was told the following from the Linux person that setup our environment
“They don’t have root passwords. Ubuntu and Debian follow the ‘best practices’ and disable logging in as root” These are underlying as the ProxMox is the actual operating system for the servers using one of these as the foundation."
I was also told that my user has full admin access so i'm not sure why I can't get into this folder.
Any help is greatly appreciated, Thank You!!
Anytime we try to access this folder we get a permission denied message. I was told the following from the Linux person that setup our environment
“They don’t have root passwords. Ubuntu and Debian follow the ‘best practices’ and disable logging in as root” These are underlying as the ProxMox is the actual operating system for the servers using one of these as the foundation."
I was also told that my user has full admin access so i'm not sure why I can't get into this folder.
Any help is greatly appreciated, Thank You!!
debian does not disable root access, only Ubuntu does. You must be logged in as root to access /etc/pve.
it could also be that the cluster lost quorum (too few nodes working to take safe decisions) and /etc/pve is in read-only mode
you can check trying, as root:
#clustat
you should read
"Member Status: Quorate"
otherwise /etc/pve is "protected", ie: in read only mode.
in this case, you can temporarily (until reboot) regain quorum with
#pvecm expected <number>
where <number is the number of your current active node votes
see also the output of
#pvecm status
Marco
you can check trying, as root:
#clustat
you should read
"Member Status: Quorate"
otherwise /etc/pve is "protected", ie: in read only mode.
in this case, you can temporarily (until reboot) regain quorum with
#pvecm expected <number>
where <number is the number of your current active node votes
see also the output of
#pvecm status
Marco
I just to confirm I has some issue. Windows 2012 0x0000005D error trying to install on Proxmox 3.4 and 3.3.
I ENABLED No-Execute Memory Protection in BIOS and they installed fine. The machines were HP ML and DL series.
In fact using processor type kvm64 when the BIOS setting "No-Execute Memory Protection" was enabled it AUTOMATICALLY ADDED args : -cpu kvm64,+cx16 to the .conf file.
Stephen
I ENABLED No-Execute Memory Protection in BIOS and they installed fine. The machines were HP ML and DL series.
In fact using processor type kvm64 when the BIOS setting "No-Execute Memory Protection" was enabled it AUTOMATICALLY ADDED args : -cpu kvm64,+cx16 to the .conf file.
Stephen
Last edited:
Hi, proxmox don't add theses args anywhere. You must have done it manually.
Anyway, they are not require to boot win2012r2.
Only +lahf was missing, and proxmox pass it to qemu command line at vm start since proxmox 3.2. (but nothing special is write in vm config)