Xen users - Dec 2005 - RE: Fixed MAC address causes spurios network connectivity loss

I appear to be having the same problem. I have 5 domU''s running on the
same machine, all of them with assigned fixed MAC addresses (all unique).
Occasionally one of the domU''s losses its network access (there is very
little network activity). I cannot ping it from the outside in dom0 or from the
other domUs.  No error messages from XEN or Linux. Sometimes it works, sometimes
it doesn''t.
   
  I did a network trace of the ping and it looks as if the ARP response is not
getting back to the domU (when pinging from within domU).  If I manually update
the ARP table in the domU myself, the ping starts working. Also, if I set the
ageing on the bridge to be 0, this also fixes the problem (but a bad
workaround).
   
  I am using XEN 2.07 on an AMD opteron.
   
  Has anyone resolved this problem?
   
  Thanks,
  Eric
   

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

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

I think I''m also having the same problem.

I have been running 3 domU''s all day and everything worked fine.  Just
now
all but dom0 stopped responding to all network activity.  I''ve shutdown
all
domU and restarted them one at a time, but they still are not reachable.

Is this a config problem or a bug?

I am running Xen 3.0 installed from the FC4 xen install script.

On 12/20/05, Eric Tessler <maiden1134@yahoo.com>
wrote:
>
> I appear to be having the same problem. I have 5 domU''s running on
the
> same machine, all of them with assigned fixed MAC addresses (all unique).
> Occasionally one of the domU''s losses its network access (there is
very
> little network activity). I cannot ping it from the outside in dom0 or
> from the other domUs.  No error messages from XEN or Linux. Sometimes it
> works, sometimes it doesn''t.
>
> I did a network trace of the ping and it looks as if the ARP response is
> not getting back to the domU (when pinging from within domU).  If I
manually
> update the ARP table in the domU myself, the ping starts working. Also, if
I
> set the ageing on the bridge to be 0, this also fixes the problem (but a
bad
> workaround).
>
> I am using XEN 2.07 on an AMD opteron.
>
> Has anyone resolved this problem?
>
> Thanks,
> Eric
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
>

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

On 12/23/05, Eric Tessler <maiden1134@yahoo.com>
wrote:
>
> Me and a co-worker are currently debugging this problem - it appears to be
> a problem with XEN or the bridge...unfortunitely we will have to dig into
> the XEN source code. In our case, dom0 works fine. One of the
domU''s from
> time to time after it starts has no network access. The funny thing is that
> if we manually update its ARP table ourselves, the network starts to work
> fine. Or if we manually restart the network in the domu after all other
> domu''s come up, it works fine as well. I am using XEN 2.07 though,
not 3.0
> .
>
I have no such luck with my domU.  I''m starting to think it may be a
problem
with my version of Xen.

When my network fails I''m still able to get into the domU domains via
the
console.  However, if I issue a ''xm shutdown'' for any of the
domU domains
they become zombies.


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