All those changes are in qemu 3.0 and later so there it will be covered by our
merge of qemu 3.1
Once that is done we can consider adding the three changes linked here to the
qemu in Bionic and Cosmic.
For your wondering "I'm not sure that fixing backward migration meets the
criteria for an SRU.":
- it is not guaranteed to be working (not fully supported)
- but if one provides the means (fixes, howto) avoid issue we are willing to
help getting them applied
For your wondering about "why Canonical didn't pick up the latest stable
release":
- in the past there were issues with qemu stable releases causing issues on
updates (this was before my time so no details).
- Due to these issues an SRU exception for those minor release updates was
nacked by our Service folks
- in the meantime testing in general got much better so I was planning to
suggest an SRU exception for qemu stable releases from 20.04 onwards (just
intention so far, nothing committed into plans so far)
** Tags added: qemu-19.04
** Also affects: qemu (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu)
Status: New => In Progress
** Changed in: qemu (Ubuntu Bionic)
Status: New => Triaged
** Changed in: qemu (Ubuntu Cosmic)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1809083
Title:
[Ubuntu 18.04] Backward migration of Ubuntu 16.04.4 P8 guest from
Ubuntu 18.04 P9 Host -> Ubuntu 16.04.4 P8 host is broken
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1809083/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
