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. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
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. -Nick>>> "Gary W. Smith" <gary@primeexalia.com> 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 Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > Yes, you should remove the ioemu from the VIF in the domUconfiguration> file. You can try the tap:aio device type with Xen and see if thatworks> with the GPL PV drivers - I haven''t been able to get that work,though. I> use the loop devices and it works fine. >Can you confirm that tap:aio works with a regular PV domain but not with HVM+GPLPV drivers? What about linux HVM and PV drivers? I could never get tap:aio working with GPLPV but then when I upgraded to 3.3.1 it all ''just worked''. James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
James, tap:aio works for all of my linux domU''s just fine. I''m looking for the answer of if I should use this for my Windows HVM''s which are running gplpv. So, if I am to get it to work, what should I be using for the disk line in the config file for the HVM? ________________________________ From: xen-users-bounces@lists.xensource.com on behalf of James Harper Sent: Wed 2/18/2009 2:29 PM To: Nick Couchman; xen-users@lists.xensource.com; Gary W. Smith Subject: RE: [Xen-users] HVM and gplpv disk question> > Yes, you should remove the ioemu from the VIF in the domUconfiguration> file. You can try the tap:aio device type with Xen and see if thatworks> with the GPL PV drivers - I haven''t been able to get that work,though. I> use the loop devices and it works fine. >Can you confirm that tap:aio works with a regular PV domain but not with HVM+GPLPV drivers? What about linux HVM and PV drivers? I could never get tap:aio working with GPLPV but then when I upgraded to 3.3.1 it all ''just worked''. James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Gary W. Smith Sent: Wednesday, February 18, 2009 5:32 PM To: James Harper; Nick Couchman; xen-users@lists.xensource.com Subject: RE: [Xen-users] HVM and gplpv disk question James, tap:aio works for all of my linux domU''s just fine. I''m looking for the answer of if I should use this for my Windows HVM''s which are running gplpv. So, if I am to get it to work, what should I be using for the disk line in the config file for the HVM? ________________________________________ From: xen-users-bounces@lists.xensource.com on behalf of James Harper Sent: Wed 2/18/2009 2:29 PM To: Nick Couchman; xen-users@lists.xensource.com; Gary W. Smith Subject: RE: [Xen-users] HVM and gplpv disk question> > Yes, you should remove the ioemu from the VIF in the domUconfiguration> file. You can try the tap:aio device type with Xen and see if thatworks> with the GPL PV drivers - I haven''t been able to get that work,though. I> use the loop devices and it works fine. >Can you confirm that tap:aio works with a regular PV domain but not with HVM+GPLPV drivers? What about linux HVM and PV drivers? I could never get tap:aio working with GPLPV but then when I upgraded to 3.3.1 it all ''just worked''. James ----------------------------------->From what I have read around the internet it seems that anything before xen 3.3.x wouldn''t use tap:aio for HVM domains... can anyone else confirm this "just worked" scenario after an upgrade to 3.3.1?Tait _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Can you confirm that tap:aio works with a regular PV domain but not > with > HVM+GPLPV drivers? What about linux HVM and PV drivers? > > I could never get tap:aio working with GPLPV but then when I upgraded > to > 3.3.1 it all ''just worked''. > > James > ----------------------------------- > > > From what I have read around the internet it seems that anythingbefore> xen 3.3.x wouldn''t use tap:aio for HVM domains... can anyone else > confirm this "just worked" scenario after an upgrade to 3.3.1? > > TaitCan we up the ante on this? Besides just confirming, can you please post a confirmed working conf file for HVM instance? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Sun, Feb 22, 2009 at 12:24 AM, Gary W. Smith <gary@primeexalia.com> wrote:> Can we up the ante on this? Besides just confirming, can you please > post a confirmed working conf file for HVM instance?Here''s mine #=============================================memory = 1000 vif = [ ''mac=00:16:3E:68:81:ED, bridge=br61'' ] disk = [ ''tap:aio:/data/img/w2k3sp2.img,hda,w'', ] boot="cd" device_model = ''/usr/lib64/xen/bin/qemu-dm'' kernel = "/usr/lib/xen/boot/hvmloader" builder=''hvm'' sdl=0 vnc=1 vnclisten="0.0.0.0" #vncunused=0 vncpasswd='''' stdvga=0 serial=''pty'' localtime=1 usbdevice=''tablet'' acpi=1 apic=0 pae=0 vcpus=1 cpus="1-7" cpu_cap=100 cpu_weight=128 #============================================= _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
One thing that I did experience with the Centos 5.2 Xen packages and tap:aio was a complete crash of the server when attempting to start a linux PV domain with tap:aio. No explanations for the crash in any log files so for now I am staying away from it. Hope other people have better luck, I guess I am sticking with loopback. -----Original Message----- From: Gary W. Smith [mailto:gary@primeexalia.com] Sent: Saturday, February 21, 2009 12:24 PM To: Tait Clarridge; James Harper; Nick Couchman; xen-users@lists.xensource.com Subject: RE: [Xen-users] HVM and gplpv disk question> Can you confirm that tap:aio works with a regular PV domain but not > with > HVM+GPLPV drivers? What about linux HVM and PV drivers? > > I could never get tap:aio working with GPLPV but then when I upgraded > to > 3.3.1 it all ''just worked''. > > James > ----------------------------------- > > > From what I have read around the internet it seems that anythingbefore> xen 3.3.x wouldn''t use tap:aio for HVM domains... can anyone else > confirm this "just worked" scenario after an upgrade to 3.3.1? > > TaitCan we up the ante on this? Besides just confirming, can you please post a confirmed working conf file for HVM instance? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users