Hypervisor Migration

Hypervisor Migration

[emdel]

[-- Attachment #1.1: Type: text/plain, Size: 201 bytes --]

Hello guys,
I would like to have some information (slides/paper) about "hypervisor
migration".
Is it supported by Xen?
Can someone point me out where to look in the source code?


Cheers,



--
/emdel

[-- Attachment #1.2: Type: text/html, Size: 357 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: Hypervisor Migration

[George Dunlap]

On Tue, Jul 16, 2013 at 10:57 AM, emdel <emdel@playhack.net> wrote:
> Hello guys,
> I would like to have some information (slides/paper) about "hypervisor
> migration".
> Is it supported by Xen?
> Can someone point me out where to look in the source code?

What do you mean by 'hypervisor migration'?  And at the risk of
sounding rude, have you tried Google?

 -George

Re: Hypervisor Migration

[emdel]

[-- Attachment #1.1: Type: text/plain, Size: 752 bytes --]

On Wed, Jul 17, 2013 at 11:55 AM, George Dunlap <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.



> And at the risk of sounding rude, have you tried Google?


Yes you're right, I should have explained the concept before.
Googling for hypervisor migration I am only able to find how to migrate the
virtual machine from the hypervisor h to the hypervisor i.
This is different from my previous definition.

Cheers,

[-- Attachment #1.2: Type: text/html, Size: 1352 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: Hypervisor Migration

[Egger, Christoph]

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

Re: Hypervisor Migration

[emdel]

[-- Attachment #1.1: Type: text/plain, Size: 305 bytes --]

On Wed, Jul 17, 2013 at 3:12 PM, Egger, Christoph <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.

[-- Attachment #1.2: Type: text/html, Size: 726 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: Hypervisor Migration

[Egger, Christoph]

On 17.07.13 15: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.

I am not aware of anyone having tried this so far.
If you do we all are interested in your testing results
(both positive and negative ones).

Christoph

Re: Hypervisor Migration

[George Dunlap]

[-- 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

Re: Hypervisor Migration

[emdel]

[-- Attachment #1.1: Type: text/plain, Size: 969 bytes --]

On Wed, Jul 17, 2013 at 3:51 PM, George Dunlap
<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 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.

[-- Attachment #1.2: Type: text/html, Size: 2171 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: Hypervisor Migration

[Egger, Christoph]

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. 
> 
>