PVE 4.0 Beta2 + qemu + acpi

ok, thanks.
I think I have found the problem, it's a mix between qemu 2.4 + kernel 4.2 + kvm.

rollbacking to kernel 4.1 also fix the problem.
I think it's a kvm bug in kernel 4.2.

I'll contact the qemu team to have help.

Thanks for help !
 
Works for me as well.

Could you give some more details on what features cause these troubles?
 
Last edited:
Works for me as well.

Could you give some more details on what features cause these troubles?

It's related to a new kvm feature KVM_CAP_X86_SMM

https://lkml.org/lkml/2015/5/8/235

exposed since kernel 4.2.

qemu 2.4 with machine 2.4, try to enable it. But it seem to hang on some servers/chipset?/cpus?.

I'm currently debug it with paolo bonzini from qemu team.



For other guys in this thread, could you test it too ? (the pve-qemu-kvm package)
I'm also interested to have result of this command:

grep -r . /sys/module/kvm*/parameters
 
It's related to a new kvm feature KVM_CAP_X86_SMM

https://lkml.org/lkml/2015/5/8/235

exposed since kernel 4.2.

qemu 2.4 with machine 2.4, try to enable it. But it seem to hang on some servers/chipset?/cpus?.

I'm currently debug it with paolo bonzini from qemu team.



For other guys in this thread, could you test it too ? (the pve-qemu-kvm package)
I'm also interested to have result of this command:

grep -r . /sys/module/kvm*/parameters

I can confirmed that is work also for me.

Here comes my results:

root@w01-c-h:~# grep -r . /sys/module/kvm*/parameters
/sys/module/kvm_intel/parameters/ept:Y
/sys/module/kvm_intel/parameters/pml:N
/sys/module/kvm_intel/parameters/vpid:Y
/sys/module/kvm_intel/parameters/enable_shadow_vmcs:N
/sys/module/kvm_intel/parameters/eptad:N
/sys/module/kvm_intel/parameters/flexpriority:Y
/sys/module/kvm_intel/parameters/ple_window_grow:2
/sys/module/kvm_intel/parameters/ple_window_shrink:0
/sys/module/kvm_intel/parameters/ple_window_max:1073741823
/sys/module/kvm_intel/parameters/fasteoi:Y
/sys/module/kvm_intel/parameters/enable_apicv:N
/sys/module/kvm_intel/parameters/unrestricted_guest:N
/sys/module/kvm_intel/parameters/emulate_invalid_guest_state:Y
/sys/module/kvm_intel/parameters/nested:N
/sys/module/kvm_intel/parameters/vmm_exclusive:Y
/sys/module/kvm_intel/parameters/ple_window:4096
/sys/module/kvm_intel/parameters/ple_gap:0
/sys/module/kvm/parameters/tsc_tolerance_ppm:250
/sys/module/kvm/parameters/halt_poll_ns:0
/sys/module/kvm/parameters/min_timer_period_us:500
/sys/module/kvm/parameters/kvmclock_periodic_sync:Y
/sys/module/kvm/parameters/ignore_msrs:N
/sys/module/kvm/parameters/allow_unsafe_assigned_interrupts:N
/sys/module/kvm/parameters/lapic_timer_advance_ns:0

Thank you Spirit!
 
In my case BIOS has been updated to the latest one. Will try to update CPU microcode (never have done it before :) )
 
microcode-20150121.tgz from Intel website

Code:
root@pve:/tmp/micro# iucode_tool -tb -lS /tmp/micro
iucode_tool: system has processor(s) with signature 0x000106a5
selected microcodes:
001: sig 0x000106a5, pf mask 0x03, 2013-06-21, rev 0x0019, size 10240

Code:
root@pve:/tmp/micro# dmesg | grep microcode
[    0.781385] microcode: CPU0 sig=0x106a5, pf=0x1, revision=0x19
[    0.781392] microcode: CPU1 sig=0x106a5, pf=0x1, revision=0x19
[    0.781399] microcode: CPU2 sig=0x106a5, pf=0x1, revision=0x19
[    0.781409] microcode: CPU3 sig=0x106a5, pf=0x1, revision=0x19
[    0.781415] microcode: CPU4 sig=0x106a5, pf=0x1, revision=0x19
[    0.781422] microcode: CPU5 sig=0x106a5, pf=0x1, revision=0x19
[    0.781428] microcode: CPU6 sig=0x106a5, pf=0x1, revision=0x19
[    0.781433] microcode: CPU7 sig=0x106a5, pf=0x1, revision=0x19
[    0.781489] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba

Seems nothing to update(((
 
Great ! :)

Note that currently it's more like a workaround to disable the new feature introduce from kernel 4.2.
I'm currently debugging the kernel with paolo from qemu, I hope we'll find where is the problem soon.

(This feature is only to manage uefi inside guest vm, so it's not critical)
 
Thx.On my
Code:
 Supermicro X8DTT + L5520
with pve-qemu-kvm: 2.4-9 all works great.
Previous version pve-qemu-kvm: 2.4-8 - unfortunately not.
If you need a tester/platform for test - please PM me, i will try to help.
 
Going to change CPU to X5650 but it seems probably not related to CPU/microcode
 
Going to change CPU to X5650 but it seems probably not related to CPU/microcode

Paolo from qemu think it's not related if microcode is upgraded to last version.
He send me some kernel patches to display more debug infos.

I'll keep you in touch as soon as possible.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!