This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Migrate linux to run on Xen

To: "limin.hust" <limin.hust@xxxxxxxxx>
Subject: Re: [Xen-devel] Migrate linux to run on Xen
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Fri, 20 Nov 2009 11:59:59 +0800
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 19 Nov 2009 20:02:01 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <200911182106142810210@xxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <200911182106142810210@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20091014 Fedora/3.0-2.8.b4.fc11 Lightning/1.0pre Thunderbird/3.0b4
On 11/18/09 21:06, limin.hust wrote:
> Recently i was studying the case, for example:
> (1)linux is running on the native hardware
> (2)suspend linux to ram
> (3)fast boot Xen with kexec system call(without hardware reset)
> (4)resume the linux from the suspended linux image.
> I have known how to do the fisrt three steps, but the last and i think
> is the hardest, i still can't figure out how to deal with it.
> Is there any suggestions to my case, i would really appreciate that.

This is difficult because Linux will get very confused if its apparent
hardware platform changes spontaneously under it.  Assuming you start it
as an HVM domain, all the hardware will change from the native hosts to
the qemu emulated hardware (which is almost certainly not like your
physical hardware).

You might be able to get it to work by somehow arranging that the kernel
hot-unplug all its hardware before resume, then generating hot-plug
events for all the new hardware on resume, but I suspect that won't work
(for example, in-use can't be replaced on the fly like this).


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>