so I looked into it some more. I have a work around that I can live with (for now). Better solutions and working on the box are going to be for hardy hopefully.
I noticed that I got the following errors in /etc/xen/xend-debug.log: ifdown: interface eth0 not configured SIOCSIFNAME: Device or resource busy So, I stopped xend and tried /etc/xen/scripts/network-bridge star manually and the same errors appeared...: #/etc/xen/scripts/network-bridge start ifdown: interface eth0 not configured SIOCSIFNAME: Device or resource busy So, I remove network-manager and added the following to /etc/network/interfaces: auto eth0 iface eth0 inet dhcp I now I have networking in my guest. (Also, don't forget to restart xend) I rebooted the guest and networking still works by the way. Another thing to note is that if you have multiple network cards xen can't always automatically figure out which one to use as the bridge. So, if you don't need the network card you can take it out. Or carefully specify in /etc/xen/xend-config.sxp. Or if you just don't want a card to show up you can hide it from dom0. In this case it can actually be used by a guest directly too... To hide it add the pciback stuff to the dom0 kernel command line, an example follows: module /boot/vmlinuz-2.6.22-14-xen root=UUID=6af9903c-e2ee-4fe3-86e2-3601d97131a2 ro console=tty0 pciback.permissive pciback.hide=(03:00.0) If you then want a guest to be able to use that card instead, you can then use something like pci='03:00.0' in the guest config file. I use 03:00.0 since that is the card i wanted to hide. I determined this with the lspci command as below. # lspci | grep net 03:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5754 Gigabit Ethernet PCI Express (rev 02) 04:02.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10) More testing will be needed, but at least it is in a working state. Hope that helps. -- domU fails to get network connection https://bugs.launchpad.net/bugs/150805 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
