https://bugzilla.kernel.org/show_bug.cgi?id=198621 Kashyap Chamarthy (kashyap.cv@xxxxxxxxx) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kashyap.cv@xxxxxxxxx --- Comment #3 from Kashyap Chamarthy (kashyap.cv@xxxxxxxxx) --- (In reply to David Hildenbrand from comment #1) > There is no support for nVMX migration yet. So trying to migrate a guest > while it is using VMX itself is expected to fail. > > Some people are currently working on this. Especially to > - Migrate the nVMX state > - Properly add and indicate VMX features in the CPU model to guarantee that > no VMX features will be lost during migration. Hmm, interesting. FWIW, I was able to successfully migrate L2 guest to the destination L1 guest (hypervisor). My full QEMU command-lines for both L1s and L2 are here: https://kashyapc.fedorapeople.org/virt/Migrate-a-nested-guest-08Feb2018.txt With the below versions: L0: $ uname -r; qemu-system-x86_64 --version; rpm -q libvirt-daemon-kvm 4.13.13-300.fc27.x86_64+debug QEMU emulator version 2.11.0(qemu-2.11.0-4.fc27) Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers libvirt-daemon-kvm-3.10.0-2.fc27.x86_64 On both source and destination L1s: $ uname -r; qemu-system-x86_64 --version; rpm -q libvirt-daemon-kvm 4.14.16-200.fc26.x86_64 QEMU emulator version 2.10.0(qemu-2.10.0-4.fc26) Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers libvirt-daemon-kvm-3.7.0-2.fc26.x86_64 -- You are receiving this mail because: You are watching the assignee of the bug.
