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] Wireless device in Xen Guest

To: "Jui-Ting (Jerry) Weng" <jtweng@xxxxxxxxx>
Subject: RE: [Xen-users] Wireless device in Xen Guest
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Tue, 25 Jan 2011 14:16:37 +1100
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 24 Jan 2011 19:17:42 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AANLkTinVdrhb6PY=s+jdVyEdRveaVtGb00u5UqwaGEz-@xxxxxxxxxxxxxx>
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>
References: <AANLkTikot0Drg+W4MM+uvbSCv6wSUfVfOwhRhrJcNUAv@xxxxxxxxxxxxxx><AEC6C66638C05B468B556EA548C1A77D01BB924B@trantor> <AANLkTinVdrhb6PY=s+jdVyEdRveaVtGb00u5UqwaGEz-@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acu8PfpJUoEV0hSLTw2KDKe4EdjxbwAAB0GA
Thread-topic: [Xen-users] Wireless device in Xen Guest
> I'll double check the NAT configurations.
> Right now I can use wireless in DomU. it is just incredibly slow.
> I perform the following test through Iperf.
> laptop A. Setup an Iperf server at Dom0
> (1)
> laptop B. Setup an Iperf client at Dom0, connect to laptop A.
Throughput is
> 2.2Mbps
> (2)
> laptop B. Setup an Iperf client at DomU, connect to laptop A.
Throughput is
> 90Kbps
> DomU throughput degrade to 1/20 of the Dom0. Since this only happen on
> wireless card, I was wondering if my configuration is wrong.

One thing to try is to use ethtool to disable all forms of offload in
DomU and Dom0 on the bridge, physical, and virtual interfaces. That
should at least confirm that offload is not the cause.

A simple tcpdump might show you some checksum issues (assuming you use
-s0 to grab the whole frame) but it's often hard to tell as packets can
have no checksum while on the bridge.


Xen-users mailing list

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