Weblog entry #4 for shortpath
See all weblog entries made by shortpath.
Today, I fired up the box, had networking on Dom0 working but using the network-dummy script and used xen-tools to install a DomU using debootstrap. When I started the DomU, it failed on the network device. Doh. Set network-bridge in the xen config file, restart xend, and it worked. Right on. So now I have an amd64 etch Dom0 running an amd64 etch DomU.
Watching kernel messages, it seemed that the xen bridge and virtual interfaces are not brought up until a DomU is started. Networking was fine as soon as I had a guest running. Maybe one day I'll know enough to sort it out, but I bet someone beats me to it.
Comments on this Entry
What helped me was removing the hotplug stuff from /etc/networking/interfaces and declare them 'auto ethX' instead.
[ Parent | Reply to this comment ]
[ Parent | Reply to this comment ]
[ Parent | Reply to this comment ]
[ Parent | Reply to this comment ]
I bring up the bridge via /etc/network/interfaces:
auto xenbridge-e1000
iface xenbridge-e1000 inet static
address 172.16.0.2
netmask 255.255.255.0
network 172.16.0.0
bridge_ports eth-e1000
(I've renamed the interfaces via udev, but it should work as well with
bridge_ports eth0, or something like that)
And have in my /etc/xen/xend-config.sxp:
(network-script network-dummy)
Network is working from the bootup regardless of any DomU running or not.
I did the same and it worked fine, without the udev renaming.
[ Parent | Reply to this comment ]
Thanks for your response.
Not knowing how to rename the interfaces via udev, and seeing that it should work as well with bridge_ports eth0, I've now changed my /etc/network/interfaces from what it was originally . . .
# The loopback network interface auto lo iface lo inet loopback # The primary network interface allow-hotplug eth0 iface eth0 inet dhcp auto eth0
. . . to:
# The loopback network interface auto lo iface lo inet loopback # The primary network interface iface xenbridge-e1000 inet dhcp bridge_ports eth0 auto xenbridge-e1000
(What's xenbridge-e1000?)
I've left out the address, netmask and network lines on the assumption that they are inappropriate given that I'm using DHCP. Just a guess, really.
Anyway, long story short: still no connection. I won't have time to look at this for another week but thanks for your help.
[ Parent | Reply to this comment ]
[ Parent | Reply to this comment ]
auto xenbr0
iface xenbr0 inet static
address xxx.xxx.xxx.xxx
netmask xxx.xxx.xxx.xxx
network xxx.xxx.xxx.xxx
bridge_ports eth0
The address, netmask, and network settings were the static settings for eth0, so now the bridge is brought up using those settings with eth0 as a part of the bridge. You said you were using dhcp, so you could probably do something like
auto xenbr0
iface xenbr0 inet dhcp
bridge_ports eth0
Heh, now that I look back at your post, that's exactly what you're doing. I think all you need to change is 'xenbridge-e1000' to 'xenbr0' (the default name for the xen bridge).
[ Parent | Reply to this comment ]
So now /etc/network/interfaces looks like this:
# The loopback network interface auto lo iface lo inet loopback # The primary network interface iface xenbr0 inet dhcp bridge_ports eth0 auto xenbr0
Running ifconfig xenbr0 returns this:
xenbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:31 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:9018 (8.8 KiB)
Note: still no IP address after running /etc/init.d/networking restart
What strikes me at this point is the HWaddr 00:00:00:00:00:00. All those 0's look curious.
But before you spend any more time helping me, I'll just let you know that I'm going to re-direct my efforts to something else I've just discovered: Qemu. Given that installing Xen involves installing (and keeping up-to-date) its own kernel and that Qemu doesn't, I'm thinking now that Xen might be overkill for the effect I'm looking for: having a Linux machine on which I can switch to Windows from time to time without re-booting.
Thanks again for your blog entry and responses.
[ Parent | Reply to this comment ]