I was analyzing the case for myself now, here my notes as documentation.
The default type in Precise is (now): pc-1.0-qemu-kvm
The logic in Trusty's libvirt to receive is in src/qemu/qemu_migration.c:
IF TYPE = pc-1.0 && allow_incoming_qemukvm
THEN SET TYPE => pc-1.0-precise
But as shown above the type is pc-1.0-qemu-kvm in Precise, so the upper logic
doesn't apply
This is in patch: debian/patches/define-qemu-kvm-mt
In since 1.0+noroms-0ubuntu14.18 due to LP: #1374612
That would still be fine as on Precise pc-1.0-qemu-kvm is a type with alias
pc-1.0-precise.
So this is the Distribution specific type. Only Trusty has to agree on the
definition of the type.
On Trusty this seems wrong, here I see double pc-1.0-qemu-kvm:
kvm -M ? | egrep '(precise|1.0)'
pc-1.0-qemu-kvm Standard PC (i440FX + PIIX, 1996) (alias of pc-1.0)
pc-1.0 Standard PC (i440FX + PIIX, 1996)
pc-1.0-precise Standard PC (i440FX + PIIX, 1996) (alias of
pc-1.0-qemu-kvm)
pc-1.0-qemu-kvm Standard PC (i440FX + PIIX, 1996)
One is the alias of pc-1.0, and one is a type on its own.
Remember on Precise this looks like:
pc-1.0-precise Ubuntu 12.04 Standard PC (alias of pc-1.0-qemu-kvm)
pc-1.0-qemu-kvm Ubuntu 12.04 Standard PC (default)
pc Standard PC (alias of pc-1.0)
pc-1.0 Standard PC
Which one is it picking on migration?
This code for Trusty is at:
debian/patches/ubuntu/add-machine-type-pc-1.0-qemu-kvm-for-live-migrate-co.patch
And this is in since: 2.0.0+dfsg-2ubuntu1.6 due to LP: #1374612
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536331
Title:
Precise to Trusty live migration failing
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1536331/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
