Hello.
I''ve just started with Xen and configuring Dom0.
My hardware is Core2Duo based Xeon server and I installed Debian etch
for amd64 architecture. The Xen related pachages installed are the
following.
linux-image-2.6.17-2-xen-amd64
linux-modules-2.6.17-2-xen-amd64
xen-hypervisor-3.0.3-1-amd64
xen-tools
xen-utils-3.0.3-1
xen-utils-common
My problem is that when xend is configure to have bridge network, Dom0
can not communicate with the external machines. I''ve not tried the
other
DomUs yet. (I guess they cannot communicate either.)
The related part of xend-config.sxp is the following.
(network-script ''network-bridge'')
(vif-script vif-bridge)
If the the above first line is replaced with (network-script network-
dummy)
then everything works correctly.
I appreciate any help to solve this problem.
Here are something about status and logs.
The routing definition becomes different under the network-bridge. I
tried
to invoke place a link /etc/rc0.d/S34xend -> /etc/init.d/xend but it
did not
solve the problem.
Under network-bridge
# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window
irtt Iface
10.140.202.0 0.0.0.0 255.255.254.0 U 0
0 0 eth0
0.0.0.0 10.140.203.254 0.0.0.0 UG 0
0 0 eth0
Under network-dummy
# netstat -r
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window
irtt Iface
localnet * 255.255.254.0 U 0
0 0 eth0
default 10.140.203.254 0.0.0.0 UG 0
0 0 eth0
From /var/log/messages
kernel: eth0: Broadcom NetXtreme II BCM5708 1000Base-T (B1) PCI-X
64-bit 133MHz found at mem ce000000, IRQ 16, node addr 00145e18c59f
...
kernel: bnx2: eth0 NIC Link is Up, 1000 Mbps full duplex
...
kernel: Bridge firewalling registered
kernel: device vif0.0 entered promiscuous mode
kernel: audit(1165827245.987:2): dev=vif0.0 prom=256 old_prom=0
auid=4294967295
kernel: xenbr0: port 1(vif0.0) entering learning state
kernel: xenbr0: topology change detected, propagating
kernel: xenbr0: port 1(vif0.0) entering forwarding state
kernel: ADDRCONF(NETDEV_UP): peth0: link is not ready
kernel: bnx2: peth0 NIC Link is Up, 1000 Mbps full duplex
kernel: ADDRCONF(NETDEV_CHANGE): peth0: link becomes ready
kernel: device peth0 entered promiscuous mode
kernel: audit(1165827249.211:3): dev=peth0 prom=256 old_prom=0
auid=4294967295
kernel: xenbr0: port 2(peth0) entering learning state
kernel: xenbr0: topology change detected, propagating
kernel: xenbr0: port 2(peth0) entering forwarding state
From /var/log/xen/xen.log
[2006-12-11 17:54:04 xend 4490] INFO (__init__:1072) Xend Daemon
started
[2006-12-11 17:54:04 xend 4490] INFO (__init__:1072) Xend changeset:
Tue Oct 17
22:09:52 2006 +0100 .
[2006-12-11 17:54:04 xend.XendDomainInfo 4490] DEBUG (__init__:1072)
XendDomainI
nfo.recreate({''paused'': 0, ''cpu_time'':
11483528780L, ''ssidref'': 0,
''handle'': [0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0],
''shutdown_reason'': 0,
''dying'': 0,
''dom'': 0, ''mem_kb'': 5021444,
''maxmem_kb'': 17179869180,
''max_vcpu_id'': 3, ''crash
ed'': 0, ''running'': 1, ''shutdown'':
0, ''online_vcpus'': 4, ''blocked'': 0})
[2006-12-11 17:54:04 xend.XendDomainInfo 4490] INFO (__init__:1072)
Recreating d
omain 0, UUID 00000000-0000-0000-0000-000000000000.
[2006-12-11 17:54:04 xend.XendDomainInfo 4490] WARNING (__init__:
1072) No vm pat
h in store for existing domain 0
[2006-12-11 17:54:04 xend.XendDomainInfo 4490] DEBUG (__init__:1072)
Storing VM
details: {''shadow_memory'': ''0'',
''uuid'':
''00000000-0000-0000-0000-000000000000'',
''on_reboot'': ''restart'',
''on_poweroff'': ''destroy'',
''name'':
''Domain-0'', ''xend/rest
art_count'': ''0'', ''vcpus'':
''4'', ''vcpu_avail'': ''3'',
''memory'': ''4904'',
''on_crash'':
''restart'', ''maxmem'':
''4904''}
[2006-12-11 17:54:04 xend.XendDomainInfo 4490] DEBUG (__init__:1072)
Storing dom
ain details: {''cpu/1/availability'':
''online'', ''cpu/3/availability'':
''offline'', ''
name'': ''Domain-0'',
''console/limit'': ''1048576'',
''cpu/2/availability'':
''offline'',
''vm'':
''/vm/00000000-0000-0000-0000-000000000000'',
''domid'': ''0'', ''cpu/
0/availabil
ity'': ''online'', ''memory/target'':
''5021696''}
[2006-12-11 17:54:04 xend 4490] DEBUG (__init__:1072) number of
vcpus to use is 2
[2006-12-11 17:54:05 xend.XendDomainInfo 4490] DEBUG (__init__:1072)
XendDomainI
nfo.handleShutdownWatch
Output of some commnds
# brctl show
bridge name bridge id STP enabled interfaces
xenbr0 8000.feffffffffff no vif0.0
peth0
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:14:5E:18:C5:9F
inet addr:10.140.203.84 Bcast:10.140.203.255 Mask:255.255.254.0
inet6 addr: fe80::214:5eff:fe18:c59f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:133 errors:0 dropped:0 overruns:0 frame:0
TX packets:60 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:21923 (21.4 KiB) TX bytes:5019 (4.9 KiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:38 errors:0 dropped:0 overruns:0 frame:0
TX packets:38 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2880 (2.8 KiB) TX bytes:2880 (2.8 KiB)
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:197 errors:0 dropped:0 overruns:0 frame:0
TX packets:57 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:27309 (26.6 KiB) TX bytes:5637 (5.5 KiB)
Interrupt:16 Memory:ce000000-ce011100
vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:60 errors:0 dropped:0 overruns:0 frame:0
TX packets:133 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5019 (4.9 KiB) TX bytes:21923 (21.4 KiB)
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:187 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:23880 (23.3 KiB) TX bytes:0 (0.0 b)
Thank you.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On 12/11/06, 石井俊直 <ishii.toshinao@ay.mitsubishielectric.co.jp> wrote:> [...] > The related part of xend-config.sxp is the following. > > (network-script ''network-bridge'') > (vif-script vif-bridge) > > If the the above first line is replaced with (network-script network- > dummy) > then everything works correctly.If then everything is O.K. then, what is the problem? O.K. network.dummy is not ideal to get networking for the domu''s. I don''t see any other obvious problems... And: it really *does* work with network-dummy, and *does not* work with network-bridge? Do you have any firewalling stuff running? I think, you need to restart your machine after changing the networs-script stuff, because there are some situations where changes don''t apply when just restarting xend. (it''s a quite complex change to the network devices, so a reboot is cleaner when changing something fundamentalk like this, I think) Henning _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello Henning, Thank you for comments. On 2006/12/12, at 21:46, Henning Sprang wrote:> If then everything is O.K. then, what is the problem? O.K. > network.dummy is not ideal to get networking for the domu''s. I don''t > see any other obvious problems... > > And: it really *does* work with network-dummy, and *does not* work > with network-bridge?It is true whether it is a problem or not depends how one recognizes. For me, it is a problem. If one looks around, there are much more documents about configuring DomUs under the case other than network-dummy. (For example, 2006-11/msg00884.html) If "work" means, communication of Dom0 with external machines, network-dummy really does work and network-bridge really does not work under the configuration I explained.> Do you have any firewalling stuff running?Yes. This is because Debian package xen-hypervisor-3.0.3-1-amd64 needs iproute to be installed and recommends bridge-utils to be installed. I do not need firewalling capability. I want to be able to setup with these packages.> I think, you need to restart your machine after changing the > networs-script stuff, because there are some situations where changes > don''t apply when just restarting xend. (it''s a quite complex change to > the network devices, so a reboot is cleaner when changing something > fundamentalk like this, I think)For most of the tests, I restarted the machine. I will keep this way. -- toshinao _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello.
I found that the Dom0 has the network problem after invoking `network-
bridge start`
and the problem disappears when `network-bridge stop` is invoked.
Again the OS is Debian Etch and installed packages are slightly
update as
the following.
linux-image-2.6.17-2-xen-amd64
linux-modules-2.6.17-2-xen-amd64
xen-hypervisor-3.0.3-2-amd64
xen-tools (2.8-2)
xen-utils-3.0.3-2
xen-utils-common (3.0.3-0-2)
Following is log of new tests. I appreciate comments about what is wrong
for Dom0 to communicate with others when network-bridge is started.
******* Here''s network interface setting
# cat /etc/network/interfaces
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug eth0
iface eth0 inet static
address 10.140.203.84
netmask 255.255.254.0
network 10.140.202.0
broadcast 10.140.203.255
gateway 10.140.203.254
******** At this point, network-bridge is stopped.
# cd /etc/xen/scripts
# ./network-bridge status
===========================================================2: eth0:
<BROADCAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:14:5e:18:c5:9f brd ff:ff:ff:ff:ff:ff
inet 10.140.203.84/23 brd 10.140.203.255 scope global eth0
inet6 fe80::214:5eff:fe18:c59f/64 scope link
valid_lft forever preferred_lft forever
Device "xenbr0" does not exist.
relache:/etc/xen/scripts# ifconfig
eth0 Link encap:Ethernet HWaddr 00:14:5E:18:C5:9F
inet addr:10.140.203.84 Bcast:10.140.203.255 Mask:
255.255.254.0
inet6 addr: fe80::214:5eff:fe18:c59f/64 Scope:Link
UP BROADCAST RUNNING MTU:1500 Metric:1
RX packets:1080 errors:0 dropped:0 overruns:0 frame:0
TX packets:304 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:142879 (139.5 KiB) TX bytes:51037 (49.8 KiB)
Interrupt:16 Memory:ce000000-ce011100
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:154 errors:0 dropped:0 overruns:0 frame:0
TX packets:154 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:11686 (11.4 KiB) TX bytes:11686 (11.4 KiB)
# ./network-bridge start
Nothing to flush.
Waiting for peth0 to negotiate link....
******* starting network-bridge
# ./network-bridge status
===========================================================6: eth0:
<BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
link/ether 00:14:5e:18:c5:9f brd ff:ff:ff:ff:ff:ff
inet 10.140.203.84/23 brd 10.140.203.255 scope global eth0
inet6 fe80::214:5eff:fe18:c59f/64 scope link
valid_lft forever preferred_lft forever
23: xenbr0: <BROADCAST,NOARP,UP,10000> mtu 1500 qdisc noqueue
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
inet6 fe80::200:ff:fe00:0/64 scope link
valid_lft forever preferred_lft forever
bridge name bridge id STP enabled interfaces
xenbr0 8000.feffffffffff no vif0.0
peth0
10.140.202.0/23 dev eth0 proto kernel scope link src 10.140.203.84
default via 10.140.203.254 dev eth0
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref
Use Iface
10.140.202.0 0.0.0.0 255.255.254.0 U 0 0
0 eth0
0.0.0.0 10.140.203.254 0.0.0.0 UG 0 0
0 eth0
===========================================================
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:14:5E:18:C5:9F
inet addr:10.140.203.84 Bcast:10.140.203.255 Mask:
255.255.254.0
inet6 addr: fe80::214:5eff:fe18:c59f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:18 errors:0 dropped:0 overruns:0 frame:0
TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2298 (2.2 KiB) TX bytes:3548 (3.4 KiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:156 errors:0 dropped:0 overruns:0 frame:0
TX packets:156 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:11882 (11.6 KiB) TX bytes:11882 (11.6 KiB)
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:25 errors:0 dropped:0 overruns:0 frame:0
TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3100 (3.0 KiB) TX bytes:3796 (3.7 KiB)
Interrupt:16 Memory:ce000000-ce011100
vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:26 errors:0 dropped:0 overruns:0 frame:0
TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3548 (3.4 KiB) TX bytes:2298 (2.2 KiB)
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:44 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:5230 (5.1 KiB) TX bytes:0 (0.0 b)
****** 10.140.203.254 is the ip address of default router.
# ping 10.140.203.254
PING 10.140.203.254 (10.140.203.254) 56(84) bytes of data.
From 10.140.203.84 icmp_seq=1 Destination Host Unreachable
From 10.140.203.84 icmp_seq=2 Destination Host Unreachable
From 10.140.203.84 icmp_seq=3 Destination Host Unreachable
--- 10.140.203.254 ping statistics ---
8 packets transmitted, 0 received, +3 errors, 100% packet loss, time
7014ms
, pipe 3
# ./network-bridge stop
# ./network-bridge status
===========================================================2: eth0:
<BROADCAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:14:5e:18:c5:9f brd ff:ff:ff:ff:ff:ff
inet 10.140.203.84/23 brd 10.140.203.255 scope global eth0
inet6 fe80::214:5eff:fe18:c59f/64 scope link
valid_lft forever preferred_lft forever
Device "xenbr0" does not exist.
relache:/etc/xen/scripts# ifconfig
eth0 Link encap:Ethernet HWaddr 00:14:5E:18:C5:9F
inet addr:10.140.203.84 Bcast:10.140.203.255 Mask:
255.255.254.0
inet6 addr: fe80::214:5eff:fe18:c59f/64 Scope:Link
UP BROADCAST RUNNING MTU:1500 Metric:1
RX packets:5 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:494 (494.0 b) TX bytes:334 (334.0 b)
Interrupt:16 Memory:ce000000-ce011100
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:162 errors:0 dropped:0 overruns:0 frame:0
TX packets:162 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:12512 (12.2 KiB) TX bytes:12512 (12.2 KiB)
# ping 10.140.203.254
PING 10.140.203.254 (10.140.203.254) 56(84) bytes of data.
64 bytes from 10.140.203.254: icmp_seq=1 ttl=255 time=2.47 ms
64 bytes from 10.140.203.254: icmp_seq=2 ttl=255 time=0.425 ms
64 bytes from 10.140.203.254: icmp_seq=3 ttl=255 time=0.386 ms
64 bytes from 10.140.203.254: icmp_seq=4 ttl=255 time=0.377 ms
--- 10.140.203.254 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3001ms
rtt min/avg/max/mdev = 0.377/0.916/2.476/0.900 ms
relache:/etc/xen/scripts# exit
On 2006/12/13, at 10:37, Toshinao Ishii wrote:
> Hello Henning,
>
> Thank you for comments.
>
> On 2006/12/12, at 21:46, Henning Sprang wrote:
>
>> If then everything is O.K. then, what is the problem? O.K.
>> network.dummy is not ideal to get networking for the domu''s. I
don''t
>> see any other obvious problems...
>>
>> And: it really *does* work with network-dummy, and *does not* work
>> with network-bridge?
>
> It is true whether it is a problem or not depends how one recognizes.
> For me, it is a problem. If one looks around, there are much more
> documents about configuring DomUs under the case other than
> network-dummy. (For example, 2006-11/msg00884.html)
>
> If "work" means, communication of Dom0 with external machines,
> network-dummy really does work and network-bridge really does
> not work under the configuration I explained.
>
>> Do you have any firewalling stuff running?
>
> Yes. This is because Debian package xen-hypervisor-3.0.3-1-amd64
> needs iproute to be installed and recommends bridge-utils to be
> installed. I do not need firewalling capability.
>
> I want to be able to setup with these packages.
>
>> I think, you need to restart your machine after changing the
>> networs-script stuff, because there are some situations where changes
>> don''t apply when just restarting xend. (it''s a quite
complex
>> change to
>> the network devices, so a reboot is cleaner when changing something
>> fundamentalk like this, I think)
>
> For most of the tests, I restarted the machine. I will keep this way.
>
> -- toshinao
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Toshinao Ishii
2006-Dec-14 07:46 UTC
show me ifconfig result (Re: [Xen-users] Dom0 network problem)
Hello. To solve my problem, I traced what network-bridge script does. So far I cannot find any error status of the commands invoked in the script. I''d like to know whether the resulting setup of interfaces are correct or not. Does someone show me `ifconfig` result of successfully configured bridged network ? I suspect the following `ifconfig` result in the sense that there is no inet(4) address for peth0 and xenbr0. The HWaddr of them are also suspected to be wrong. -- toshinao> # ifconfig > eth0 Link encap:Ethernet HWaddr 00:14:5E:18:C5:9F > inet addr:10.140.203.84 Bcast:10.140.203.255 Mask: > 255.255.254.0 > inet6 addr: fe80::214:5eff:fe18:c59f/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:18 errors:0 dropped:0 overruns:0 frame:0 > TX packets:26 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:2298 (2.2 KiB) TX bytes:3548 (3.4 KiB) > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:156 errors:0 dropped:0 overruns:0 frame:0 > TX packets:156 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:11882 (11.6 KiB) TX bytes:11882 (11.6 KiB) > > peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 > RX packets:25 errors:0 dropped:0 overruns:0 frame:0 > TX packets:24 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:3100 (3.0 KiB) TX bytes:3796 (3.7 KiB) > Interrupt:16 Memory:ce000000-ce011100 > > vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 > RX packets:26 errors:0 dropped:0 overruns:0 frame:0 > TX packets:18 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:3548 (3.4 KiB) TX bytes:2298 (2.2 KiB) > > xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link > UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 > RX packets:44 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:5230 (5.1 KiB) TX bytes:0 (0.0 b)> # ping 10.140.203.254 > PING 10.140.203.254 (10.140.203.254) 56(84) bytes of data. > From 10.140.203.84 icmp_seq=1 Destination Host Unreachable > From 10.140.203.84 icmp_seq=2 Destination Host Unreachable > From 10.140.203.84 icmp_seq=3 Destination Host Unreachable_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Toshinao Ishii
2006-Dec-20 03:18 UTC
inet and brd for peth0 drops in setup_bridge_port() (Re: [Xen-users] Dom0 network problem)
Hello.
I traced the problem a little more.
I''d like to know what''s described in the following is as
intended for
the proper
operation.
In network-bridge script, there''s following command invoked in
op_start().
setup_bridge_port ${pdev}
In my case ${pdev} is peth0. Just before this command, the properties of
peth0 is the following
2: peth0: <BROADCAST> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether
00:14:5e:18:c5:9f brd ff:ff:ff:ff:ff:ff inet 10.140.203.84/23 brd
10.140.203.255
scope global peth0
where 10.140.203.something are our network address.
After the command `setup_bridge_port` is completed, the properties are
chaned to
2: peth0: <BROADCAST,NOARP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether
fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
I guess drop of properties of inet and brd is noticeable.
The setup_bridge_port, defined in xen-network-command.sh, contains the
following comannds
ip link set ${dev} down
ip link set ${dev} arp off
ip link set ${dev} multicast off
ip link set ${dev} addr fe:ff:ff:ff:ff:ff
ip addr flush ${dev}
where ${dev} is the first argument. I checked these steps and I found
that
the last command `ip addr flush ${dev}` drops the properties of inet
and brd.
According to xenwiki/XenNetworking page, peth0 should have network
address since it comes the interface directly connected to the external.
The drop of inet and brd properties may be the reason of the problem
that
Dom0 cannot communicate with the external machines.
Does someone give comments to (verify) this message and hopefully a
method to solve the problem ?
-- toshinao
On 2006/12/13, at 18:20, Toshinao Ishii wrote:
> Hello.
>
> I found that the Dom0 has the network problem after invoking
> `network-bridge start`
> and the problem disappears when `network-bridge stop` is invoked.
>
> Again the OS is Debian Etch and installed packages are slightly
> update as
> the following.
>
> linux-image-2.6.17-2-xen-amd64
> linux-modules-2.6.17-2-xen-amd64
> xen-hypervisor-3.0.3-2-amd64
> xen-tools (2.8-2)
> xen-utils-3.0.3-2
> xen-utils-common (3.0.3-0-2)
>
> Following is log of new tests. I appreciate comments about what is
> wrong
> for Dom0 to communicate with others when network-bridge is started.
>
> ******* Here''s network interface setting
>
> # cat /etc/network/interfaces
> # The loopback network interface
> auto lo
> iface lo inet loopback
>
> # The primary network interface
> allow-hotplug eth0
> iface eth0 inet static
> address 10.140.203.84
> netmask 255.255.254.0
> network 10.140.202.0
> broadcast 10.140.203.255
> gateway 10.140.203.254
>
> ******** At this point, network-bridge is stopped.
>
> # cd /etc/xen/scripts
> # ./network-bridge status
> ===========================================================> 2: eth0:
<BROADCAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
> link/ether 00:14:5e:18:c5:9f brd ff:ff:ff:ff:ff:ff
> inet 10.140.203.84/23 brd 10.140.203.255 scope global eth0
> inet6 fe80::214:5eff:fe18:c59f/64 scope link
> valid_lft forever preferred_lft forever
> Device "xenbr0" does not exist.
> relache:/etc/xen/scripts# ifconfig
> eth0 Link encap:Ethernet HWaddr 00:14:5E:18:C5:9F
> inet addr:10.140.203.84 Bcast:10.140.203.255 Mask:
> 255.255.254.0
> inet6 addr: fe80::214:5eff:fe18:c59f/64 Scope:Link
> UP BROADCAST RUNNING MTU:1500 Metric:1
> RX packets:1080 errors:0 dropped:0 overruns:0 frame:0
> TX packets:304 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:142879 (139.5 KiB) TX bytes:51037 (49.8 KiB)
> Interrupt:16 Memory:ce000000-ce011100
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:154 errors:0 dropped:0 overruns:0 frame:0
> TX packets:154 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:11686 (11.4 KiB) TX bytes:11686 (11.4 KiB)
>
> # ./network-bridge start
> Nothing to flush.
> Waiting for peth0 to negotiate link....
>
> ******* starting network-bridge
>
> # ./network-bridge status
> ===========================================================> 6: eth0:
<BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
> link/ether 00:14:5e:18:c5:9f brd ff:ff:ff:ff:ff:ff
> inet 10.140.203.84/23 brd 10.140.203.255 scope global eth0
> inet6 fe80::214:5eff:fe18:c59f/64 scope link
> valid_lft forever preferred_lft forever
> 23: xenbr0: <BROADCAST,NOARP,UP,10000> mtu 1500 qdisc noqueue
> link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
> inet6 fe80::200:ff:fe00:0/64 scope link
> valid_lft forever preferred_lft forever
> bridge name bridge id STP enabled interfaces
> xenbr0 8000.feffffffffff no vif0.0
> peth0
> 10.140.202.0/23 dev eth0 proto kernel scope link src 10.140.203.84
> default via 10.140.203.254 dev eth0
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref
> Use Iface
> 10.140.202.0 0.0.0.0 255.255.254.0 U 0
> 0 0 eth0
> 0.0.0.0 10.140.203.254 0.0.0.0 UG 0
> 0 0 eth0
> ===========================================================>
>
> # ifconfig
> eth0 Link encap:Ethernet HWaddr 00:14:5E:18:C5:9F
> inet addr:10.140.203.84 Bcast:10.140.203.255 Mask:
> 255.255.254.0
> inet6 addr: fe80::214:5eff:fe18:c59f/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:18 errors:0 dropped:0 overruns:0 frame:0
> TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:2298 (2.2 KiB) TX bytes:3548 (3.4 KiB)
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:156 errors:0 dropped:0 overruns:0 frame:0
> TX packets:156 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:11882 (11.6 KiB) TX bytes:11882 (11.6 KiB)
>
> peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
> inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
> RX packets:25 errors:0 dropped:0 overruns:0 frame:0
> TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:3100 (3.0 KiB) TX bytes:3796 (3.7 KiB)
> Interrupt:16 Memory:ce000000-ce011100
>
> vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
> inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
> RX packets:26 errors:0 dropped:0 overruns:0 frame:0
> TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:3548 (3.4 KiB) TX bytes:2298 (2.2 KiB)
>
> xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
> inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
> RX packets:44 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:5230 (5.1 KiB) TX bytes:0 (0.0 b)
>
> ****** 10.140.203.254 is the ip address of default router.
>
> # ping 10.140.203.254
> PING 10.140.203.254 (10.140.203.254) 56(84) bytes of data.
> From 10.140.203.84 icmp_seq=1 Destination Host Unreachable
> From 10.140.203.84 icmp_seq=2 Destination Host Unreachable
> From 10.140.203.84 icmp_seq=3 Destination Host Unreachable
>
> --- 10.140.203.254 ping statistics ---
> 8 packets transmitted, 0 received, +3 errors, 100% packet loss,
> time 7014ms
> , pipe 3
> # ./network-bridge stop
> # ./network-bridge status
> ===========================================================> 2: eth0:
<BROADCAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
> link/ether 00:14:5e:18:c5:9f brd ff:ff:ff:ff:ff:ff
> inet 10.140.203.84/23 brd 10.140.203.255 scope global eth0
> inet6 fe80::214:5eff:fe18:c59f/64 scope link
> valid_lft forever preferred_lft forever
> Device "xenbr0" does not exist.
> relache:/etc/xen/scripts# ifconfig
> eth0 Link encap:Ethernet HWaddr 00:14:5E:18:C5:9F
> inet addr:10.140.203.84 Bcast:10.140.203.255 Mask:
> 255.255.254.0
> inet6 addr: fe80::214:5eff:fe18:c59f/64 Scope:Link
> UP BROADCAST RUNNING MTU:1500 Metric:1
> RX packets:5 errors:0 dropped:0 overruns:0 frame:0
> TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:494 (494.0 b) TX bytes:334 (334.0 b)
> Interrupt:16 Memory:ce000000-ce011100
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:162 errors:0 dropped:0 overruns:0 frame:0
> TX packets:162 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:12512 (12.2 KiB) TX bytes:12512 (12.2 KiB)
>
> # ping 10.140.203.254
> PING 10.140.203.254 (10.140.203.254) 56(84) bytes of data.
> 64 bytes from 10.140.203.254: icmp_seq=1 ttl=255 time=2.47 ms
> 64 bytes from 10.140.203.254: icmp_seq=2 ttl=255 time=0.425 ms
> 64 bytes from 10.140.203.254: icmp_seq=3 ttl=255 time=0.386 ms
> 64 bytes from 10.140.203.254: icmp_seq=4 ttl=255 time=0.377 ms
>
> --- 10.140.203.254 ping statistics ---
> 4 packets transmitted, 4 received, 0% packet loss, time 3001ms
> rtt min/avg/max/mdev = 0.377/0.916/2.476/0.900 ms
> relache:/etc/xen/scripts# exit
>
>
> On 2006/12/13, at 10:37, Toshinao Ishii wrote:
>
>> Hello Henning,
>>
>> Thank you for comments.
>>
>> On 2006/12/12, at 21:46, Henning Sprang wrote:
>>
>>> If then everything is O.K. then, what is the problem? O.K.
>>> network.dummy is not ideal to get networking for the
domu''s. I don''t
>>> see any other obvious problems...
>>>
>>> And: it really *does* work with network-dummy, and *does not* work
>>> with network-bridge?
>>
>> It is true whether it is a problem or not depends how one recognizes.
>> For me, it is a problem. If one looks around, there are much more
>> documents about configuring DomUs under the case other than
>> network-dummy. (For example, 2006-11/msg00884.html)
>>
>> If "work" means, communication of Dom0 with external
machines,
>> network-dummy really does work and network-bridge really does
>> not work under the configuration I explained.
>>
>>> Do you have any firewalling stuff running?
>>
>> Yes. This is because Debian package xen-hypervisor-3.0.3-1-amd64
>> needs iproute to be installed and recommends bridge-utils to be
>> installed. I do not need firewalling capability.
>>
>> I want to be able to setup with these packages.
>>
>>> I think, you need to restart your machine after changing the
>>> networs-script stuff, because there are some situations where
>>> changes
>>> don''t apply when just restarting xend. (it''s a
quite complex
>>> change to
>>> the network devices, so a reboot is cleaner when changing something
>>> fundamentalk like this, I think)
>>
>> For most of the tests, I restarted the machine. I will keep this way.
>>
>> -- toshinao
>>
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Dominique Rousseau
2006-Dec-20 08:15 UTC
Re: inet and brd for peth0 drops in setup_bridge_port() (Re: [Xen-users] Dom0 network problem)
Le Wed, Dec 20, 2006 at 12:18:37PM +0900, Toshinao Ishii [Ishii.Toshinao@ay.MitsubishiElectric.co.jp] a écrit: [...]> where ${dev} is the first argument. I checked these steps and I found > that the last command `ip addr flush ${dev}` drops the properties of > inet and brd. > > According to xenwiki/XenNetworking page, peth0 should have network > address since it comes the interface directly connected to the > external. > The drop of inet and brd properties may be the reason of the problem > that Dom0 cannot communicate with the external machines.Here, on a setup using the network-bridge topology, we have, after starting Xen : - eth0 in Dom0 : which has the ip address - peth0 : the physical ethernet - vif0.0 : the other extremity of eth0 - xenbr0 : the bridge where peth0 and vif0.0 (and the further vifX) are included So, from this point of view, what you get seems quite normal. -- Dominique Rousseau Neuronnexion, Prestataire Internet & Intranet 57, route de Paris 80000 Amiens tel: 03 22 71 61 90 - fax: 03 22 71 61 99 - http://www.neuronnexion.fr _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Matt Richardson
2006-Dec-21 22:07 UTC
Re: inet and brd for peth0 drops in setup_bridge_port() (Re: [Xen-users] Dom0 network problem)
On 12/20/06, Dominique Rousseau <d.rousseau@nnx.com> wrote:> Le Wed, Dec 20, 2006 at 12:18:37PM +0900, Toshinao Ishii [Ishii.Toshinao@ay.MitsubishiElectric.co.jp] a écrit: > [...] > > where ${dev} is the first argument. I checked these steps and I found > > that the last command `ip addr flush ${dev}` drops the properties of > > inet and brd. > > > > According to xenwiki/XenNetworking page, peth0 should have network > > address since it comes the interface directly connected to the > > external. > > The drop of inet and brd properties may be the reason of the problem > > that Dom0 cannot communicate with the external machines. > > Here, on a setup using the network-bridge topology, we have, after > starting Xen : > > - eth0 in Dom0 : which has the ip address > - peth0 : the physical ethernet > - vif0.0 : the other extremity of eth0 > - xenbr0 : the bridge where peth0 and vif0.0 (and the further vifX) are > included > > So, from this point of view, what you get seems quite normal. > > > -- > Dominique Rousseau > Neuronnexion, Prestataire Internet & Intranet > 57, route de Paris 80000 Amiens > tel: 03 22 71 61 90 - fax: 03 22 71 61 99 - http://www.neuronnexion.fr > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >I was having the same difficulty with Etch: networking was broken on Dom0 when using network-bridge, worked fine with network-dummy. However, I was just able to install a DomU using debootstrap with network-dummy selected, then had to switch to network-bridge and restart xend to get networking happening for both. ifconfig on Dom0 shows fe:ff:blah MAC addresses for the bridge, vif, and peth interfaces, which seems odd to me. It also seems odd that networking for Dom0 only works when a DomU is brought up. But I''m new to this, so a lot of it seems odd. -- Matt _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Christopher G. Stach II
2006-Dec-22 03:17 UTC
Re: inet and brd for peth0 drops in setup_bridge_port() (Re: [Xen-users] Dom0 network problem)
Matt Richardson wrote:> I was having the same difficulty with Etch: networking was broken on > Dom0 when using network-bridge, worked fine with network-dummy. > However, I was just able to install a DomU using debootstrap with > network-dummy selected, then had to switch to network-bridge and > restart xend to get networking happening for both. ifconfig on Dom0 > shows fe:ff:blah MAC addresses for the bridge, vif, and peth > interfaces, which seems odd to me. It also seems odd that networking > for Dom0 only works when a DomU is brought up. But I''m new to this, > so a lot of it seems odd. >What state was networking left in when the script ran? Were the interfaces in t -- Christopher G. Stach II _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Christopher G. Stach II
2006-Dec-22 03:26 UTC
Re: inet and brd for peth0 drops in setup_bridge_port() (Re: [Xen-users] Dom0 network problem)
Christopher G. Stach II wrote:> Matt Richardson wrote: >> I was having the same difficulty with Etch: networking was broken on >> Dom0 when using network-bridge, worked fine with network-dummy. >> However, I was just able to install a DomU using debootstrap with >> network-dummy selected, then had to switch to network-bridge and >> restart xend to get networking happening for both. ifconfig on Dom0 >> shows fe:ff:blah MAC addresses for the bridge, vif, and peth >> interfaces, which seems odd to me. It also seems odd that networking >> for Dom0 only works when a DomU is brought up. But I''m new to this, >> so a lot of it seems odd. >> > > What state was networking left in when the script ran? Were the > interfaces in t >Weird, got chopped. Were the interfaces in the bridge? What did ifconfig show? What did brctl show? -- Christopher G. Stach II _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Matt Richardson
2006-Dec-22 07:24 UTC
Re: inet and brd for peth0 drops in setup_bridge_port() (Re: [Xen-users] Dom0 network problem)
On 12/21/06, Christopher G. Stach II <cgs@ldsys.net> wrote:> Christopher G. Stach II wrote: > > Matt Richardson wrote: > >> I was having the same difficulty with Etch: networking was broken on > >> Dom0 when using network-bridge, worked fine with network-dummy. > >> However, I was just able to install a DomU using debootstrap with > >> network-dummy selected, then had to switch to network-bridge and > >> restart xend to get networking happening for both. ifconfig on Dom0 > >> shows fe:ff:blah MAC addresses for the bridge, vif, and peth > >> interfaces, which seems odd to me. It also seems odd that networking > >> for Dom0 only works when a DomU is brought up. But I''m new to this, > >> so a lot of it seems odd. > >> > > > > What state was networking left in when the script ran? Were the > > interfaces in t > > > > Weird, got chopped. Were the interfaces in the bridge? What did > ifconfig show? What did brctl show? > > -- > Christopher G. Stach II > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >I won''t be able to reproduce it for at least a couple of days; however, the earlier thread started by Toshinao had ifconfig output that was identical to mine. If I can get in to work for a couple of hours next week, I''ll get the output for brctl and ifconfig. -- Matt _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users