Bruno,
Try using brctl to manually create the bridge, then pin the nic to the
bridge manually (quick fix), if that works just toss something in init.d
to do so.
Better fix :
I usually find its easier to rename network-script to network-dummy, and
make the bridges in /etc/network/interfaces myself.
/etc/xen/scripts/network-dummy would look like this:
#!/bin/sh
exit 0
chmod +x
Make the change in xend-config.sxp
Then in interfaces :
auto xenbr0
iface xenbr0 inet static
address x.x.x.x
netmask x.x.x.x
network x.x.x.x
broadcast x.x.x.x
gateway x.x.x.x
bridge_fd 0
bridge_maxwait 0
bridge_helo 0
bridge_stp off
bridge_ports eth0
If using hotplug, make sure you tell hotplug about xenbr0.
Secondly, be sure to specify bridge and mac for the dom-u, if you paste
the config file for the dom-u I can give you a hand with that too.
Should look something like :
vif = [ 'bridge=xenbr0 mac=00:00:00:3a:ff:e0' ]
I don't specify the IP in my configs, just do it in the guest.
The network-script that comes with Xen isn't the best to use in a colo
facility where you have a /29 on one side and /32 on the other (typical
vlan).
If still no connectivity, try treating every IP in the dom-u as its
own /32, meaning use subnet mask 255.255.255.255 and the IP itself as
the broadcast / network.
To restart after this, you'll need to be sure all eth devices associated
to a bridge are down, and the bridges are taken down too. Manually do it
with ifdown then /etc/init.d/networking restart
Hope this helps :) If still no luck paste the output of a brctl show
Best,
-Tim
Mine looks like this
On Thu, 2006-11-02 at 21:38 +0100, [EMAIL PROTECTED] wrote:
> Hi,
>
> has anyone experience with a system configuration using xen 3.0.x and vlan
> ?
> The box is connected to a cisco switch via 802.11q and has access to two
> vlans.
>
> in /etc/network/interfaces instead of eth0 only eth0.2 is configured.
>
> auto eth0.2
> iface eth0.2 inet static
> address 10.0.0.1
> netmask 255.255.255.0
>
> The Dom0 can succesfully communicate with the outside world,
> but no DomU can be started regardless what I'm trying in xend-config.sxp,
> the xenbr0 isn't created upon xend-start.
>
> xm create yields:
> "Error: Device 0 (vif) could not be connected. Backend device not found."
>
> (vif-script vif-bridge)
> (network-script 'network-bridge netdev=eth0')
> or
> (network-script 'network-bridge netdev=eth0.2')
>
> TIA for any hints,
> Bruno
> --
> [EMAIL PROTECTED]
>
>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
