WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: [PATCH 0/4] (Refactored) VHD Support Addition

To: Steve Ofsthun <sofsthun@xxxxxxxxxxxxxxx>
Subject: [Xen-devel] Re: [PATCH 0/4] (Refactored) VHD Support Addition
From: Anthony Liguori <anthony@xxxxxxxxxxxxx>
Date: Thu, 21 Jun 2007 15:07:14 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, "Daniel P. Berrange" <berrange@xxxxxxxxxx>, Ben Guthro <bguthro@xxxxxxxxxxxxxxx>
Delivery-date: Thu, 21 Jun 2007 13:05:17 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <467ACDE8.8000907@xxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <467AB504.7040809@xxxxxxxxxxxxxxx> <20070621173518.GE13026@xxxxxxxxxx> <467ABC1A.4010302@xxxxxxxxxxxxxxx> <467AC030.4030803@xxxxxxxxxxxxx> <467ACDE8.8000907@xxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.12 (X11/20070604)
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


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel