Phew, after some time lost fiddling with LXD, I was finally able to
reproduce the problem manually.
I usually rely on a special LXD profile to make containers able to run
VMs, but this bug does not reproduce under this scenario. Despite
taking me a long time to find that out, it's something important to know
because our current QEMU/libvirt migration testsuite relies on the same
trick to test migrations across instances. This is actually the reason
why this bug hasn't been caught before (I've been wondering about that
myself, since I run the testsuite before making uploads to the archive).
Anyway, with that out of the way, I'm able to start investigating the
what's going on. It's late now, and I haven't tested Oracular/Plucky
(thanks gboutry for testing Oracular, btw!), but I'd still like to do
that in order to pinpoint the exact fix.
I'll post more updates next week, when I resume working on this.
Thanks.
** Also affects: libvirt (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu Noble)
Status: New => Triaged
** Changed in: libvirt (Ubuntu Noble)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
--
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
