Xen users - Aug 2010 - Slow windows network with gplpv driver.

Have 4 xen servers with windows domains.
2 work OK and 2 have xp domains with slow network performance.

Doing most of the testing on a xen system that currently is not in production.
Running xen 4.0 with 2.6.32 kernel from lenny backports.
Have xp service pack3 freshly installed with no updates.
Installed gplpv gplpv_XP_0.11.0.213.msi

hdtack gives 60mb/sec which is good
iperf gives ~15Mbits/sec
Without gplpv is about hte same.
A linux pv domu gives 686Mbits/sec
Shows it as using Xen Net Device Driver.

Things that I have tried that did not help:
Disable Checksum Offload.
Disable Large Send Offload.
Disable Scatter/Gather.
Adding /patchptr  to boot.ini

Any Ideas?

John





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

> 
> Have 4 xen servers with windows domains.
> 2 work OK and 2 have xp domains with slow network performance.
> 
> Doing most of the testing on a xen system that currently is not in
production.
> Running xen 4.0 with 2.6.32 kernel from lenny backports.
> Have xp service pack3 freshly installed with no updates.
> Installed gplpv gplpv_XP_0.11.0.213.msi
> 
> hdtack gives 60mb/sec which is good
> iperf gives ~15Mbits/sec
> Without gplpv is about hte same.
> A linux pv domu gives 686Mbits/sec
> Shows it as using Xen Net Device Driver.
> 
> Things that I have tried that did not help:
> Disable Checksum Offload.
> Disable Large Send Offload.
> Disable Scatter/Gather.
> Adding /patchptr  to boot.ini
> 
> Any Ideas?
> 
What XP service pack are you running? Try turning off the firewall,
including disabling the firewall service completely (eg services.msc and
disable the actual service, don''t just turn off the firewall)

James

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

On 25 August 2010 12:46, John McMonagle <johnm@advocap.org>
wrote:
> On Tuesday, August 24, 2010 05:55:08 pm you wrote:
>
>> Do you still have type=ioemu in the domU vif settings? I found
>> removing that almost doubled network performance when the GPLPV
>> drivers are installed.
>>
>> I even seen references to replacing it with type=paravirtualized as
>> well, but have compared that yet.
>
> Had
> vif=[''mac=00:16:3E:30:E1:32'' ]
> Tried
> vif=[''type=paravirtualized'',
''mac=00:16:3E:30:E1:32'' ]
> No change :-(
>
[whoops, my original reply didn''t go to the list - fixed]

So you didn''t have the type=ioemu anyway - oh well.

One minor point (that might not have any effect):

I think that vif line should probably be written like:

vif=[''type=paravirtualized, mac=00:16:3E:30:E1:32'' ]

The quotes either side of the comma should be removed to make it a
single string.

I think...

vif=[''type=paravirtualized'',
''mac=00:16:3E:30:E1:32'' ]

...will actually be creating two different interfaces - one with the
type setting and a second one with the MAC setting. The
paravirtualized setting might not have been applied to your actual
interface, but I don''t know that will actually make any difference
anyway.

http://wiki.xen.org/xenwiki/XenNetworking

-- 
Cheers
Anton

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

On Tuesday, August 24, 2010 08:33:19 pm Anton wrote:
> On 25 August 2010 12:46, John McMonagle <johnm@advocap.org> wrote:
> > On Tuesday, August 24, 2010 05:55:08 pm you wrote:
> >> Do you still have type=ioemu in the domU vif settings? I found
> >> removing that almost doubled network performance when the GPLPV
> >> drivers are installed.
> >> 
> >> I even seen references to replacing it with type=paravirtualized
as
> >> well, but have compared that yet.
> > 
> > Had
> > vif=[''mac=00:16:3E:30:E1:32'' ]
> > Tried
> > vif=[''type=paravirtualized'',
''mac=00:16:3E:30:E1:32'' ]
> > No change :-(
> 
> [whoops, my original reply didn''t go to the list - fixed]
> 
> So you didn''t have the type=ioemu anyway - oh well.
> 
> One minor point (that might not have any effect):
> 
> I think that vif line should probably be written like:
> 
> vif=[''type=paravirtualized, mac=00:16:3E:30:E1:32'' ]
> 
> The quotes either side of the comma should be removed to make it a
> single string.
> 
> I think...
> 
> vif=[''type=paravirtualized'',
''mac=00:16:3E:30:E1:32'' ]
> 
Yes indeed. Was 2 interfaces.
Fixed and now have just one.
Speed  is still the same :-(

> ...will actually be creating two different interfaces - one with the
> type setting and a second one with the MAC setting. The
> paravirtualized setting might not have been applied to your actual
> interface, but I don''t know that will actually make any difference
> anyway.
> 
> http://wiki.xen.org/xenwiki/XenNetworking
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Tuesday 24 August 2010 06:38:03 pm James Harper
wrote:
> > Have 4 xen servers with windows domains.
> > 2 work OK and 2 have xp domains with slow network performance.
> >
> > Doing most of the testing on a xen system that currently is not in
>
> production.
>
> > Running xen 4.0 with 2.6.32 kernel from lenny backports.
> > Have xp service pack3 freshly installed with no updates.
> > Installed gplpv gplpv_XP_0.11.0.213.msi
> >
> > hdtack gives 60mb/sec which is good
> > iperf gives ~15Mbits/sec
> > Without gplpv is about hte same.
> > A linux pv domu gives 686Mbits/sec
> > Shows it as using Xen Net Device Driver.
> >
> > Things that I have tried that did not help:
> > Disable Checksum Offload.
> > Disable Large Send Offload.
> > Disable Scatter/Gather.
> > Adding /patchptr  to boot.ini
> >
> > Any Ideas?
>
> What XP service pack are you running? Try turning off the firewall,
> including disabling the firewall service completely (eg services.msc and
> disable the actual service, don''t just turn off the firewall)
>
____________________________________________
it''s service pack3.
Killing the firewall helped a little but not much.

Is there any way to verify it''s really using the paravirtualized
driver?
This my configuration:
import os, re
arch_libdir = ''lib''
arch = os.uname()[4]
if os.uname()[0] == ''Linux'' and
re.search(''64'', arch):
    arch_libdir = ''lib64''
kernel = "/usr/lib/xen/boot/hvmloader"
builder=''hvm''
device_model = ''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''
memory=1024
name=''fdlxp1''
vif=[''type=paravirtualized, mac=00:16:3E:30:E1:32'' ]
shadow_memory = 8
disk=[''phy:/dev/xvg0/fdlxp1-disk,ioemu:hda,w'',''file:/extra/xp-sp3.iso,hdc:cdrom,r'']
boot=''d''
vnc=1
stdvga=0
usb=1
usbdevice="host:0ea0:2168"
usbdevice=''tablet''
serial=''pty''
vnclisten=''0.0.0.0''
vncpasswd=''''
on_xend_stop = ''shutdown''



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