From: Paul Brook <paul@codesourcery.com>
To: "Jim C. Brown" <jma5@umd.edu>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] using partition images
Date: Mon, 8 May 2006 15:28:31 +0100 [thread overview]
Message-ID: <200605081528.32129.paul@codesourcery.com> (raw)
In-Reply-To: <20060508141911.GA2869@jbrown.mylinuxbox.org>
On Monday 08 May 2006 15:19, Jim C. Brown wrote:
> On Mon, May 08, 2006 at 02:11:36PM +0100, Paul Brook wrote:
> > > I'll work on this tonight. I've been thinking about doing this, since
> > > it would allow one to use any qemu-supported disk image format as a
> > > partition image.
> > >
> > > I can't think of any disk format that's heavily used in qemu that is
> > > normally used for partition images except for raw. OTOH it might be
> > > interesting to have qcow partition images.
> >
> > If done properly this should also allow use of vmware split image files.
>
> It'd probably be easier to fix the vmdk driver to handle these natively.
>
> If split vmdks are just a series of partition images plus an image of an
> MBR/partition table then it may be possible to hack this up via a partition
> driver that supported harddisk sharing (using multiple partition images as
> part of the same hard disk).
I think you should be aiming for a generic composite device block driver.
Then write a fake MBR block device (or whatever you want to call it).
To use a single partition you create a composite device consisting of the fake
mbr and the raw partition.
A vmware split image file is just a composite of several raw images with a
funny config file.
Paul
next prev parent reply other threads:[~2006-05-08 14:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-08 3:53 [Qemu-devel] using partition images Jim C. Brown
2006-05-08 4:49 ` Jim C. Brown
2006-05-08 10:20 ` Fabrice Bellard
2006-05-08 12:26 ` Jim C. Brown
2006-05-08 12:32 ` Johannes Schindelin
2006-05-08 13:11 ` Paul Brook
2006-05-08 14:19 ` Jim C. Brown
2006-05-08 14:28 ` Paul Brook [this message]
2006-05-08 14:59 ` Jim C. Brown
2006-05-08 15:09 ` Paul Brook
2006-05-08 14:49 ` Jim C. Brown
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=200605081528.32129.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=jma5@umd.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).