WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Suggestions for the xen user's manual / wiki

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Suggestions for the xen user's manual / wiki
From: Ralph Passgang <ralph@xxxxxxxxxxxxx>
Date: Wed, 11 Jan 2006 01:40:39 +0100
Delivery-date: Wed, 11 Jan 2006 00:46:09 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <43C437F6.5010302@xxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <43C437F6.5010302@xxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.8.3
Am Dienstag, 10. Januar 2006 23:40 schrieb Michael Heyse:
> Hi,
>
> there are two issues wich cost me some time to figure out and maybe it
> made sense if someone put them into the documentation and / or wiki,
> because without these addressed my system ran pretty instable and wasn't
> very usable. This applies to xen-3.0 and kernel 2.6.12.6-xen:
>
>
> 1) Networking issue
>
> With the default bridged setup, networking was quite flaky, e.g. samba
> access from dom0 to a server in domU was impossible, ssh connections
> froze, and dmesg contained lots of lines like "Received packet needs 8
> bytes more headroom". A short explanation is found in
>
> http://lists.xensource.com/archives/html/xen-devel/2005-12/msg00226.html
>
> and is apparently due to some bug in the networking code. The suggested
> workaround fixed this problem for me: set the mtu to 1400 for all
> network interfaces in dom0 and domU.
>
> I'm actually suprised that this is not a FAQ.

I had exactly this problem on one testing box. Changing the mtu should help, 
but better is to use xen-3.0-testing. This bug is fixed in xen-3.0-testing.

why it's not in the faq? probably because the most users won't see this on xen 
3.0.0 release, just on some configuration this seems to happen.

and also this is not a long term issue and that's probably why not worth to be 
mentioned in the faq.

--Ralph

[...]
> Thanks,
> Michael

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