From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Han, Huaitong" <huaitong.han@intel.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Does Xen support nested VM migration
Date: Wed, 1 Jul 2015 10:58:57 +0100 [thread overview]
Message-ID: <5593B9E1.7080108@citrix.com> (raw)
In-Reply-To: <1435740948.5710.22.camel@huaitong-MOBL.ccr.corp.intel.com>
On 01/07/15 09:56, Han, Huaitong wrote:
> On Wed, 2015-07-01 at 08:50 +0100, Andrew Cooper wrote:
>> On 01/07/2015 03:49, Han, Huaitong wrote:
>>> Hi, all,
>>>
>>> When I create a L1 guest with nestedhvm=1, and create a L2 guest in L1
>>> guest, then migrate L1 guest, but the operation fails, and I find the
>>> bugfix requires a lot of work.
>> Fails in what way?
> The xen hypervisor in L1 guest has execute "vmxon" and
> nvmx->vmxon_region_pa get the value, after L1 migration, vmxon impact is
> lost and nvmx->vmxon_region_pa==0 , when L2 guest has some operation
> like VMREAD or VMWRITE, vmx_inst_check_privilege will return 1, and L1
> guest maybe hang or panic.
Ah yes - I remember this now. I raised it as a concern about a year ago
when rewriting migration and finding no information along these lines in
the migration stream.
To support this, you will need to add a new per-vcpu record in the
hypervisor migration stream which sends the VMX architectural state from
the source to the destination.
~Andrew
prev parent reply other threads:[~2015-07-01 9:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 2:49 Does Xen support nested VM migration Han, Huaitong
2015-07-01 7:50 ` Andrew Cooper
2015-07-01 8:56 ` Han, Huaitong
2015-07-01 9:58 ` Andrew Cooper [this message]
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=5593B9E1.7080108@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=huaitong.han@intel.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.