[Xen-bugs] [Bug 62] Losing network when xend started

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/cgi-bin/bugzilla/show_bug.cgi?id=62





------- Additional Comments From dbarrera@xxxxxxxxxx  2005-06-15 15:09 -------
I experience this problem again today, June 14, using the latest BK pull
(Changeset   2005/06/14 20:30:50+01:00 chrisw@xxxxxxxx 
[PATCH] x86_64 entry.S cleanup - take 3).

I captured the ifconfig output right after I lost network connectivity:
eth0      Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:30161 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3700 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:12106853 (11.5 Mb)  TX bytes:323816 (316.2 Kb)
          Base address:0x2000 Memory:d0120000-d0140000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:227 errors:0 dropped:0 overruns:0 frame:0
          TX packets:227 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:17944 (17.5 Kb)  TX bytes:17944 (17.5 Kb)

veth0     Link encap:Ethernet  HWaddr 00:0D:60:83:F1:AC
          inet addr:9.3.190.118  Bcast:9.3.190.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:252 (252.0 b)

vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:252 (252.0 b)  TX bytes:0 (0.0 b)

----------------------------------------------------------

The 'dmesg' output (last lines) was:

device vif0.0 entered promiscuous mode
bridge: can't decode speed from eth0: 65535
device eth0 entered promiscuous mode
e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex

----------------------------------------------------------

The last few lines of 'xm log' output:

[2005-06-15 09:40:05 xend] INFO (XendRoot:128) EVENT> xend.domain.create
['Domain-0', 0]
[2005-06-15 09:40:06 xend] INFO (SrvServer:63) unix 
path=/var/lib/xend/xend-socket
[2005-06-15 09:40:06 xend] INFO (XendRoot:128) EVENT> xend.start 0
[2005-06-15 09:40:08 xend] INFO (process:35) [network] network start
bridge=xen-br0 netdev=eth0 antispoof=no

----------------------------------------------------------





------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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