kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@kernel.org
Subject: [Bug 198621] KVM Guest panics when running own guest, while being live migrated
Date: Thu, 08 Feb 2018 11:59:18 +0000	[thread overview]
Message-ID: <bug-198621-28872-Md9jho9CAN@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-198621-28872@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=198621

Kashyap Chamarthy (kashyap.cv@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kashyap.cv@gmail.com

--- Comment #3 from Kashyap Chamarthy (kashyap.cv@gmail.com) ---
(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.

  parent reply	other threads:[~2018-02-08 11:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-31 11:03 [Bug 198621] New: KVM Guest panics when running own guest, while being live migrated bugzilla-daemon
2018-02-02 15:41 ` [Bug 198621] " bugzilla-daemon
2018-02-08  8:25 ` bugzilla-daemon
2018-02-08 11:59 ` bugzilla-daemon [this message]
2018-02-08 12:07 ` bugzilla-daemon
2018-02-09  8:11 ` bugzilla-daemon
2018-02-12 14:05 ` bugzilla-daemon
2018-02-15  9:44 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-198621-28872-Md9jho9CAN@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=kvm@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).