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] Strange Network behaviour

To: "Pasi Kärkkäinen" <pasik@xxxxxx>
Subject: Re: [Xen-users] Strange Network behaviour
From: hbh@xxxxxx
Date: Tue, 15 Sep 2009 12:09:10 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 15 Sep 2009 03:09:51 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20090915095312.GR31123@xxxxxxxxxxx>
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: <20090915094820.242740@xxxxxxx> <20090915095312.GR31123@xxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

thanks for the hints.

> What does "xm info" say about free memory before and after starting the
> 14th domU?

It is the same line:

Domain-0        0      478     8 r----- 357306.0

> Does your dom0 memory get ballooned (too much) down? Check the amount of
> dom0 memory aswell before and after 14th domU.
> Anything in dom0 logs? dmesg? /var/log/messages file? 

A dmesg is interesting:

ADDRCONF(NETDEV_CHANGE): vif55.0: link becomes ready
xenbr0: port 14(vif55.0) entering learning state
xenbr0: topology change detected, propagating
xenbr0: port 14(vif55.0) entering forwarding state
printk: 126 messages suppressed.
xen_net: Memory squeeze in netback driver.
printk: 4 messages suppressed.
xen_net: Memory squeeze in netback driver.
printk: 4 messages suppressed.
xenbr0: port 14(vif55.0) entering disabled state
xenbr0: port 14(vif55.0) entering disabled state
device vif55.0 left promiscuous mode

This is from start to end of 14th domU. So i guess there is a problem with the 
network configuration.
In xend-config I have "(dom0-min-mem 0)"
Shoud I set dom0 memory via boot-parameter? I found that solution on the net. 
Which value whould be best then?



Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3 -
sicherer, schneller und einfacher! http://portal.gmx.net/de/go/atbrowser

Xen-users mailing list