From: Anthony Liguori <anthony@codemonkey.ws>
To: Steve Ofsthun <sofsthun@virtualiron.com>
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:07:14 -0500 [thread overview]
Message-ID: <467ADA72.7080701@codemonkey.ws> (raw)
In-Reply-To: <467ACDE8.8000907@virtualiron.com>
Steve Ofsthun wrote:
>> 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.
>
I suspect there are really two possible ways to go here:
1) Add generic support to mount blktap disks to QEMU via block-add in
dom0 and then apply your stuff to blktap.
2) Just enhance the VPC in QEMU to cover anything it doesn't now. That
doesn't really address blktap but that's the right thing to do from the
QEMU perspective.
Adding a second block-vhd to QEMU is really a bad idea from a
maintainability perspective. #1 is much better since it avoids that
problem.
Regards,
Anthony Liguori
>> 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
>
prev parent reply other threads:[~2007-06-21 20:07 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
2007-06-21 20:07 ` Anthony Liguori [this message]
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=467ADA72.7080701@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=berrange@redhat.com \
--cc=bguthro@virtualiron.com \
--cc=sofsthun@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.