Re: Configuring domU filesystem image from dom0

[Robert Elz <kre%munnari.OZ.AU@localhost>]

    Date:        Wed, 29 Jun 2016 22:33:28 +0100
    From:        Alaric Snell-Pym <alaric%snell-pym.org.uk@localhost>
    Message-ID:  <0b2ad4da-a7f9-5661-80eb-1649cfc42a7b%snell-pym.org.uk@localhost>

  | Or should I use the entire LV as a filesystem for dom0's sake, and then
  | somehow tell the domU to treat it as such? "root on xbd0d" or similar?

I do (almost) exactly that for my test builds - I newfs a filesystem
(I don't use LVM, but just a GPT partition on a raid array) and mount
it, build,sh with TARGET=/the/mount/point and after that finishes, go
do the rest of the setup (MAKEDEV, copy config files into /etc ...)
unmount, and start a xen DomU using that device - with root on xbd0a

But I'd only do it that way for test systems I only want to run for
long enough for them to build themselves (kind of proof that the system
works - if it is good enough to build itself, and that system also runs,
then generally it is good enough to use).

For real systems, I either do it via the standard install procedure, or
just make multiple partitions (multiple LV's in your case) - there's no
reason you need to be limited to one.   The Xen DomU client just gets
multiple xbdN's to use (so you end up using xbd0a xbd1a xbd2a rather than
xbd0a xbd0b ...)

kre