|
|
|
|
|
|
|
|
|
|
xen-users
[Xen-users] bridging troubles with Xen3
Hi,
I've been having troubles with bridge networking in Xen3.
RHEL4 is running in dom0 and Debian sarge in domU.
Both domains get their IPs from an external DHCP server.
dom0 starts up OK and gets its IP from the server. (all networking services
work fine; in and out)
domU starts up OK and sometimes gets its IP while sometimes fails to get the IP.
In any case, after logging into domU from 'xm console' the first ping in any
direction causes following:
* 'link down' for nic peth0 shows up in /var/log/messages (for dom0)
* activity led stops flashing on the network card
* pings from both domains outside stop working
Sometimes pinging from domU does work OK at first, but then attempting to ping
from dom0 causes the same network shutdown for both domains.
Removing either vif0.0 or vif2.0 from the bridge and giving it enough time (1-2
minutes, dhclient timeout?) fixes the networking for the other domain:
* 'link up' for nic peth0 shows up in /var/log/messages (for dom0)
* activity led starts flashing on the network card
* if vif0.0 was removed, domU regains its network
* if vif2.0 was removed, dom0 regains its network
A similar (but not hardware identical) box standing next to this one having
same software configuration (RHEL4 for dom0, same sarge image for domU) works
fine.
Tried replacing network card and using latest xen3-testing release; same
behavior.
Any help will be appreciated,
Thanks
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- [Xen-users] bridging troubles with Xen3,
Starik Hatabich <=
|
|
|
|
|