All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Ben Guthro <bguthro@virtualiron.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH 0/4] (Refactored) VHD Support Addition
Date: Thu, 21 Jun 2007 18:35:18 +0100	[thread overview]
Message-ID: <20070621173518.GE13026@redhat.com> (raw)
In-Reply-To: <467AB504.7040809@virtualiron.com>

On Thu, Jun 21, 2007 at 01:27:32PM -0400, Ben Guthro wrote:
> [PATCH 0/4] (Refactored) VHD Support addition
> The patches that follow implement Microsoft's VHD format support, and
> apply to xen-unstable.hg CS 15414:3827b12d24dd
> Per Mark McLoughlin's suggestions - these have been reworked to use the 
> tapaio wrapper.
> 
> This is based on the VHD format spec covered by Microsoft's "Open
> Specification Promise":
> http://www.microsoft.com/interop/osp/default.mspx
> MS VHD Spec can be found at the following link:
> http://download.microsoft.com/download/f/f/e/ffef50a5-07dd-4cf8-aaa3-442c0673a029/Virtual%20Hard%20Disk%20Format%20Spec_10_18_06.doc
> 
> It is divided up into the following patches:
> qemu-vhd-support.patch        [1/4]
> tapdisk-vhd-support.patch     [2/4]
> blktap-fixes.patch            [3/4]
> vdisk-support.patch           [4/4]
> 
> ### libvdisk ####
> These patches implement a shared library (libvdisk) between qemu, and
> blktap which can be expanded upon for additional formats in the future.
> This was done in order to avoid code duplcation between the two areas.
> At this time, it only supports the vhd format.
> 
> ### vdisk_tool ###
> The vdisk_tool provides a means of creating, and converting vhd files.
> Like libvdisk, it is designed with future support of additional formats
> in mind, but currently only supports vhd.

Why not just add vhd support to qemu's existing qemu-img tool, then it will
support all image formats, right from the start, rather than inventing yet
another tool :-(

Any changes to QEMU should be sent to the QEMU upstream mailing lists for
review/inclusion too, otherwise the Xen fork gets even worse than it 
already is

Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

  parent reply	other threads:[~2007-06-21 17:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-21 17:27 [PATCH 0/4] (Refactored) VHD Support Addition Ben Guthro
2007-06-21 17:32 ` Ben Guthro
2007-06-21 17:35 ` Daniel P. Berrange [this message]
2007-06-21 17:57   ` Steve Ofsthun
2007-06-21 18:15     ` Anthony Liguori
2007-06-21 19:13       ` Steve Ofsthun
2007-06-21 20:07         ` Anthony Liguori

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=20070621173518.GE13026@redhat.com \
    --to=berrange@redhat.com \
    --cc=bguthro@virtualiron.com \
    --cc=xen-devel@lists.xensource.com \
    /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.