I am currently testing pve-qemu-kvm 11.0.0-1 from the test repository to utilize hardware acceleration via MBEC/GMET on HVCI.
Up to Qemu 11, the only option is “Disabled.” Without hardware acceleration, performance will likely drop significantly.
The test is already available. It’s currently just a working prototype, but official support will require an update to Qemu.
*If you just want to play around, go ahead and try it. If it’s for business purposes, please refrain...
Virtual machines with the Hyper-V role added get stuck in a boot loop with the following combinations:
The system boots without issues in the following cases:
A temporary workaround
It appears that there is an issue with the combination of a kernel that supports MBEC/GMET and QEMU 11.
*7.0.0-3-pve is the first kernel to which MBEC/GMET v3 was backported.
7.0.2-1-pve is a kernel with MBEC/GMET v5 backported.
Since version 7.0.0-2-pve does not include backports for MBEC/GMET, and since the issue does not occur when used in combination with that version, and since it does not occur with QEMU 10, we have determined that the issue occurs specifically when using a kernel that includes MBEC/GMET in combination with QEMU 11.
Is there anything you can provide to help us investigate this?
Whats the current best practice regarding having to use vbs in windows: host ?
Up to Qemu 11, the only option is “Disabled.” Without hardware acceleration, performance will likely drop significantly.
The test is already available. It’s currently just a working prototype, but official support will require an update to Qemu.
*If you just want to play around, go ahead and try it. If it’s for business purposes, please refrain...
Virtual machines with the Hyper-V role added get stuck in a boot loop with the following combinations:
Code:
pve-qemu-kvm 11.0.0-1 ⁺ Linux 7.0.0-3-pve
pve-qemu-kvm 11.0.0-1 ⁺ Linux 7.0.2-1-pve
The system boots without issues in the following cases:
Code:
pve-qemu-kvm 11.0.0-1 ⁺ Linux 7.0.0-2-pve
pve-qemu-kvm 10.2.1-2 ⁺ Linux 7.0.0-3-pve
pve-qemu-kvm 10.2.1-2 ⁺ Linux 7.0.2-1-pve
A temporary workaround
Code:
apt install pve-qemu-kvm=10.2.1-2
apt-mark hold pve-qemu-kvm
It appears that there is an issue with the combination of a kernel that supports MBEC/GMET and QEMU 11.
*7.0.0-3-pve is the first kernel to which MBEC/GMET v3 was backported.
7.0.2-1-pve is a kernel with MBEC/GMET v5 backported.
Since version 7.0.0-2-pve does not include backports for MBEC/GMET, and since the issue does not occur when used in combination with that version, and since it does not occur with QEMU 10, we have determined that the issue occurs specifically when using a kernel that includes MBEC/GMET in combination with QEMU 11.
Is there anything you can provide to help us investigate this?
Last edited: