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 Ar
I'm afraid there is no "perfect" fix for it - so I need your help evaluating.
And as I assumed it is worse than it seemed at first.
The reason for your finding "I have seen that in 2.3, the utopic machine is a
kvm-2.3 machine while it's a kvm-2.5 machine is 2.5 when it should be kvm-2.3
too" is
** Attachment added: "2.3-trusty-machine-fix"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1641532/+attachment/4777159/+files/2.3-trusty-machine-fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
It's not a debdiff but just the patch I have applied as-is.
--
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:
Unknown ramblock "/rom@etc/acpi/rsdp", cannot accept migration
To manage not
After more investigation (comparation of the machine description between
the ubuntu qemu 2.3 and 2.5), I have seen that in 2.3, the utopic
machine is a kvm-2.3 machine while it's a kvm-2.5 machine is 2.5 when it
should be kvm-2.3 too.
I will provide a debdiff once I have validated my change.
--
** Also affects: cloud-archive
Importance: Undecided
Status: New
--
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:
Unknown ramblock "/rom@etc/acpi/rsdp", cannot accept migration
