Comment 20 for bug 1681839
Revision history for this message
| Christian Ehrhardt (paelzer) wrote Re: libvirt - disk not ready for pivot yet | #20 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Hi Dominik,
thanks for the links.
Yes 1.3.1 is ancient in a way of "as old as the 16.04 Ubuntu release" plus fix-backports as they are identifiable and qualify for the SRU process [1].
We have three Options here, but atm not all are feasible:
1. Backport the fix to Xenial
I beg your pardon, but for this particular case so far I unable to recreate to debug further on my side or to identify the fix it would need for the SRU - I provided a test ppa in c#15 to help with that, but I understand that it can be unwanted to shove that into production systems to test it.
2. Update the packages in Xenial to newer versions
The complexity of the virtualization stack (and all the potential regressions by just upgrading the versions for everyone out there) can be high, so just bumping all those in Xenial to the level e.g. we have in artful do not qualify for an SRU update.
3. Use a backport
Since the virtualization stack is one of those places where the "newer vs stable" issue comes up often, and even more so because newer openstack releases should go along a newer virt-stack there is a way out just as you assume. Via the Ubuntu Cloud Archive [2] you can get access to a backport of the most recent versions into the latest LTS. While it wasn't created for that I'd think this is the "backport" to 16.04 LTS you might be looking for.
[1]: https:/
[2]: https:/