This bug was fixed in the package libvirt - 5.0.0-1ubuntu2.2
---
libvirt (5.0.0-1ubuntu2.2) disco; urgency=medium
* d/p/ubuntu/lp-1825195-*.patch: fix issues with old guests that defined
the never functional osxsave and ospke features (LP: #1825195).
-- Christian Ehrhardt
This bug was fixed in the package libvirt - 5.0.0-1ubuntu2.2
---
libvirt (5.0.0-1ubuntu2.2) disco; urgency=medium
* d/p/ubuntu/lp-1825195-*.patch: fix issues with old guests that defined
the never functional osxsave and ospke features (LP: #1825195).
-- Christian Ehrhardt
Thanks, setting up the case on Disco (without proposed) as outlined and
hitting it:
Using:
core2duo
root@d:~# virsh start test-osx
error: Failed to start domain test-osx
error: internal error: process exited while connecting to monitor:
2019-05-22T06:47:37.379603Z
Hello Christian, or anyone else affected,
Accepted libvirt into disco-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libvirt/5.0.0-1ubuntu2.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Now that it is complete in Eoan and upstream accepted I uploaded it to
Disco-unapproved as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825195
Title:
qemu dropped osxsave/ospke feature
** Changed in: qemu (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825195
Title:
qemu dropped osxsave/ospke feature triggering upgrade issues
To manage
This bug was fixed in the package libvirt - 5.0.0-1ubuntu4
---
libvirt (5.0.0-1ubuntu4) eoan; urgency=medium
* d/p/ubuntu/lp-1825195-*.patch: fix issues with old guests that defined
the never functional osxsave and ospke features (LP: #1825195).
* d/p/series: reorder ubuntu
** Description changed:
## Bug ##
There are conditions where old qemu/libvirt created guests with the
osxsafe or ospke cpu feature:
That feature was removed in recent qemu, this triggers issues starting
some old guests definitions using it after upgrade.
After successful tests submitted upstream at
https://www.redhat.com/archives/libvir-list/2019-April/msg01388.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825195
Title:
qemu dropped
** Description changed:
+ [Impact]
+
+ * Newer qemu dropped a few features (that never worked) without
+deprecation period. In some edge cases that might trigger qemu no more
+starting at all.
+
+ * Fix by backporting the upstream fix (in those Ubuntu releases that have
+an
Some details from testing that make it even less severe ...
Note: since this was never in any Host defined any required setting would have
triggered a pre-check like:
error: the CPU is incompatible with host CPU: Host CPU does not provide
required features: ospke
But if set to optional:
I have created a preliminary patch and a PPA for Disco with it.
The plan is to do some testing on that and then suggest the change upstream.
History has shown that such fixes can differ greatly depending on the
"preferred style" how to implement it thou - so there might be a few iterations
The fix in newer virt-install might be related to https://github.com
/virt-manager/virt-manager/commit/469fed08
** Description changed:
## Bug ##
There are conditions where old qemu/libvirt created guests with the
osxsafe or ospke cpu feature:
That feature was
** Description changed:
## Bug ##
There are conditions where old qemu/libvirt created guests with the
osxsafe or ospke cpu feature:
That feature was removed in recent qemu, this triggers issues starting
some old guests definitions using it after upgrade.
Triggers that would in the past have added the flag in the past - it
will have to be fixed anyway, but this is mostly to evaluate the
severity/urgency of the issue.
TL;DR: it seems rare to have been added, yet we haven't covered all
cases and there must be a reason why it occurred
Will trigger,
15 matches
Mail list logo
