[Xen-devel] Xen 3.0 Xend loses network - eth0 -> veth0?

[Jurgen Stroo <blurg@xxxxxxxxxxxxxxx>]

Hi list.

I started with Xen yesterday, but I am facing a bit of a problem.
My system had always configure eth0 with 10.0.0.4/8

I am using Xen unstable source (on Debian sid)

Now I installed Xen, rebooted the machine, and first the usual network is
coming up and then the xend will be started.

I'll end up with this, but I am wondering if this should be the way of
things to be configured:

megalosaurus:~# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:40:63:D7:A3:82
          inet addr:10.0.0.4  Bcast:10.255.255.255  Mask:255.0.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:807379 errors:0 dropped:0 overruns:0 frame:0
          TX packets:680984 errors:0 dropped:0 overruns:0 carrier:0
          collisions:174 txqueuelen:1000
          RX bytes:800654135 (763.5 MiB)  TX bytes:52893851 (50.4 MiB)
          Interrupt:11 Base address:0xec00

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:19 errors:0 dropped:0 overruns:0 frame:0
          TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2004 (1.9 KiB)  TX bytes:2004 (1.9 KiB)

tap0      Link encap:Ethernet  HWaddr EE:F6:D7:D8:F4:F8
          inet addr:10.0.0.150  Bcast:10.255.255.255  Mask:255.0.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:21 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:0 (0.0 b)  TX bytes:882 (882.0 b)

veth0     Link encap:Ethernet  HWaddr 00:40:63:D7:A3:82
          inet addr:10.0.0.4  Bcast:10.255.255.255  Mask:255.0.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:120 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:32280 (31.5 KiB)

vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:120 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:32280 (31.5 KiB)  TX bytes:0 (0.0 b)

xen-br0   Link encap:Ethernet  HWaddr 00:00:00:00:00:00
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 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:0 (0.0 b)  TX bytes:0 (0.0 b)

After the system boots and the network and xend is started, nothing works,
with this configuration.

Actually, it works now after restarting the network
(/etc/init.d/networking) and after restarting xend (sometimes a couple of
times though)

I can't find anywhere in the docs if eth0 should be configured like this.
Sometimes I am experiencing lots of lag, as if these IP's are conflicting with
each other.

The whole networking thing seems not to be configured right.

for completeness:

megalosaurus:~# netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt
Iface
10.0.0.202      10.0.0.150      255.255.255.255 UGH       0 0          0
tap0
10.0.0.201      10.0.0.150      255.255.255.255 UGH       0 0          0
tap0
10.0.0.0        0.0.0.0         255.0.0.0       U         0 0          0
eth0
10.0.0.0        0.0.0.0         255.0.0.0       U         0 0          0
tap0
0.0.0.0         10.0.0.254      0.0.0.0         UG        0 0          0
eth0


---------------------------------------------------------------------------
"When a man sits with a pretty girl for an hour, it seems like a minute.
But let him sit on a hot stove for a minute and it's longer than any hour.
That's relativity." [A. Einstein, 1938]


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