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/
Home Products Support Community News


[Xen-users] GPL PV TAP cow incompatible?

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] GPL PV TAP cow incompatible?
From: Martin Kjær Jørgensen <shaoh@xxxxxxx>
Date: Thu, 26 Feb 2009 16:32:48 +0100
Cc: james.harper@xxxxxxxxxxxxxxxx
Delivery-date: Thu, 26 Feb 2009 07:30:27 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Internet Messaging Program (IMP) 4.3.3

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?


Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>