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@xxxxxxxxxxxxxx]
> Sent: Monday, June 11, 2007 7:51 PM
> To: Schober Walter
> Cc: xen-users@xxxxxxxxxxxxxxxxxxx
> 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@xxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home