qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Jim C. Brown" <jma5@umd.edu>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] using partition images
Date: Mon, 8 May 2006 10:59:12 -0400	[thread overview]
Message-ID: <20060508145912.GA7690@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <200605081528.32129.paul@codesourcery.com>

On Mon, May 08, 2006 at 03:28:31PM +0100, Paul Brook wrote:
> > 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.

I'm not sure if it's worth it to make the fake MBR its own block device.

Since we're going to need configurable options anyways, it might be possible
to specify how the MBR should be handled. E.g.

-hda multipart:mbr:fake:part1:/usr/images/hda1.img:part1sysid:0xc:part2:fat:floppy:/usr/images/tools:part2sysid:0x6

would handle the current faking of the mbr using bootmbr.bin and autogenerated
partition table, while

-hda multipart:mbr:file:/usr/images/vmdk-mbr.vmdk:part1:/usr/images/hda1.vmdk:part2:/usr/images/hda2.vmdk

would allow for having the mbr as a separate file. And even

-hda multipart:mbr:part1:part1:/usr/images/hda1.vmdk:part2:/usr/images/hda2.vmdk

which would specify that hda1.vmdk has the mbr and partition table prepended to it.

The syntax is getting kinda ugly though. Anthony suggested that we use mini-config
files with all the options and just pass those to -hda (e.g. -hda multipart:hda.config)

> 
> A vmware split image file is just a composite of several raw images with a 
> funny config file.

It'd still be nice if the vmware driver had support for using those config files
instead of requiring a user to type this out by hand.

I guess qemu-img could have an option to convert those config files into qemu
multipart/composite harddisk image configs.

> 
> Paul
> 

-- 
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.

  reply	other threads:[~2006-05-08 14:59 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
2006-05-08 14:59             ` Jim C. Brown [this message]
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=20060508145912.GA7690@jbrown.mylinuxbox.org \
    --to=jma5@umd.edu \
    --cc=paul@codesourcery.com \
    --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).