ATM - I can't think of a really good way out.
We can fix X/Y/Z releases to expect the "correct" types when seeing the old
machine-types.
On top one would have to to the same for all qemus in UCA.
But everybody that had (re)-started a guest "in between" with a newer
qemu - think of Ubuntu Cloud Archive that can give Trusty all varieties
of Qemu - might have a different version on his guests.
Trying to summarize:
- Affected machine types: trusty and utopic
- Effect: those types are not non-ambiguous, they can be any hw_version from
2.0-2.5 depending on
under which qemu they were started last time.
Status today - a migration forward fails in some combinations but not in others.
- Trusty as-is (2.0) to Xenial works even with the bug in place.
- Trusty + UCA-Liberty (2.3) to Xenial fails due to the issue.
- other combinations have to be evaluated
Fixing the types to the "correct" ones will fix anybody that never has
restarted the guests.
But it might break those that have restarted guests as they have accidentally
picked up a too new guest type.
** Changed in: qemu (Ubuntu)
Status: New => Confirmed
** Changed in: qemu (Ubuntu)
Importance: Undecided => Critical
** Summary changed:
- Unknown ramblock "/rom@etc/acpi/rsdp", cannot accept migration
+ machine-types trusty and utopic are not unique (depend on the qemu version)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641532
Title:
machine-types trusty and utopic are not unique (depend on the qemu
version)
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1641532/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
