Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have 3 NICs that I want to be seen by my domU, even though they're not configured in dom0.

Here's my sample lines from interfaces file

auto lo
iface lo inet loopback

# Local network, cable labeled M3
auto eth0
allow-hotplug eth0
iface eth0 inet static
        address 192.168.1.184
        netmask 255.255.255.0
        gateway 192.168.1.1

# cable labeled M1
auto eth1
allow-hotplug eth1
iface eth1 inet manual
        hwaddress ether 00:19:5B:33:86:D5
        up ifconfig eth1 up

# cable labeled M2
auto eth2
allow-hotplug eth2
iface eth2 inet manual
        hwaddress ether 00:19:5B:33:86:D3
        up ifconfig eth2 up

I'm trying to use multiple bridge configuration with xend, but it complains about the "Link not in running state" and interface being down, although I can see them in ifconfigs' output.

What are my options to make those NICs visible in domU without configuring them in dom0?

share|improve this question
    
Show us your entire /e/n/interfaces file. I have a strong suspicion you're doing something really unwise, because the same layout works fine for me on my dom0s. –  womble Jun 17 '09 at 11:40
    
Updated as per your request –  Karolis T. Jun 17 '09 at 11:46

1 Answer 1

up vote 4 down vote accepted

Oh dear... I think you're trying to use the Xen bridging stuff, which is just dire. Set network-script network-dummy in xend-config.sxp, then go with this config:

iface lo
iface lo inet loopback

# Local network, cable labeled M3
auto eth0
allow-hotplug eth0
iface eth0 inet static
    address 192.168.1.184
    netmask 255.255.255.0
    gateway 192.168.1.1

# cable labeled M1
iface eth1 inet manual
    hwaddress ether 00:19:5B:33:86:D5

# cable labeled M2
iface eth2 inet manual
    hwaddress ether 00:19:5B:33:86:D3

auto br-eth1
iface br-eth1 inet manual
  bridge_ports eth1

auto br-eth2
iface br-eth2 inet manual
  bridge_ports eth2

What you then do is tell the domUs to use either the br-eth1 or br-eth2 bridge (as appropriate). Given that you've got cable labelling happening, I'd change the bridge names to something more useful, like perhaps m1 and m2.

share|improve this answer
    
I agree. As a rule of thumb, avoid using Xen networking scripts. It's not so complex to do things yourself and leads to much better results. –  Antoine Benkemoun Jun 17 '09 at 12:02
    
Thanks a lot, the idea of manually bridging interfaces didn't even occur to me. What is wrong with XEN native bridging scripts? –  Karolis T. Jun 17 '09 at 12:11
1  
They're excessively complicated, and don't follow standard conventions for bridging configuration, which makes it harder to manage and maintain. –  womble Jun 17 '09 at 12:16
    
I can't vote this up enough. The Xen bridge setup scripts are just dreadful. –  Jeff Snider Oct 26 '09 at 4:05

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.