Comment 21 for bug 1713490

I subscribed James and Corey as this might be special to Ubuntu Cloud Archive.
Maybe an upgrade path that we have missed?

@James/Corey - do you see that as well?

@Christian Z. - what version of qemu was installed when failing?

Overall this looks like the ipxe from Bionic in the cloud archive for Xenial.
@James - does the UCA for B-to-X hold also a source of ipxe-qemu-256k-compat-efi-roms?
@James - does the qemu in UCA for B-to-X has [1] and [2]?

https://salsa.debian.org/qemu-team/qemu/commit/7b917f26ac6a224195f68088dcd8e8f99d932675
https://salsa.debian.org/qemu-team/qemu/commit/6409970b59979c6b0a80222d168956fc9867cac4

Overall what should happen is that
- if you had only the older qemu installed then guests used the old ipxe roms and got defined as pre 2.10 machine
- on a migration to a newer system (and Xenial + UCA copied from Bionic counts as new) it would detect that it is an old type and use the compat roms (matching old size for allocation)
- migration should work
- but the report says that is not true, hmm - needs more details

@Christian Z - could you share a "virsh dumpxml" of one of the guests (on the source) that fails to migrate?