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

Re: [Xen-users] 3.4.2 domU networking fails to recover after glitch


  • To: Tony Lill <ajlill@xxxxxxxxxxxxxxxxxxx>, xen-users List <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: Andrew Lyon <andrew.lyon@xxxxxxxxx>
  • Date: Thu, 3 Dec 2009 16:56:47 +0000
  • Cc:
  • Delivery-date: Thu, 03 Dec 2009 08:57:47 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=Cyk0WopoPup3hjzJ+U/JLryh7oGsJWwwgpkmTLPf1Y4OQadvW0PkcRhDQl/p7mP3co RsxhgQ32flSGkSyEfEbdk682GXNPDdNb95ZRxnvvQBcbZP5ItO4OPf4nhBf8U1ItfELV KsfTRiuBUDSSaJIK4Ts7w0XjRe0Jo6SHtbJ2k=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

On Thu, Dec 3, 2009 at 4:24 PM, Tony Lill <ajlill@xxxxxxxxxxxxxxxxxxx> wrote:
> A couple of times yesterday, my network hiccuped (something funky on
> the switch, a couple of other hosts reported the same thing). While
> the dom0 handled it fine, I could not communicate to any of my
> domUs. using tcpdump on both eth2 and peth2, I could see them send
> packets out, but could not see any of the response packets.
>
> These are the messages that I get around the hiccup
>
> Dec  2 10:52:34 xen kernel: skge peth2: Link is down.
> Dec  2 10:52:34 xen kernel: eth2: port 1(peth2) entering disabled state
> Dec  2 10:52:36 xen kernel: skge peth2: Link is up at 1000 Mbps, full duplex, 
> flow control tx and rx
> Dec  2 10:52:36 xen kernel: eth2: port 1(peth2) entering learning state
> Dec  2 10:52:36 xen kernel: eth2: topology change detected, propagating
> Dec  2 10:52:36 xen kernel: eth2: port 1(peth2) entering forwarding state
>
> I haven't had time to do any serious debugging, but I'm hoping
> someones has seen similar problems.
>
> --
> Tony Lill,                         Tony.Lill@xxxxxxxxxxxxxxxxxxx
> President, A. J. Lill Consultants                 (519) 650 0660
> 539 Grand Valley Dr., Cambridge, Ont. N3H 2S2     (519) 241 2461
> --------------- http://www.ajlc.waterloo.on.ca/ ----------------
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>

Try this:

ip link set dev eth2 up

or

ifconfig eth2 up

In my case the problem happened for a different reason, I had run the
network-bridge script manually to create a second bridge for eth1, but
the physical link (peth1) went down for a while between running the
script and starting a domU, that seemed to cause the bridge to get
stuck in a down state and required the above command to bring it back
up.

I'm not sure if this is intended behaviour, I need to read up on what
is supposed to happen if a physical interface connected to a bridge
goes down..

Andy

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


 


Rackspace

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