Comment 5 for bug 1641532
Revision history for this message
| Christian Ehrhardt (paelzer) wrote Re: Unknown ramblock "/rom@etc/acpi/rsdp", cannot accept migration | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
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.