[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] Xen 3.0 RHEL4.1 networking problem


  • To: "Michael Best" <mbest@xxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
  • Date: Tue, 6 Dec 2005 16:51:44 -0000
  • Delivery-date: Tue, 06 Dec 2005 16:52:08 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcX6ZNmuqH7gDH1ORHqENgJeF5SrLAAFtFoQ
  • Thread-topic: [Xen-devel] Xen 3.0 RHEL4.1 networking problem

> I'm copying the installer from my dom0 to my domU (48M file) 
> the file transfer stalls out and on the domU I get this 
> kernel message:
> 
> i.e. dom0:
> # scp xen-3.0-x86_32-rhel4.1.bin.tar domU:/mnt/sources 
> root@domU's password:
> xen-3.0-x86_32-rhel4.1.bin.tar       0%  196KB   0.0KB/s - stalled -K
> 
> domU:
> dmesg | tail -n 1
> Received packet needs 8 bytes more headroom.
> 
> tail /var/log/message:
> Dec  5 16:28:06 domU kernel: Received packet needs 8 bytes 
> more headroom.
> Dec  5 16:28:59 domU last message repeated 10 times

This bug is understood and a fix has been applied to the testing tree.

It only effects dom0 kernels built with the -xen config rather than
-xen0.

[Basically, the -xen kernel config turns on so much stuff that the area
reserved for the max posible header length is too big. This causes a
netfront slow-path to be exercised that copys the skb. Unfortunately,
this path hadn't been exercised before, and guess what, it was subteley
broken for checksum offloaded packets.]

You can work around the bug by reducing the MTU of eth0 in the dom0 e.g.
"ifconfig eth0 mtu 1400"


Ian

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.