[Group.of.nepali.translators] [Bug 1830268] Re: Use changed nested VMX attribute as trigger to refresh libvirt capability cache

2019-06-24 Thread Launchpad Bug Tracker
This bug was fixed in the package libvirt - 4.0.0-1ubuntu8.11 --- libvirt (4.0.0-1ubuntu8.11) bionic; urgency=medium * d/p/ubuntu/lp-1830268-refresh-capabilities-on-KVM-nesting.patch: fix consideration of VMX flag (LP: #1830268) -- Christian Ehrhardt Mon, 27 May 2019 11:52:0

[Group.of.nepali.translators] [Bug 1830268] Re: Use changed nested VMX attribute as trigger to refresh libvirt capability cache

2019-06-17 Thread Launchpad Bug Tracker
This bug was fixed in the package libvirt - 4.6.0-2ubuntu3.6 --- libvirt (4.6.0-2ubuntu3.6) cosmic; urgency=medium * d/p/ubuntu/lp-1830268-refresh-capabilities-on-KVM-nesting.patch: fix consideration of VMX flag (LP: #1830268) -- Christian Ehrhardt Tue, 28 May 2019 07:59:48

[Group.of.nepali.translators] [Bug 1830268] Re: Use changed nested VMX attribute as trigger to refresh libvirt capability cache

2019-06-03 Thread Christian Ehrhardt 
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: core2duo Intel And it becomes -cpu core2duo,+vmx for qemu commandline. So Xenial is actually "invalid" as the issue desc