From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Starting multiple domains at boot?
Date: Thu, 08 Apr 2010 21:32:53 -0700
Message-ID: <4BBEADF5.1010007@goop.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Keir Fraser <keir.fraser@eu.citrix.com>, Ian Campbell <Ian.Campbell@citrix.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

Is there any fundimental reason why we can't support starting multiple
domains at boot?  For example, having something like:

title Xen
        root (hd0,1)
        kernel /xen.gz
        module /vmlinuz-dom0
        module /initrd-dom0.img
	module /some-other-domain
	module /other-domains-initrd.img
	module ...
	module ...


(For simplicity's sake, I'd assume that domains are always (kernel,
initrd) pairs, but one could imagine doing something like content
sniffing or magic module parameters ("xen:kernel", "xen:initrd") to
distinguish the module's roles.)

Has someone already done this?

It seems like it would be a straightforward way to deal with essential
early service domains (like a xenstore domain, for example).

Thanks,
    J