Problem with Windows and Linux VMs if i choose Processor type Haswell

D

Daniel Keller

Renowned Member
Mar 10, 2015
39
3
73
Hello,

I have a problem with windows and linux VMs if i choose processor type haswell (or any other intel processor type) for the VMs i get the error:

kernel: [ 1976.482041] kvm [18316]: vcpu0 unhandled rdmsr: 0xce

Sometimes this causing a memory error in the Windwos Server 2012R2 vm followed by a reboot of the vm.

As workaround i have to choose the processor type kvm64 or host then no errors are showing and all is good.

The host servers has a Intel Xeon e5-2620 v3 processor.

I have tested it with the kernel 2.6.32 and 3.10 and with both the errors are exists.

Any ideas how to fix this problem?
 
My motherboard is a Supermicro X10DRI.

Since i have changed processor typ to kvm64 my cenots7 guest had no problems.

The Windwos Server 2012 R2 is getting the error "unable to connect to VM 103 socket - timeout after 31 retries" if i run disk benchmarks inside the vm.
 
X10DAI here
I've not had any issues with Windows 2008R2 or 2012R2, only with debian wheezy guests.

I was just reading through the January 2015 Processor Specification Update
http://www.intel.com/content/dam/ww...cification-updates/xeon-e5-v3-spec-update.pdf

HSE29
Implication: Guest software may crash or experience unpredictable behaviour as a result of this erratum.
Workaround: It is possible for the BIOS to contain a workaround for this erratum.

HSE60
Implication: The unexpected system behaviour may result in incorrect instruction execution, EPT (Extended Page Table) violation, page fault, or similar event.
Workaround: It is possible for the BIOS to contain a workaround for this erratum.

Both of those seem like issues that might be causing the problems we have experienced.

Supermicro does not publish BIOS changelogs so I have no idea if those issues are corrected in the latest update or not.:mad:
I emailed supermicro asking for a changelog, maybe if enough people start asking for them they will start including them by default.
 
e100 said:
No solution but you are not the only person who has issues with newer Haswell processors.

I've had issues with IO stalling in debian 7 guests, changing from virtio to ide is the only workaround I've found for my issue.

http://forum.proxmox.com/threads/20372-Linux-guest-problems-on-new-Haswell-EP-processors

What motherboard are you using?
Click to expand...

I'm running E5-2687W v3 @ 3.10GHz without any problem.
Dell r630 server, with host on pve 3.10 kernel

I'm running debian wheezy guest, but with 3.16 kernel from backports (kvm64 vcpu).

Note that sometime bios updates also update cpu microcodes.
 
I have found two problems they are now are fixed for me.

first problem was some error with the processor features now with the BIOS Revision: R 1.1 i can choose processor type "host" without a error.

the guest hangs was for me fixed with the new stable virtio drivers for windows 2012r2 0.1.96
 
You must log in or register to reply here.
Top Bottom