As it turns out, it's a bit more complicated to perform the verification
on Oracular.
First, if we generate a migratable XML definition while running Noble
and then upgrade to Oracular, "virsh migrate" won't accept that
definition anymore exactly because of how the <cpu> is defined.
If we then regenerate the XML definition (which I believe is what every
should will/should do in this case), the new definition won't have the
same problem because <cpu> defaults to "host-model". This is actually
part of one of the attempts to fix these migration issues that have been
affecting libvirt for a while; upstream decided to simplify the
generation of the migratable XML. If you look at how the initial
domain.xml is laid out, you will see:
...
<cpu mode="host-model" match="exact">
<topology sockets="2" cores="1" threads="1"/>
</cpu>
...
which is exactly what Oracular's libvirt generates with "virsh dumpxml
--migratable".
Having said all that, I performed the following tests:
1) Migrate the VM from Oracular to Noble, using Oracular's libvirt from
proposed. OK.
2) Migrate the VM from Oracular to Oracular, also using libvirt from
proposed. OK.
Therefore, I'm considering this as verified.
** Tags removed: verification-needed verification-needed-oracular
** Tags added: verification-done verification-done-oracular
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083986
Title:
Live migration fails because VMX features are missing on target cpu
definition
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2083986/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
