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 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
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
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, _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
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
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. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
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
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 --------------000608090005010106010900 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: 8bit <html> <head> <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> <div class="moz-cite-prefix">On 17/07/13 14:23, emdel wrote:<br> </div> <blockquote cite="mid:CALKiAsHO1r7x4YCWVvzYZnk9cwU-a6-zLT5ovs0dhW9S1q6-CA@mail.gmail.com" type="cite"> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <div dir="ltr"> <div class="gmail_extra">On Wed, Jul 17, 2013 at 3:12 PM, Egger, Christoph <span dir="ltr"><<a moz-do-not-send="true" href="mailto:chegger@amazon.de" target="_blank">chegger@amazon.de</a>></span> wrote:<br> <div class="gmail_quote"> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">So let me draw a picture. If it is correct then that means on machine n<br> hypervisor i must support nested virtualization.<br> </blockquote> </div> <br> </div> <div class="gmail_extra">Exactly. The hypervisor i must support nested virtualization.</div> <div class="gmail_extra">Your picture is exactly what I mean.</div> </div> </blockquote> <br> 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?<br> <br> 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.<br> <br> 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.<br> <br> -G<br> </body> </html> --------------000608090005010106010900-- --===============4769673209951230607=Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============4769673209951230607==--
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. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
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. > >