From: "Egger, Christoph" <chegger@amazon.de>
To: emdel <emdel@playhack.net>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Hypervisor Migration
Date: Wed, 17 Jul 2013 16:32:16 +0200 [thread overview]
Message-ID: <51E6AAF0.2040808@amazon.de> (raw)
In-Reply-To: <CALKiAsGi=1AbWOtcNuEun_K-NTB3tpToGz8zVpBQguPEH9Vuig@mail.gmail.com>
On 17.07.13 16:12, emdel wrote:
> On Wed, Jul 17, 2013 at 3:51 PM, George Dunlap
> <george.dunlap@eu.citrix.com <mailto:george.dunlap@eu.citrix.com>> wrote:
>
> 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?
>
>
> The second situation, thus I want to migrate the hypervisor itself from
> running on bare metal to running in a VM.
I cannot imagine how this should work as the Xen hypervisor itself is
what you boot on machine m.
I can imagine that you launch a xen hypervisor as guest hypervisor
on machine n and then migrate all guests from m to n.i.
Christoph
>
>
> 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 have Intel machines so I am interested in the Intel architecture.
> Is the Intel work public? I would like to have a look.
> I'm more interested in Xen-on-Xen even if Xen-on-metal is cool as well.
>
>
>
> 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.
>
>
> Ok good to know. Maybe it's because the nested support was sperimental
> and there are no useful application so far.
>
>
prev parent reply other threads:[~2013-07-17 14:32 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
2013-07-17 14:12 ` emdel
2013-07-17 14:32 ` Egger, Christoph [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=51E6AAF0.2040808@amazon.de \
--to=chegger@amazon.de \
--cc=emdel@playhack.net \
--cc=george.dunlap@eu.citrix.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 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).