Hmm, we just don't need the xenial portion.
As already mentioned at the backport the code was way different then.
I can start a VMX defined guest on Xenial:
<cpu match='exact'>
<model fallback='allow'>core2duo</model>
<vendor>Intel</vendor>
<feature policy='require' name='vmx'/>
</cpu>
And it becomes -cpu core2duo,+vmx for qemu commandline.
So Xenial is actually "invalid" as the issue described here doesn't apply there.
** Changed in: libvirt (Ubuntu Xenial)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830268
Title:
Use changed nested VMX attribute as trigger to refresh libvirt
capability cache
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1830268/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
