Bug 198621
| Summary: | KVM Guest panics when running own guest, while being live migrated | ||
|---|---|---|---|
| Product: | Virtualization | Reporter: | Dennis (dennis) |
| Component: | kvm | Assignee: | virtualization_kvm |
| Status: | NEW --- | ||
| Severity: | normal | CC: | christian.rohmann, david, florian, kashyap.cv |
| Priority: | P1 | ||
| Hardware: | Intel | ||
| OS: | Linux | ||
| Kernel Version: | 4.15.0-rc9 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Bug Depends on: | 53851 | ||
| Bug Blocks: | |||
|
Description
Dennis
2018-01-31 11:03:52 UTC
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. Taking the liberty to cross-reference a related discussion on the libvirt mailing list: https://www.redhat.com/archives/libvirt-users/2018-February/msg00014.html (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 (In reply to Kashyap Chamarthy from comment #3) > (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). Ah, hang on -- I should actually double-read the original bug description. The original bug description is takking about migrating the *L1* (while L2 is running on it) to a destination L0 hypervisor. So I admit: I haven't yet migrated the L1 guest while L2 is running on it. (My earlier comment only talks about migrating L2 guest to a destination L1.) Some documentation on the limitations associated with nested guests can now be found here: https://www.linux-kvm.org/page/Nested_Guests https://www.linux-kvm.org/page/Migration#Problems_.2F_Todo |