Greetings everyone,
I am trying to set up Xen on Debian Etch for the first time.
Hardware is an IBM Blade type HS21 (IBM machine type-model 8853A2G).
Everything is installed from Debian packages, nothing is locally
compiled. Relevant packages installed, with revision numbers:
linux-image-2.6.18-5-xen-amd64 2.6.18.dfsg.1-13etch6
linux-modules-2.6.18-5-xen-amd64 2.6.18.dfsg.1-13etch6
xen-linux-system-2.6.18-5-xen-amd64 2.6.18.dfsg.1-13etch6
xen-tools 2.8-2
xen-utils-3.0.3-1 3.0.3-0-4
xen-utils-common 3.0.3-0-2
I have succeeded in creating and booting a guest domain with Debian as
the guest OS, and controlling the guest domain via xm console, so I
guess the basic installation of Xen is OK.
However, I am failing to bring up networking for dom0.
The blade''s network setup is as simple as it gets. Just one of its two
ethernet interfaces is used as eth0, configured with static settings
from Debian''s /etc/network/interfaces file.
When the default choice of network-dummy is used as the network startup
script in /etc/xen/xend-config.sxp, the blade has network connectivity.
ifconfig output for eth0 with network-dummy:
# ifconfig
eth0
Link encap:Ethernet HWaddr 00:1A:64:8C:BE:AA
inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:769 errors:0 dropped:0 overruns:0 frame:0
TX packets:433 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:68461 (66.8 KiB) TX bytes:76186 (74.4 KiB)
Interrupt:19 Memory:da000000-da011100
When I change the choice of network script in /etc/xen/xend-config.sxp
to try and bring up networking for Xen, the blade boots up with no
ethernet connectivity. But it seems that the various virtual interfaces
and the bridge for dom0 are configured correctly, here is the output of
ifconfig with bridging enabled:
eth0
Link encap:Ethernet HWaddr 00:1A:64:8C:BE:AA
inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7 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:764 (764.0 b) TX bytes:468 (468.0 b)
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: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)
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:15 errors:0 dropped:0 overruns:0 frame:0
TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1356 (1.3 KiB) TX bytes:732 (732.0 b)
Interrupt:20 Memory:da000000-da011100
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:6 errors:0 dropped:0 overruns:0 frame:0
TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:468 (468.0 b) TX bytes:764 (764.0 b)
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:11 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:958 (958.0 b) TX bytes:0 (0.0 b)
And here is the output of brctl show:
bridge name bridge id STP enabled interfaces
xenbr0 8000.feffffffffff no vif0.0
peth0
And of iptables -L -n -v (just the same as with network-dummy):
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination
Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination
And of route -n (again this is the same as with network-dummy):
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0
eth0
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0
eth0
I am not sure how to troubleshoot this any further. I have read the
background on Xen networking at
http://wiki.xensource.com/xenwiki/XenNetworking and understood the basic
concepts more or less, but there seems to be little information on what
to check if it doesn''t work as described.
Any help would be very much appreciated.
Best regards,
George Karaolides
System Administrator
OTEnet Telecommunications Ltd.
Nicosia, Cyprus
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
George Karaolides
2008-Mar-20 10:12 UTC
Re: [Xen-users] Xen on Debian Etch - no dom0 network
Further to my previous, I have determined that it is possible to set up domU''s on xen with network access when using the network-bridge and vif-bridge scripts. Only dom0 does not have network access. Does anyone have any idea how to troubleshoot this? Best regards, George Karaolides System Administrator OTENet Telecommunications Ltd. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
George Karaolides
2008-Mar-21 08:50 UTC
Re: [Xen-users] Xen on Debian Etch - no dom0 network
Greetings all, On Thu, 2008-03-20 at 12:12 +0200, George Karaolides wrote:> Further to my previous, I have determined that it is possible to set > up domU''s on xen with network access when using the network-bridge and > vif-bridge scripts.I have also found that when I run /etc/xen/scripts/network-bridge stop dom0 recovers its network access. When I run /etc/xen/scripts/network-bridge start dom0 once again loses network access, but domU''s can once again be set up with network access. dom0 and the domU''s all have network access to each other. The issue is only with dom0''s access to the external network. Anyone else having the same problem, or any ideas as to how to troubleshoot further? George Karaolides System Administator OTEnet Telecommunications Ltd. Nicosia, Cyprus _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, Mar 21, 2008 at 10:50:04AM +0200, George Karaolides wrote: Hello,> > Further to my previous, I have determined that it is possible to set > > up domU''s on xen with network access when using the network-bridge and > > vif-bridge scripts. > > I have also found that when I run > > /etc/xen/scripts/network-bridge stop > > dom0 recovers its network access.> Anyone else having the same problem, or any ideas as to how to > troubleshoot further?No problem here but I found that''s easier to not use network-bridge script[1]. You can setup bridge interface in /etc/network/interfaces and configure xend to use network-dummy script. "(network-script network-dummy)" in /etc/xen/xend-config.sxp Install bridge-utils and in /etc/network/interfaces put: auto xen-br0 iface br0 inet static address ... network ... netmask ... broadcast ... gateway ... # bridge setup # eth0 -- outgoing NIC bridge_ports eth0 bridge_stp off bridge_fd 0 Use vif-bridge script in domU configuration normally. Back to your problem -- run commands (while dom0 network has problems): # brctl show # brctl showmacs xen-br0 # ip addr ls Post results to mailing list. Regards, Kupson [1] YMMV. -- Great software without the knowledge to run it is pretty useless. (Linux Gazette #1) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
George Karaolides
2008-Mar-24 07:30 UTC
Re: [Xen-users] Xen on Debian Etch - no dom0 network
Dear Rafał, Thanks for your reply and useful suggestions. On Fri, 2008-03-21 at 12:53 +0100, Rafał Kupka wrote:> Back to your problem -- run commands (while dom0 network has > problems): > # brctl show > # brctl showmacs xen-br0 > # ip addr ls# brctl show bridge name bridge id STP enabled interfaces xenbr0 8000.feffffffffff no vif0.0 peth0 vif1.1 vif1.0 This is with one domU running; domU does have network access; dom0 does not. It is possible to connect to the domU via ssh and then connect to the dom0 from the domU via ssh. # brctl showmacs xenbr0 port no mac addr is local? ageing timer 2 00:14:5e:ce:b5:c9 no 61.11 2 00:14:5e:ce:bb:8f no 89.24 2 00:14:5e:ce:bb:ba no 20.52 2 00:14:5e:ce:bb:bd no 81.96 2 00:14:5e:ce:bb:be no 39.58 2 00:14:5e:ce:bb:c4 no 85.97 2 00:19:56:e3:24:8c no 8.84 2 00:1a:64:8c:77:0e no 123.29 2 00:1a:64:8c:78:0a no 14.64 1 00:1a:64:8c:be:aa no 0.00 2 00:90:7f:3c:47:c3 no 0.00 4 02:00:00:00:00:01 no 0.00 1 fe:ff:ff:ff:ff:ff yes 0.00 00:1a:64:8c:be:aa is the MAC address of the physical eth0 interface 02:00:00:00:00:01 is the MAC address I have assigned to the domU according to the rules in http://wiki.xensource.com/xenwiki/XenNetworking: "In summary, an address of the following form should be OK: XY:XX:XX:XX:XX:XX where X is any hexadecimal digit, and Y is one of 2, 6, A or E." # ip addr ls 1: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: peth0: <BROADCAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff inet6 fe80::fcff:ffff:feff:ffff/64 scope link valid_lft forever preferred_lft forever 3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000 link/ether 00:1a:64:8c:be:ac brd ff:ff:ff:ff:ff:ff 4: vif0.0: <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::fcff:ffff:feff:ffff/64 scope link valid_lft forever preferred_lft forever 5: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue link/ether 00:1a:64:8c:be:aa brd ff:ff:ff:ff:ff:ff inet 192.168.0.1/24 brd 192.168.0.255 scope global eth0 inet6 fe80::21a:64ff:fe8c:beaa/64 scope link valid_lft forever preferred_lft forever 6: vif0.1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff 7: veth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 8: vif0.2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff 9: veth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 10: vif0.3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff 11: veth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 12: sit0: <NOARP> mtu 1480 qdisc noop link/sit 0.0.0.0 brd 0.0.0.0 13: 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 14: vif1.0: <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::fcff:ffff:feff:ffff/64 scope link valid_lft forever preferred_lft forever 15: vif1.1: <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::fcff:ffff:feff:ffff/64 scope link valid_lft forever preferred_lft forever I will also try your suggestion of configuring the bridge via Debian''s interfaces file and using network-dummy as the Xen networking script. Best regards, George Karaolides System Administrator OTEnet Telecommunications Ltd. Nicosia, Cyprus _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users