Jurgen Stroo
2005-Jun-05 10:57 UTC
[Xen-devel] Xen 3.0 Xend loses network - eth0 -> veth0?
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@lists.xensource.com
http://lists.xensource.com/xen-devel
Jurgen Stroo
2005-Jun-05 15:48 UTC
Re: [Xen-devel] Xen 3.0 Xend loses network - eth0 -> veth0?
No one on this? Although very unlikely, it seems Jurgen Stroo stated on Jun 5 that :> 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@lists.xensource.com > http://lists.xensource.com/xen-devel >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ian Pratt
2005-Jun-05 16:32 UTC
RE: [Xen-devel] Xen 3.0 Xend loses network - eth0 -> veth0?
> No one on this?The /etc/xen/scripts/network script should be creating the bridge and veth0, and transferring the IP address from eth0 to veth0. It appears in your report as though both eth0 and veth0 have the same address. I expect this is a conflict between the network script and your existing setup. Ian> Although very unlikely, it seems Jurgen Stroo stated on Jun 5 that : > > > 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@lists.xensource.com > > http://lists.xensource.com/xen-devel > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser
2005-Jun-05 16:40 UTC
Re: [Xen-devel] Xen 3.0 Xend loses network - eth0 -> veth0?
On 5 Jun 2005, at 17:32, Ian Pratt wrote:> The /etc/xen/scripts/network script should be creating the bridge and > veth0, and transferring the IP address from eth0 to veth0. > > It appears in your report as though both eth0 and veth0 have the same > address. I expect this is a conflict between the network script and > your > existing setup.The script does not bother to delete the address from the old interface, but the routes should be changed to be via veth0 rather than eth0. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser
2005-Jun-05 16:47 UTC
Re: [Xen-devel] Xen 3.0 Xend loses network - eth0 -> veth0?
On 5 Jun 2005, at 17:40, Keir Fraser wrote:>> The /etc/xen/scripts/network script should be creating the bridge and >> veth0, and transferring the IP address from eth0 to veth0. >> >> It appears in your report as though both eth0 and veth0 have the same >> address. I expect this is a conflict between the network script and >> your >> existing setup. > > The script does not bother to delete the address from the old > interface, but the routes should be changed to be via veth0 rather > than eth0.Hmm.. actually the script *is* supposed to delete the address from eth0. So I''m not sure how things ended up in the state Jurgen posted. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jurgen Stroo
2005-Jun-05 20:53 UTC
Re: [Xen-devel] Xen 3.0 Xend loses network - eth0 -> veth0?
Hi,
Actually, I checked this script indeed, and also did by hand what I
thought should happen, the takeover of the MAC and IP of eth0 and transfer
it to de veth0. What I did was setting the MAC address to a plain
FE:FF:FF:FF:FF:FF MAC address, and deleted the IP address, after these
were taken over by veth0.
But, as Keir correctly stated, the routes should also be redefined, hence
eth0 is disabled.
Also, when I boot, and I do not use ''xend start'' but do the
/etc/xen/scripts/network start instead, the IP take-over process is done
correctly. So I''ll check why this isn''t working via xend start
later.
The thing is, after I''ve got the following configuration it is still
-NOT-
working:
megalosaurus:~# ifconfig -a
eth0 Link encap:Ethernet HWaddr FF:FF:FF:FF:FF:FF
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:20 errors:0 dropped:0 overruns:0 frame:0
TX packets:86 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1956 (1.9 KiB) TX bytes:12490 (12.1 KiB)
Interrupt:11 Base address:0xec00
<..snip..>
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:21 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:882 (882.0 b)
megalosaurus:~#
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt
Iface
10.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0
veth0
0.0.0.0 10.0.0.254 0.0.0.0 UG 0 0 0
veth0
megalosaurus:~# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy DROP)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
So, this looks good IMHO, but it does not work.
Some checking with tcpdump on the Xen host (10.0.0.4) gave me the
following remarkable info:
04:41:30.508617 arp who-has 10.0.0.3 tell newmeg
04:41:30.508763 arp reply 10.0.0.3 is-at 00:01:02:0a:25:0d
And, I saw on this 10.0.0.3 (oldserver) host:
20:44:00.289199 arp who-has oldserver tell 10.0.0.4
They are getting each others arp replies!
So, these two servers actually *see* each other, but they won''t come
much
further than arp, ip (as in the protocol) is not working...
PS
When stopping the xen network and thus the bridge, and restart my default
debian network configuration, everything works again..
I am really scratching my head now.
Jurgen
Although very unlikely, it seems Keir Fraser stated on Jun 5 that :
>
> On 5 Jun 2005, at 17:40, Keir Fraser wrote:
>
> >> The /etc/xen/scripts/network script should be creating the bridge
and
> >> veth0, and transferring the IP address from eth0 to veth0.
> >>
> >> It appears in your report as though both eth0 and veth0 have the
same
> >> address. I expect this is a conflict between the network script
and
> >> your
> >> existing setup.
> >
> > The script does not bother to delete the address from the old
> > interface, but the routes should be changed to be via veth0 rather
> > than eth0.
>
> Hmm.. actually the script *is* supposed to delete the address from
> eth0. So I''m not sure how things ended up in the state Jurgen
posted.
>
> -- Keir
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Keir Fraser
2005-Jun-06 08:14 UTC
Re: [Xen-devel] Xen 3.0 Xend loses network - eth0 -> veth0?
On 5 Jun 2005, at 21:53, Jurgen Stroo wrote:> > The thing is, after I''ve got the following configuration it is still > -NOT- > working: > > megalosaurus:~# ifconfig -a > eth0 Link encap:Ethernet HWaddr FF:FF:FF:FF:FF:FFThe MAC address should be FE:FF:FF:FF:FF:FF. The one above is the broadcast address. Not sure if it actually matters, but worth fixing anyway as it might confuse the bridge. I had problems with ARP when I first started testing veth0. It turned out that domain0 was not applying the information in ARP packets to the ARP cache. Since the ARP cache wasn''t kept up to date, I saw very weird IP behaviour. I fixed that particular bug, but maybe there''s another one. It is perhaps worth looking at /proc/net/arp and seeing how it compares with other machines on your network. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jurgen Stroo
2005-Jun-09 08:50 UTC
Re: [Xen-devel] Xen 3.0 Xend loses network - eth0 -> veth0?
Hi Keir, and others, I didn''t have time last week to further investigate the problem, but I''m able to do now. When I do the network scripts by hand, as I already mentioned, things are going well and the interface and routing configuration are okay. this means correct routes via veth0 etc. Also eth0 got its FE:FF:FF:FF:FF:FF correctly. The arp table looks good actually: normal situation without xen: megalosaurus:~# cat /proc/net/arp IP address HW type Flags HW address Mask Device 10.0.0.3 0x1 0x2 00:01:02:0A:25:0D * eth0 10.0.0.142 0x1 0x0 00:00:00:00:00:00 * eth0 10.0.0.141 0x1 0x0 00:00:00:00:00:00 * eth0 10.0.0.254 0x1 0x2 00:13:49:10:0B:E0 * eth0 And with Xen and the veth0 interface: IP address HW type Flags HW address Mask Device 10.0.0.141 0x1 0x0 00:00:00:00:00:00 * veth0 10.0.0.142 0x1 0x0 00:00:00:00:00:00 * veth0 10.0.0.3 0x1 0x2 00:01:02:0A:25:0D * veth0 10.0.0.254 0x1 0x2 00:13:49:10:0B:E0 * veth0 Looks perfectly right, I don''t know what the problem could be actually. Everyting looks right and they reply to each others arp requests, that means on ARP level they see each other and reply to each other with the ARP replies. :-S Jurgen Although very unlikely, it seems Keir Fraser stated on Jun 6 that :> > On 5 Jun 2005, at 21:53, Jurgen Stroo wrote: > > > > > The thing is, after I''ve got the following configuration it is still > > -NOT- > > working: > > > > megalosaurus:~# ifconfig -a > > eth0 Link encap:Ethernet HWaddr FF:FF:FF:FF:FF:FF > > The MAC address should be FE:FF:FF:FF:FF:FF. The one above is the > broadcast address. Not sure if it actually matters, but worth fixing > anyway as it might confuse the bridge. > > I had problems with ARP when I first started testing veth0. It turned > out that domain0 was not applying the information in ARP packets to the > ARP cache. Since the ARP cache wasn''t kept up to date, I saw very weird > IP behaviour. > > I fixed that particular bug, but maybe there''s another one. It is > perhaps worth looking at /proc/net/arp and seeing how it compares with > other machines on your network. > > -- Keir > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel