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] VM reboot ?

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] VM reboot ?
From: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Date: Tue, 14 Oct 2003 08:50:19 +0100
Cc: Nicolas Bougues <nbougues-listes@xxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxxx, Ian.Pratt@xxxxxxxxxxxx
Delivery-date: Tue, 14 Oct 2003 08:51:27 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: Your message of "Tue, 14 Oct 2003 08:19:45 BST." <E1A9JT7-0005jD-00@xxxxxxxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
> > I've not solved my VBD problems, but I realized that NFS mounting is a
> > better way somehow.
> > 
> > Now I'm wondering if it's possible to have a domain reboot/restart
> > itself without domain 0 intervention. Right now, when I reboot a non 0
> > domain, it basically turns if off and makes it disappear.
> No, that's not supported at the moment, although it probably wouldn't
> be that hard to implement. 

There's various ways we could do this, but because the kernel
needs re-loading, it is going to require intervention from the
domain 0 user space xi_build tool.

The easiest way is probably to 'sleep' domains that exit with a
reboot code (rather than a halt code), and then somehow signal
domain 0 that is should re-run xi_build with the same arguments,
and then wake the domain. This way, we get to keep the same
memory allocation, scheduling parameters, VBDs and physical

We should keep this sort of thing in mind when discussing the
redesign of the xenctl tools.


This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
Xen-devel mailing list

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