From: George Dunlap <george.dunlap@eu.citrix.com>
To: emdel <emdel@playhack.net>
Cc: "Egger, Christoph" <chegger@amazon.de>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Hypervisor Migration
Date: Wed, 17 Jul 2013 14:51:09 +0100 [thread overview]
Message-ID: <51E6A14D.4070801@eu.citrix.com> (raw)
In-Reply-To: <CALKiAsHO1r7x4YCWVvzYZnk9cwU-a6-zLT5ovs0dhW9S1q6-CA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 837 bytes --]
On 17/07/13 14:23, emdel wrote:
> On Wed, Jul 17, 2013 at 3:12 PM, Egger, Christoph <chegger@amazon.de
> <mailto:chegger@amazon.de>> wrote:
>
> So let me draw a picture. If it is correct then that means on
> machine n
> hypervisor i must support nested virtualization.
>
>
> Exactly. The hypervisor i must support nested virtualization.
> Your picture is exactly what I mean.
Do you mean you want to migrate the guests from m.h to n.i.h? Or do you
mean you want to migrate the hypervisor itself from running on bare
metal to running in a VM?
I think the Intel guys have been looking at the first (migrating a VM
running on Xen-on-metal to Xen-on-Xen). Not sure about AMD.
I don't think anyone has tried the second even with a normal operating
system, much less a hypervisor with things running on top of it.
-G
[-- Attachment #1.2: Type: text/html, Size: 1859 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-07-17 13:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 9:57 Hypervisor Migration emdel
2013-07-17 9:55 ` George Dunlap
2013-07-17 12:33 ` emdel
2013-07-17 13:12 ` Egger, Christoph
2013-07-17 13:23 ` emdel
2013-07-17 13:31 ` Egger, Christoph
2013-07-17 13:51 ` George Dunlap [this message]
2013-07-17 14:12 ` emdel
2013-07-17 14:32 ` Egger, Christoph
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=51E6A14D.4070801@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=chegger@amazon.de \
--cc=emdel@playhack.net \
--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 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).