With the fix applied, the most reduced case is:
<cpu mode='custom' match='exact' check='full'>
<model fallback='forbid'>qemu64</model>
<feature policy='require' name='x2apic'/>
<feature policy='require' name='hypervisor'/>
<feature policy='require' name='lahf_lm'/>
<feature policy='disable' name='svm'/>
</cpu>
Which ends up as:
-cpu qemu64
That is without VMX (as expected)
If adding FMX as feature (didn't work to enable it before)
<cpu mode='custom' match='exact' check='full'>
<model fallback='forbid'>qemu64</model>
<feature policy='require' name='vmx'/>
=> Nested KVM works
=> It got a smaller subset of cpuflags than in the past - just vmx + tpr_shadow
And if started with <cpu> tag at all it gets:
<cpu mode='custom' match='exact' check='full'>
<model fallback='forbid'>qemu64</model>
<feature policy='require' name='x2apic'/>
<feature policy='require' name='hypervisor'/>
<feature policy='require' name='lahf_lm'/>
<feature policy='disable' name='svm'/>
</cpu>
So we are missing to get VMX auto added here as we did in the past.
We can enable VMX now (ok for upgraders of old guests), but the same
XML/commandline still is too different.
Maybe I need to re-add the main flag as well, lets do a rebuild over
night.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868692
Title:
default cpu (qemu64) no more capable of nesting
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1868692/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
