From: Douglas McClendon <dmc@filteredperception.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] block composite driver and partition driver
Date: Tue, 30 Jan 2007 16:28:26 -0600 [thread overview]
Message-ID: <45BFC68A.5010704@filteredperception.org> (raw)
In-Reply-To: <20070130112442.BVE66081@po0.mail.umd.edu>
jma5@umd.edu wrote:
> I've finally gotten around to working on my multipart driver again.
Why? I'm new to the list. Can you elaborate what sorts of things this
would be used for? I haven't yet gotten around to writing my per device
snapshot enablable/specifiable COW tmpfiles patch. But your code, while
I have no clue how it might be used, seems like it might interrelate
with that (or if not, I'm still curious).
-dmc
>
> block-composite.c is the basic low level composite image format, which lets you
> use a bunch of disk images as a single image.
>
> block-ram.c is a ram block device, with the size of the "image" given in the
> number of disk sectors.
>
> block-partition.c is a partition block device that uses the composite driver
> to combine partitions together along with a fake mbr that it generates and
> stores inside of a ram block device. (It doesn't work yet - for some reason the
> number of cylinders being reported to the guest OS is 0.)
>
> --
> Infinite complexity begets infinite beauty.
> Infinite precision begets infinite perfection.
>
next prev parent reply other threads:[~2007-01-30 22:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-30 16:24 [Qemu-devel] block composite driver and partition driver jma5
2007-01-30 22:28 ` Douglas McClendon [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-01-31 5:26 jbrown105
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=45BFC68A.5010704@filteredperception.org \
--to=dmc@filteredperception.org \
--cc=qemu-devel@nongnu.org \
/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.