* Re: [Xen-devel] accessing loopback filesystem+partitions on a file
[not found] ` <200506290233.05922.mark.williamson@cl.cam.ac.uk>
@ 2005-06-29 2:33 ` Luke Kenneth Casson Leighton
0 siblings, 0 replies; only message in thread
From: Luke Kenneth Casson Leighton @ 2005-06-29 2:33 UTC (permalink / raw)
To: Mark Williamson; +Cc: xen-devel, linux-kernel
EXCELLENT. thank you.
On Wed, Jun 29, 2005 at 02:33:05AM +0100, Mark Williamson wrote:
> > i'm sort-of helping test a xen install project where a
> > block device is presented as the DRIVE - not, i repeat
> > not, the partitions on the drive which is the quotes
> > normal quotes way of doing xen installes
> >
> > (yes there are good reasons for doing this).
>
> That's fine. It's something that (is supposed to) works.
yep. it does.
> > * how the hell do you loopback mount (or lvm mount
> > or _anything_! something!) partitions that have
> > been created in a loopback'd file!!!!
>
>
> You could work out where the partitions are, then use hexedit... woops! just
> kidding ;-)
>
> This has come up before but it's easier to find the list entries when you
> remember what you're looking for ;-)
>
> There's a patch by NASA (of all people!) that enables the Linux loopback
> driver to support partitions:
> ftp://ftp.hq.nasa.gov/pub/ig/ccd/enhanced_loopback/readme.txt
*curious* - why haven't these mods been merged back yet?
> There's also the "lomount" utility from QEmu:
> http://www.dad-answers.com/qemu/utilities/QEMU-HD-Mounter/lomount/
> Which works out where partitions are and mounts them (no kernel mods needed).
_great_.
> Apparently kpartx (from the multipath tools -
> http://christophe.varoqui.free.fr/wiki/wakka.php?wiki=Home) can use the
> device mapper to create block devices for each partition.
>
> I think I'd go with lomount, as it looks easiest.
okay.
question for you.
would there be any reason (e.g. performance increase)
which could justify providing the block device remapping
facility at the linux device driver level instead of in
xen's fun-and-games?
the non-technical (but aesthetic) justification is that
xen provides the facility to represent block devices
(major+minor) for use as generic block devices _anyway_ -
just in a rather roundabout (and exclusionary i.e.
"unfair!! i wanna play!!") manner.
l.
p.s. mark, what the hell are _you_ doing up at 3am??? :)
^ permalink raw reply [flat|nested] only message in thread