From: Jan Kiszka <jan.kiszka@siemens.com>
To: 缪天翔 <cwndmiao@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: nested migration issues
Date: Tue, 27 Aug 2013 11:18:45 +0200 [thread overview]
Message-ID: <521C6EF5.2060807@siemens.com> (raw)
In-Reply-To: <CAFtLEyF5Sc+ThmpPjcTLg71Cfh=XrRTsTr2ZJkp4_HK488eKGw@mail.gmail.com>
On 2013-08-27 10:29, 缪天翔 wrote:
> Hi all
>
> I am doing a research project similar to "Turtles" using the nested
> vmx feature of kvm. In detail, I launch a guest kvm (donated as L1) on
> the underlying kvm (donated as L0) and then set up a nested guest
> (donated as L2) upon the L1 guest kvm.
>
> The problem I come up with is that I want to migrate the whole L1
> guest kvm from source machine to target (that is keeping the L2 guest
> running normally). And this action causes the L2 kernl to panic.
>
> Can anybody tell me whether kvm supports this kind of nested migration
> or anybody is working on the relating field?
No, KVM does not support migration while nested VMX (or SVM) is enabled.
We lack userspace interfaces to export/import the required state, and
that mostly because we do not really know yet what state needs to be
made available. Specifically nVMX is still under development. Migration
support will officially follow once we feel we reached a mature state
with nesting support.
That said, if you want to play with adding such an interface yourself,
no one will stop you. It may serve as a reference for us what is
required, but you should not expect it to be merged soon.
BTW, not only migration is broken so far. Even reset does not work while
VMX is enabled. For the same reason: userspace cannot load a VCPU state
that resets all VMX states properly.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2013-08-27 9:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 8:29 nested migration issues 缪天翔
2013-08-27 9:18 ` Jan Kiszka [this message]
2013-08-27 12:02 ` Nadav Har'El
2013-08-27 13:38 ` Kashyap Chamarthy
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=521C6EF5.2060807@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=cwndmiao@gmail.com \
--cc=kvm@vger.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