From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Han, Huaitong" <huaitong.han@intel.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Does Xen support nested VM migration
Date: Wed, 01 Jul 2015 08:50:23 +0100 [thread overview]
Message-ID: <55939BBF.6010300@citrix.com> (raw)
In-Reply-To: <1435718964.3287.17.camel@huaitong-MOBL.ccr.corp.intel.com>
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?
> Does Xen support the operation? I guess the nestedvm migration feature
> is not at all implemented.
Nested virtualisation is still experimental, and there are areas with
known issues, and scenarios which I expect have never been tried.
Having said that, there is nothing I am of with migration which I would
expect to break or need further fixing in a nested scenario.
~Andrew
next prev parent reply other threads:[~2015-07-01 7:50 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 [this message]
2015-07-01 8:56 ` Han, Huaitong
2015-07-01 9:58 ` Andrew Cooper
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=55939BBF.6010300@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.