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
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
On 09/04/2010 05:32, "Jeremy Fitzhardinge" <jeremy@goop.org> wrote:> (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).It''s been thought about at various times in the past. I''m not sure it''s better than having an initial stubdom do it. But either way, discussions have never led to actual finished patches. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel