From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@bugzilla.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
Message-ID:
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8BIT
To: kvm@kernel.org
Return-path:
Received: from mail.wl.linuxfoundation.org ([198.145.29.98]:40808 "EHLO
mail.wl.linuxfoundation.org" rhost-flags-OK-OK-OK-OK)
by vger.kernel.org with ESMTP id S1751878AbeBHMHN (ORCPT
); Thu, 8 Feb 2018 07:07:13 -0500
Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1])
by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 99EB7294C0
for ; Thu, 8 Feb 2018 12:07:12 +0000 (UTC)
In-Reply-To:
Sender: kvm-owner@vger.kernel.org
List-ID:
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.