Comment 13 for bug 1536331

I tried setting pc-1.0 on the migration source as type as suggested by Serge.
But that didn't get it running for me with the current 14.30 verison.
Doing so with 1.0+noroms-0ubuntu14.18 on built locally and inserted into the test container.
But I still see the same migration failure - default machien types look the same as with 14.30.
I spawned "new" guests on 14.18 with default pc-1.0-qemu-kvm and pc-1.0 - but all those failed as well.

Then as Serge I also tried rebuilding qemu on Trusty without that double alias.
Still having 14.18 on the source I tried to migrate all three guests I had already (created with 14.30 modified to pc-1.0, created with 14.18 and created as pc-1.0 with 14.18) again, but they all fail.

I wanted to make sure my overall setup at least worked with the last known good states.
And last good state is what was published for bug 1374612.
P: 1.0+noroms-0ubuntu14.18
T: 2.0.0+dfsg-2ubuntu1.6
To ensure we cover all qemu packages installed with:
apt-get install $(dpkg -l '*qemu*' | awk '/ii qemu/ {printf("%s=2.0.0+dfsg-2ubuntu1.6 ", $2)}')
apt-get install $(dpkg -l '*qemu*' | awk '/ii qemu/ {printf("%s=1.0+noroms-0ubuntu14.18 ", $2)}')
That would be exactly the combination that the old bug was verified with.
But even that was failing as well for me.

To round things up I checked which libvirt versions where active back then and prepared matching old libvirt packages as well.
P: 0.9.8-2ubuntu17.19
T: 1.2.2-0ubuntu13.1.6
Note: has to be build with DEB_BUILD_OPTIONS="nocheck" these days.
apt-get install $(dpkg -l '*libvirt*' | awk '/ii libvirt/ {printf("%s=0.9.8-2ubuntu17.19 ", $2)}')
apt-get install $(dpkg -l '*libvirt*' | awk '/ii libvirt/ {printf("%s=1.2.2-0ubuntu13.1.6 ", $2)}')
This still failed to migrate any of my three guests.

I was afraid I might miss something obvious and checked my setup once more.
And I was right and found that kvm-ipxe-precise is not installed as it is only a suggest on Trusty.
That could explain my failures, trying with that installed next.