Re: [Xen-users] GPL PV TAP cow incompatible?

[Martin Kjær Jørgensen <shaoh@xxxxxxx>]

I'm running Xen 3.3.1 with a patched ioemu-qemu-xen (patched with the  
qemu_disable_patches.diff patch (6 Jan 2009)) on a Debian Lenny  
machine. I've compiled Xen manually as Lenny only delivers Xen 3.2.1.
I've also tried with the official ioemu-qemu-xen but with no luck.

/Martin

Quoting Nick Couchman <Nick.Couchman@xxxxxxxxx>:

> What version of Xen are you running?  I've never been able to get
> tap:{aio,cow} to work with the GPL PV drivers under Xen 3.2.x.  However,
> James Harper has reported that they work find under Xen 3.3.x.
>
> -Nick
>
>
> -----Original Message-----
> From: Martin Kjær Jørgensen <shaoh@xxxxxxx>
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Cc: james.harper@xxxxxxxxxxxxxxxx
> Subject: [Xen-users] GPL PV TAP cow incompatible?
> Date: Thu, 26 Feb 2009 16:32:48 +0100
>
>
> Hi
>
> Is it true that the GPLPV drivers is incompatible with QCOW images?
>
> The Windows DomU works fine with raw standard "file:/" images, and
> paravirtualized Linux DomU works fine with QCOW and raw images.
>
> If i use QCOW images with my Windows DomU's i get a stop error:
> 0x00000007b (inaccessible boot device).
> It looks like the blkback.3.hda process, that normally starts with
> normal raw backend, doesnt get started with tap:qcow disks.
> Instead i get this repeating entry in the qemu log:
>     XenPCI     Still waiting for 2 (currently 1)...
>     XenPCI     Still waiting for 2 (currently 1)...
>     XenPCI     Still waiting for 2 (currently 1)...
>
> Any ideas?
>
> /Martin
>
>
>
>
>
>
>
>
>
> This e-mail may contain confidential and privileged material for the  
> sole use of the intended recipient.  If this email is not intended  
> for you, or you are not responsible for the delivery of this message  
> to the intended recipient, please note that this message may contain  
> SEAKR Engineering (SEAKR) Privileged/Proprietary Information.  In  
> such a case, you are strictly prohibited from downloading,  
> photocopying, distributing or otherwise using this message, its  
> contents or attachments in any way.  If you have received this  
> message in error, please notify us immediately by replying to this  
> e-mail and delete the message from your mailbox.  Information  
> contained in this message that does not relate to the business of  
> SEAKR is neither endorsed by nor attributable to SEAKR.


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