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] domU loses incoming network after period of inactivity

To: "Fajar A. Nugraha" <fajar@xxxxxxxxx>
Subject: Re: [Xen-users] domU loses incoming network after period of inactivity
From: Martin Gombač <martin@xxxxxx>
Date: Thu, 18 Feb 2010 14:33:23 +0100
Cc: matt@xxxxxxxxxxxxxxxxxx, Xen User-List <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 18 Feb 2010 05:34:39 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <7207d96f1002170307u24b72a7fm6f9fcef79b632c6@xxxxxxxxxxxxxx>
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: <d1bb6cdfd98ed0297adf822b35387863.squirrel@xxxxxxxxxxxxxxxxxxxxxx> <4B7A9ECB.8070100@xxxxxx> <767df12b7f709c6c1a3d5abdd8eec4e6.squirrel@xxxxxxxxxxxxxxxxxxxxxx> <7207d96f1002170307u24b72a7fm6f9fcef79b632c6@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
Matthew L.,

replacing the switch might be a solution. If it works for you, please let us all know.

Tnx.

M.

Fajar A. Nugraha wrote:
On Wed, Feb 17, 2010 at 6:49 AM, Matthew Law <matt@xxxxxxxxxxxxxxxxxx> wrote:
A workaround is to ping gateway from crontab, each minute. But this
won't help you from loosing connection to other machines on the same
network. :-/

Oh, dear :-(

I have to use bridged for most domUs, so routed is not an option for me
either.  Did you try posting it in the xen developers list? - surely
something as serious as this is being or has been addressed...

At first glance it looks like switch problem. You should be able to
trace it when the problem occurs:
- ping from outside host
- "brctl showmacs name_of_bridge", see if domU MAC is listed there
- tcpdump on uplink interface (usually peth0), see if arp goes through
correctly and domU replies it
- look at mac address table on the switch, see if you can find domUs
MAC on the correct port

It might be that the switch who should be doing arp broadcast to all
port when a MAC is not cached didn't do that, so the request from
outside world to domU never reach dom0's port.


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