From: Steve Ofsthun <sofsthun@virtualiron.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: xen-devel@lists.xensource.com,
"Daniel P. Berrange" <berrange@redhat.com>,
Ben Guthro <bguthro@virtualiron.com>
Subject: Re: [PATCH 0/4] (Refactored) VHD Support Addition
Date: Thu, 21 Jun 2007 15:13:44 -0400 [thread overview]
Message-ID: <467ACDE8.8000907@virtualiron.com> (raw)
In-Reply-To: <467AC030.4030803@codemonkey.ws>
Anthony Liguori wrote:
> Steve Ofsthun wrote:
>> Daniel P. Berrange wrote:
>>> On Thu, Jun 21, 2007 at 01:27:32PM -0400, Ben Guthro wrote:
>>
>>>> ### 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 :-(
>>
>> Well, when we started this, it wasn't clear we were going to be able to
>> publicly release any code in support of the VHD format. Microsoft later
>> relaxed the restrictions, and by that time the separate tool already
>> existed. We can investigate integrating the work into qemu-img.
>
> QEMU already supports VHD (it calls it VPC) and supported it long before
> Microsoft released any specs. QEMU supported VMDK before VMware release
> the specs for that too.
This code was developed in the Xen 3.0.2 days when the integrated qemu had
no vpc support. Our original code was targeted at PV on HVM drivers using
blocktap. We needed to support the same format unaccelerated and so the
qemu integration was also done.
> Is there a particular feature of VHD/VPC that your code adds that QEMU
> didn't already support?
Not having any experience with VPC, I couldn't tell you. I can say that we
tried to adhere to the Microsoft spec rather than reverse engineering the
format from examples. Perusing the VPC code, there are many references to
unknown fields within the format.
Is there a complete and concise summary of the VPC feature coverage?
Thanks,
Steve
--
Steve Ofsthun - Virtual Iron Software, Inc.
next prev parent reply other threads:[~2007-06-21 19:13 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
2007-06-21 17:57 ` Steve Ofsthun
2007-06-21 18:15 ` Anthony Liguori
2007-06-21 19:13 ` Steve Ofsthun [this message]
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=467ACDE8.8000907@virtualiron.com \
--to=sofsthun@virtualiron.com \
--cc=anthony@codemonkey.ws \
--cc=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.