From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Keir Fraser <keir.fraser@eu.citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>
Subject: Starting multiple domains at boot?
Date: Thu, 08 Apr 2010 21:32:53 -0700 [thread overview]
Message-ID: <4BBEADF5.1010007@goop.org> (raw)
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
next reply other threads:[~2010-04-09 4:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 4:32 Jeremy Fitzhardinge [this message]
2010-04-09 7:15 ` Starting multiple domains at boot? Keir Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BBEADF5.1010007@goop.org \
--to=jeremy@goop.org \
--cc=Ian.Campbell@citrix.com \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.