Hi, I am using Xen 3.0.2 on SUSE SLES 10. I have created a script in /etc/xen/scripts called "network-mybridges" and use two lines to setup xenbr0 and xenbr1. When executed manually the script works fine and creates xenbr0 and xenbr1. I can then xm create -c <vmname>. with absolutely no issues. It just won''t work at boot time. It appears that the vif-bridge script is shutting down and deleting the devices (xenbr) at boot time instead of bringing them up. The script is configured into /etc/xen/xend-config.sxp. Here is an excerpt from /var/log/messages: 2357 May 31 16:57:04 zeus kernel: eth1: no IPv6 routers present 2358 May 31 16:57:04 zeus logger: /etc/xen/scripts/vif-bridge: online XENBUS_ PATH=backend/vif/1/0 2359 May 31 16:57:04 zeus logger: /etc/xen/scripts/block: add XENBUS_PATH=bac kend/vbd/1/768 2360 May 31 16:57:04 zeus logger: /etc/xen/scripts/vif-bridge: online XENBUS_ PATH=backend/vif/1/1 2361 May 31 16:57:04 zeus logger: /etc/xen/scripts/block: add XENBUS_PATH=bac kend/vbd/1/832 Thanks in advance, Tony 2362 May 31 16:57:04 zeus kernel: NET: Registered protocol family 17 2363 May 31 16:57:04 zeus ifup: vif1.0 2364 May 31 16:57:04 zeus ifup: No configuration found for vif1 .0 2365 May 31 16:57:04 zeus ifup: vif1.1 2366 May 31 16:57:04 zeus ifup: No configuration found for vif1 .1 2367 May 31 16:57:04 zeus logger: /etc/xen/scripts/block: Writing backend/vbd /1/768/node /dev/loop0 to xenstore. 2368 May 31 16:57:04 zeus logger: /etc/xen/scripts/block: Writing backend/vbd /1/768/physical-device 7:0 to xenstore. 2369 May 31 16:57:04 zeus logger: /etc/xen/scripts/block: Writing backend/vbd /1/768/hotplug-status connected to xenstore. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Tony! Maybe not a solution to your problem, but it may help you to reach the target: I played around with that for days without getting it solved, so I left that interface thing out of Xen. Means: Configure the Bridges and Interfaces and all that acc. to your distro, e.g. ifcfg-xenbr0, ifcfg-xenbr1, ifcfg-eth0, ... on Redhat (I can provide the infos, if you need them). Also just replace the network-script with a network-script-dummy, which simply does nothing. With that method I managed it to have VLANs on bonding interfaces bridged into xenbr0 and xenbr1. But keep the names xenbr0 and xenbr1 - they are used too often somewhere ;-) Br Walter -----Original Message----- From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Anthony G Angerame Sent: Sunday, June 10, 2007 2:32 AM To: xen-users@lists.xensource.com Subject: [Xen-users] Multiple Bridges Fail to Start Hi, I am using Xen 3.0.2 on SUSE SLES 10. I have created a script in /etc/xen/scripts called "network-mybridges" and use two lines to setup xenbr0 and xenbr1. When executed manually the script works fine and creates xenbr0 and xenbr1. I can then xm create -c <vmname>. with absolutely no issues. It just won''t work at boot time. It appears that the vif-bridge script is shutting down and deleting the devices (xenbr) at boot time instead of bringing them up. The script is configured into /etc/xen/xend-config.sxp. Here is an excerpt from /var/log/messages: 2357 May 31 16:57:04 zeus kernel: eth1: no IPv6 routers present 2358 May 31 16:57:04 zeus logger: /etc/xen/scripts/vif-bridge: online XENBUS_ PATH=backend/vif/1/0 2359 May 31 16:57:04 zeus logger: /etc/xen/scripts/block: add XENBUS_PATH=bac kend/vbd/1/768 2360 May 31 16:57:04 zeus logger: /etc/xen/scripts/vif-bridge: online XENBUS_ PATH=backend/vif/1/1 2361 May 31 16:57:04 zeus logger: /etc/xen/scripts/block: add XENBUS_PATH=bac kend/vbd/1/832 Thanks in advance, Tony 2362 May 31 16:57:04 zeus kernel: NET: Registered protocol family 17 2363 May 31 16:57:04 zeus ifup: vif1.0 2364 May 31 16:57:04 zeus ifup: No configuration found for vif1 .0 2365 May 31 16:57:04 zeus ifup: vif1.1 2366 May 31 16:57:04 zeus ifup: No configuration found for vif1 .1 2367 May 31 16:57:04 zeus logger: /etc/xen/scripts/block: Writing backend/vbd /1/768/node /dev/loop0 to xenstore. 2368 May 31 16:57:04 zeus logger: /etc/xen/scripts/block: Writing backend/vbd /1/768/physical-device 7:0 to xenstore. 2369 May 31 16:57:04 zeus logger: /etc/xen/scripts/block: Writing backend/vbd /1/768/hotplug-status connected to xenstore. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Schober Walter wrote:> Hi Tony! > > Maybe not a solution to your problem, but it may help you to reach the > target: > I played around with that for days without getting it solved, so I left > that interface thing out of Xen. Means: Configure the Bridges and > Interfaces and all that acc. to your distro, e.g. ifcfg-xenbr0, > ifcfg-xenbr1, ifcfg-eth0, ... on Redhat (I can provide the infos, if you > need them). > Also just replace the network-script with a network-script-dummy, which > simply does nothing. > > With that method I managed it to have VLANs on bonding interfaces > bridged into xenbr0 and xenbr1. > But keep the names xenbr0 and xenbr1 - they are used too often somewhere > ;-) > > Br > Walter > > -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Anthony G > Angerame > Sent: Sunday, June 10, 2007 2:32 AM > To: xen-users@lists.xensource.com > Subject: [Xen-users] Multiple Bridges Fail to Start > > Hi, > > > I am using Xen 3.0.2 on SUSE SLES 10. I have created a > script in /etc/xen/scripts called "network-mybridges" and > use two lines to setup xenbr0 and xenbr1. When executed > manually the script works fine and creates xenbr0 and > xenbr1. I can then xm create -c <vmname>. with absolutely > no issues. It just won''t work at boot time. It appears > that the vif-bridge script is shutting down and deleting > the devices (xenbr) at boot time instead of bringing them > up. The script is configured into > /etc/xen/xend-config.sxp. > > Here is an excerpt from /var/log/messages: > > 2357 May 31 16:57:04 zeus kernel: eth1: no IPv6 routers > present > > 2358 May 31 16:57:04 zeus logger: > /etc/xen/scripts/vif-bridge: online XENBUS_ > PATH=backend/vif/1/0 2359 May 31 16:57:04 zeus logger: > /etc/xen/scripts/block: add XENBUS_PATH=bac kend/vbd/1/768 > 2360 May 31 16:57:04 zeus logger: > /etc/xen/scripts/vif-bridge: online XENBUS_ > PATH=backend/vif/1/1 2361 May 31 16:57:04 zeus logger: > /etc/xen/scripts/block: add XENBUS_PATH=bac kend/vbd/1/832 > > > Thanks in advance, > > > Tony > 2362 May 31 16:57:04 zeus kernel: NET: Registered > protocol family 17 > 2363 May 31 16:57:04 zeus ifup: vif1.0 > > 2364 May 31 16:57:04 zeus ifup: No configuration found for > vif1 .0 2365 May 31 16:57:04 zeus ifup: vif1.1 2366 May 31 > 16:57:04 zeus ifup: No configuration found for vif1 .1 > 2367 May 31 16:57:04 zeus logger: /etc/xen/scripts/block: > Writing backend/vbd /1/768/node /dev/loop0 to xenstore. > 2368 May 31 16:57:04 zeus logger: /etc/xen/scripts/block: > Writing backend/vbd /1/768/physical-device 7:0 to > xenstore. 2369 May 31 16:57:04 zeus logger: > /etc/xen/scripts/block: Writing backend/vbd > /1/768/hotplug-status connected to xenstore. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >Walter, Hmmmm well hopefully in the next release (Coming soon?). I know it''s in the timing of the startup so I may play with that. Thanks for your reply it''s nice to know it is an error others are experiencing. If you have any more info please pass it on and I will likewise let you know what I come up with. Thanks, Tony _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Walter, I`d be very interested in your config files. I`m hitting the wall with a reliable bridging configuration for a dualhomed dom0 for a couple days now: either xenbr0 or xenbr1 come up, the vif counter in dom0 increases, the w2k3 detects a new nic (Lan5, currently) - each time the vm is started. And of course no networking from domU to dom0. After i have tried anything, even specifically naming the vif in the configuration of the vm, but to no avail. in the vm configuration i have: vif = [ ''vifname=vm1, type=ioemu, mac=00:16:3e:00:0e:11, bridge=xenbr0, model=pcnet'' ] but it results always in log entries like the following: kernel: ADDRCONF(NETDEV_UP): vm1: link is not ready kernel: xenbr0: port 2(vm1) entering disabled state kernel: device vm1 left promiscuous mode kernel: audit(1181574843.162:9): dev=vm1 prom=0 old_prom=256 auid=4294967295 (Without the vifname directive, the above lines show the vif name). On 6/10/07, Schober Walter <Walter.Schober@neotel.at> wrote:> Hi Tony! > > Maybe not a solution to your problem, but it may help you to reach the > target:... (I can provide the infos, if you> need them)...> Br > Waltermany thanks in advance, Dirk _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello Dirk!
My config is as following:
-------------------- VLAN55
|
------- Xen Host -----------------<|>---- Xen Guests
| bond0.55 --- xenbr0 -- vif/tap -- eth0
|
| bond0.20 --- xenbr1 -- vif/tap -- eth1
-------
|
-------------------- VLAN20
My IP for the host is on xenbr0/1, the vif/veth stuff has the big
drawback, that Host networking doesn''t work anymore, if xend is
stopped.
Wouldn''t be that bad, if a "xend stop" would call the
"network-script
stop" as well, but it doesn''t...
So I do not use veth at all. No interface renaming, nothing. Pure Host
networking config. All xen does, is adding a guest to a bridge.
BTW: I use Xen 3.1 compiled from the sources for x86_64 machine (HP
DL360-G5 Dual Quad Core) on a CentOS 5 installation. Can''t wait for
CentOS 5 w/ 3.1 packaged in ;-)
**************************************************************
Host
**************************************************************
xend-config.sxp:
---
(network-script network-bridge-dummy)
(vif-script ''vif-bridge bridge=xenbr1'') # to make the inside
LAN the
default, if not spec. in config file
network-bridge-dummy
---
<empty file>
vif-bridge
---
removed that line: handle_iptable.
I manage my iptable rules with FWBuilder myself.
/etc/sysconfig/network-script scripts:
---
ifcfg-eth0
---
DEVICE=eth0
HWADDR=00:1a:4b:12:34:56
BOOTPROTO=static
MACADDR=0a:00:00:A6:4C:1E <- I do set the MAC here, so bonding
doesn''t
go into prom. mode on a switch
ONBOOT=yes
MASTER=bond0
SLAVE=yes
ifcfg-eth1
---
DEVICE=eth1
HWADDR=00:1A:4B:12:34:66
BOOTPROTO=static
MACADDR=0a:00:00:A6:4C:06
ONBOOT=yes
MASTER=bond0
SLAVE=yes
ifcfg-bond0 --- has to be present. Anyone knows how to use that native
lan w/ bridging, too?
---
DEVICE=bond0
ONBOOT=yes
BOOTPROTO=none
ifcfg-bond0.20
---
DEVICE=bond0.20
VLAN=yes
ONBOOT=yes
BOOTPROTO=none
BRIDGE=xenbr1
ifcfg-bond0.55
---
DEVICE=bond0.55
VLAN=yes
ONBOOT=yes
BOOTPROTO=none
BRIDGE=xenbr0
ifcfg-xenbr0 (analog xenbr1)
---
DEVICE=xenbr0 (->xenbr1)
ONBOOT=yes
BOOTPROTO=static
IPADDR=1.2.3.4
NETMASK=255.255.255.224
GATEWAY=1.2.3.9
TYPE=Bridge
DELAY=0
STP=off
Do the rest on xenbr0 and xenbr1 as you like. E.g. set your routes:
route-xenbr1
---
ADDRESS0=192.168.40.0
NETMASK0=255.255.248.0
GATEWAY0=192.168.45.254
**************************************************************
Guest
**************************************************************
PV Guest:
-------------- cut ----------------
kernel = "/boot/vmlinuz-2.6.18-xen.x86_32p"
ramdisk = "/boot/initrd-2.6.18-xen.x86_32p.img"
memory = "128"
name = "pv-1"
vif = [''mac=00:16:3e:12:ad:71, bridge=xenbr0'',
''mac=00:16:3e:12:ad:72,
bridge=xenbr1'', ]
disk = [''phy:vg00/p10_root,xvda1,w'',
''tap:qcow:/xen/vs2x_usr.img,xvda2,r'', ]
root = "/dev/xvda1 ro"
apic=1
acpi=1
pae=1
vcpus=4
on_reboot = ''restart''
on_crash = ''restart''
on_shutdown = ''destroy''
#vnc = 1
#vfb = [ ''type=vnc,vncdisplay=22,vnclisten=0.0.0.0'' ]
#usbdevice = ''mouse''
#keymap = ''de''
#serial = ''pty'' # enable serial console
sdl=0
-------------- cut ----------------
HVM Guest:
-------------- cut ----------------
name = "hvm-1"
# --- HVM Params
builder = "hvm"
memory = "512"
device_model = "/usr/lib64/xen/bin/qemu-dm"
kernel = "/usr/lib/xen/boot/hvmloader"
# Try to boot from HD first, then CDROM
boot = ''cd''
#disk = [ ''phy:/dev/vg00/vsXX_root,hda1,w'',
''tap:qcow:/xen/vsXX-usr.img,hda2,w'',
''file:/mnt/backup/mirrors/centos/5.0/i386/CentOS-5.
0-i386-bin-DVD.iso,hdc:cdrom,r'']
# Installation Media on /dev/hdc
#disk = [ ''file:/xen/vs2x.img,hda,w'',
''file:/mnt/backup/mirrors/centos/5.0/i386/CentOS-5.0-i386-bin-DVD.iso,hd
c:cdrom,r'']
disk = [ ''file:/xen/vs2x.img,hda,w'', ]
#vif = [ ''type=ioemu, mac=00:16:3e:12:ad:91, bridge=xenbr0'',
''type=ioemu, mac=00:16:3e:12:ad:92, bridge=xenbr1'']
vif = [ ''type=ioemu, bridge=xenbr0'', ''type=ioemu,
bridge=xenbr1'']
apic=1
acpi=1
pae=1
vcpus=1
on_reboot = ''restart''
on_crash = ''restart''
on_shutdown = ''destroy''
vnc = 1
vfb = [ ''type=vnc,vncdisplay=21,vnclisten=0.0.0.0'' ]
usbdevice = ''mouse''
keymap = ''de''
serial = ''pty'' # enable serial console
sdl=0
-------------- cut ----------------
May it help someone out there!
br
Walter
> -----Original Message-----
> From: Dirk Westfal [mailto:dwestfal@googlemail.com]
> Sent: Monday, June 11, 2007 7:51 PM
> To: Schober Walter
> Cc: xen-users@lists.xensource.com
> Subject: Re: [Xen-users] Multiple Bridges Fail to Start
>
> Hi Walter,
>
> I`d be very interested in your config files.
> I`m hitting the wall with a reliable bridging configuration for a
> dualhomed dom0 for a couple days now:
> either xenbr0 or xenbr1 come up, the vif counter in dom0 increases,
> the w2k3 detects a new nic (Lan5, currently) - each time the vm is
> started. And of course no networking from domU to dom0.
> After i have tried anything, even specifically naming the vif in the
> configuration of the vm, but to no avail.
>
> in the vm configuration i have:
> vif = [ ''vifname=vm1, type=ioemu, mac=00:16:3e:00:0e:11,
> bridge=xenbr0, model=pcnet'' ]
>
> but it results always in log entries like the following:
> kernel: ADDRCONF(NETDEV_UP): vm1: link is not ready
> kernel: xenbr0: port 2(vm1) entering disabled state
> kernel: device vm1 left promiscuous mode
> kernel: audit(1181574843.162:9): dev=vm1 prom=0 old_prom=256
> auid=4294967295
>
> (Without the vifname directive, the above lines show the vif name).
>
> On 6/10/07, Schober Walter <Walter.Schober@neotel.at> wrote:
> > Hi Tony!
> >
> > Maybe not a solution to your problem, but it may help you
> to reach the
> > target:
> ...
> (I can provide the infos, if you
> > need them).
> ..
> > Br
> > Walter
>
> many thanks in advance,
> Dirk
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users