RE: [Xen-users] domU btdownload problems

["Waeyenbergh, Sven" <Sven.Waeyenbergh@xxxxxxxxxxxxxx>]

Frank/Alexander,

I had similar problems with a similar application (but not bittorrent however).
What fixed the issues with my system was simply increasing the swap space on 
the domU.

obviously that won't help for a dom0 setup, but you might be able to solve this 
using 
some QOS setup on the WAN interface of your dom0 (eg controlling the amount of 
packets 
sent from the dom0 wan interface to the domU interface - controlling the 
inbound flow is 
probably not possible).

Greetings,
Sven

-----Original Message-----
From: Alexander Wilms [mailto:alex.wilms@xxxxxxxxxxxxx]
Sent: 26 January 2006 12:02
To: Sipos Ferenc
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] domU btdownload problems


Hi Frank, hi list

I can confirm a similar problem that I have in the combination with Xen
2.0.5 / 2.0.7 and the python based btdownloadheadless Bittorrent client.
But in my case I run the bt client in Dom0.
After a while all network traffic to my DomU's gets cut, but access via
"xm console xxx" is possible once.
When this happens I can see a huge increase of  TX packet drops on my
vif interfaces (bridged mode).

When I try to solve the problem e.g. by rebooting the domU system, it
shuts down cleanly, but never removes from "xm list".
Even "xm destroy" doesn't help. In this state the problem can be only
solved by rebooting the Dom0 server.

Normally my setup simply works without problems, uptimes of dom0 of
months is possible.
So only if I run the BT python client it shows this behaviour.

Unfortunately I don't see anything special in the xen or kernel logfiles
nor on the console running the BT client.

Hope my information helps to get closer to this issue,

Alex

Sipos Ferenc schrieb:
> Hi Guys.
>
> When I'm running a python based bittorrent client in one of my DomUs
> after having it run for a couple of minutes the whole networking dies.
> Here is all I get. Is it related to the fact that my domU has 'only'
> 128MByte physical RAM assigned to and when a burst of network packets
> come thru bittorrent it runs out of memory? What shall I do to prevent this?
>
> Thanks,
> Frank
>
> kano:~# python: page allocation failure. order:0, mode:0x20
>  [<c014a8e3>] __alloc_pages+0x2a3/0x480
>  [<c014dac7>] kmem_getpages+0x37/0xa0
>  [<c014ea93>] cache_grow+0xd3/0x200
>  [<c016c871>] end_bio_bh_io_sync+0x41/0x60
>  [<c014ed41>] cache_alloc_refill+0x181/0x260
>  [<c02f8351>] tcp_v4_send_check+0x51/0xf0
>  [<c014f05f>] kmem_cache_alloc+0x7f/0x90
>  [<c02bb2c4>] alloc_skb_from_cache+0x24/0xe0
>  [<c0106b50>] alloc_skb+0x50/0xa0
>  [<c02f4b0c>] tcp_send_ack+0x2c/0xf0
>  [<c02f026f>] tcp_rcv_established+0x2af/0x8c0
>  [<c014dac7>] kmem_getpages+0x37/0xa0
>  [<c02f976b>] tcp_v4_do_rcv+0x12b/0x130
>  [<c02f9e50>] tcp_v4_rcv+0x6e0/0x980
>  [<c014ed41>] cache_alloc_refill+0x181/0x260
>  [<c02dce30>] ip_local_deliver+0xf0/0x2d0
>  [<c02bb37b>] alloc_skb_from_cache+0xdb/0xe0
>  [<c02dd3bb>] ip_rcv+0x3ab/0x560
>  [<c02c2318>] netif_receive_skb+0x1b8/0x280
>  [<c02b5841>] netif_poll+0x251/0x7d0
>  [<c02c264a>] net_rx_action+0xca/0x1c0
>  [<c01242db>] __do_softirq+0x10b/0x130
>  [<c0124395>] do_softirq+0x95/0xa0
>  [<c010e0e2>] do_IRQ+0x22/0x30
>  [<c01049e6>] evtchn_do_upcall+0xa6/0xe0
>  [<c0109b54>] hypervisor_callback+0x2c/0x34
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>   


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
****************************************************************************
Disclaimer: 
This electronic transmission and any files attached to it are strictly 
confidential and intended solely for the addressee. If you are not 
the intended addressee, you must not disclose, copy or take any
action in reliance of this transmission. If you have received this 
transmission in error, please notify the sender by return and delete
the transmission.  Although the sender endeavors to maintain a
computer virus free network, the sender does not warrant that this
transmission is virus-free and will not be liable for any damages 
resulting from any virus transmitted. 
Thank You.
****************************************************************************

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