From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Egger, Christoph" Subject: Re: Hypervisor Migration Date: Wed, 17 Jul 2013 15:12:48 +0200 Message-ID: <51E69850.1070706@amazon.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: emdel Cc: George Dunlap , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On 17.07.13 14:33, emdel wrote: > On Wed, Jul 17, 2013 at 11:55 AM, George Dunlap > > 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