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


Re: [Xen-users] HVM and gplpv disk question

To: <xen-users@xxxxxxxxxxxxxxxxxxx>, "Gary W. Smith" <gary@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] HVM and gplpv disk question
From: "Nick Couchman" <Nick.Couchman@xxxxxxxxx>
Date: Wed, 18 Feb 2009 15:08:07 -0700
Delivery-date: Wed, 18 Feb 2009 14:09:06 -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
Yes, you should remove the ioemu from the VIF in the domU configuration file.  You can try the tap:aio device type with Xen and see if that works with the GPL PV drivers - I haven't been able to get that work, though.  I use the loop devices and it works fine.

>>> "Gary W. Smith" <gary@xxxxxxxxxxxxxxx> 2009/02/18 14:16 >>>
When I load the gplpv drivers into a Windows 2003 instance, I notice that I have to remove ioemu from the vif.  When I do that, it works just fine.  The disk images (which are file based) are still being loaded through the loop driver (which is requiring me to add a bunch of loop devices on our test box).  Is this the proper way to do this or should I be tweaking the config files for the disk as well?  If so, what should that look like?
Adding the loop devices isn't a problem but if I call tap:aio is faster than loop.

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