From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Jackson Subject: Re: hi Date: Tue, 27 May 2008 11:12:21 +0100 Message-ID: <18491.56965.341284.138748@mariner.uk.xensource.com> References: <1e16a9ed0805230834x4117314bu2b81e6ecd6fdc2d6@mail.gmail.com> <4836E518.2000508@virtualiron.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4836E518.2000508@virtualiron.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ben Guthro Cc: deshantm@gmail.com, xen-devel@lists.xensource.com, Vikram Singh List-Id: xen-devel@lists.xenproject.org Ben Guthro writes ("Re: [Xen-devel] hi"): From the discussions - there > seemed to be indication that QEMU already supported a > reverse-engineered format (before MS released specs for VHD) called > VPC This is block-vpc.c which is in upstream qemu and also in ioemu. I haven't checked at all whether the code in qemu upstream works or has been changed recently. But that would be the right place to start. Because `tap:qcow:...' in Xen config files is implemented in ioemu by iterating over the image format drivers until one of them recognises the format, you may well be able to pass a suitable disk image directly in the xen domain config file - despite it not really being qcow at all. Ian.