xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
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 15:12:48 +0200	[thread overview]
Message-ID: <51E69850.1070706@amazon.de> (raw)
In-Reply-To: <CALKiAsGgdWv2T4Cu+XNzDyB4FfmrCFSvNFLFqx0FD53Cnbj4cw@mail.gmail.com>

On 17.07.13 14:33, emdel wrote:
> On Wed, Jul 17, 2013 at 11:55 AM, George Dunlap
> <George.Dunlap@eu.citrix.com <mailto:George.Dunlap@eu.citrix.com>> wrote:
> 
>     What do you mean by 'hypervisor migration'?  
> 
> 
> Hi George, 
> hypervisor migration for me is the following scenario:
> imagine a machine m running an hypervisor h with N guests. You want to
> migrate this situation on a machine n running an hypervisor i.
> On top of the hypervisor i you will have the hypervisor h with its N
> guests. I hope it's clear now.

So let me draw a picture. If it is correct then that means on machine n
hypervisor i must support nested virtualization.


machine m:


   guest 1   guest 2   guest N
     |         |          |
     +---------+----------+
               |
            hypervisor h


machine n:

   guest 1   guest 2   guest N
     |         |          |
     +---------+----------+
               |
            hypervisor h        guest X  guest Y
               |                   |        |
               +-------------------+--------+
                         |
                     hypervisor i


Christoph

  reply	other threads:[~2013-07-17 13:12 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 [this message]
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

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=51E69850.1070706@amazon.de \
    --to=chegger@amazon.de \
    --cc=George.Dunlap@eu.citrix.com \
    --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).