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 12:07:11 +0000	[thread overview]
Message-ID: <bug-198621-28872-kGZrq3MUNN@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-198621-28872@https.bugzilla.kernel.org/>

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

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

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2018-02-08 12:07 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
2018-02-08 12:07 ` bugzilla-daemon [this message]
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-kGZrq3MUNN@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).