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: "Karsten M. Self" <kself@xxxxxxxxxxxxx>
Date: Thu, 12 Jan 2006 16:51:11 -0800
Delivery-date: Fri, 13 Jan 2006 00:58:01 +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>
Mail-followup-to: xen-users@xxxxxxxxxxxxxxxxxxx
References: <43C437F6.5010302@xxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.11
on Tue, Jan 10, 2006 at 11:40:54PM +0100, Michael Heyse (mhk@xxxxxxxxxxxxxxxxx) 
wrote:
> 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've FAQd this:

    
http://wiki.xensource.com/xenwiki/XenFaq#head-5e286e9bb5cf043f6534c917bc231af2af6adce2
 
 
> As a total xen noob I don't dare touch the wiki, but if someone more
> experienced could verify that these issues are valid, adding some hints
> to the documentation could help other xen beginners.

Wikis are designed to be self-service, to the extent possible.  Please
_do_ contribute and/or supply fixes or information as you feel
appropriate.


Cheers.

-- 
Karsten M. Self <karsten@xxxxxxxxxxxxx>
XenSource, Inc.
2300 Geng Road #250                                +1 650.798.5900 x259
Palo Alto, CA 94303                                +1 650.493.1579 fax

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