From: Paolo Marinelli <paolo.marinelli@vulcaniasystem.it>
To: xen-devel@lists.xensource.com
Subject: Wrong bheavior on vif and bridge assignement xen-2.0-testing 20050927
Date: Wed, 28 Sep 2005 15:02:09 +0200 [thread overview]
Message-ID: <433A9451.8070909@vulcaniasystem.it> (raw)
For special purpose i need multi bridge hostmachine
xenbr0
eth0 (for lan and guest lan domU)
xenbr1
eth1 (for wan)
xenbr2
for standalone domU
domU-0.cfg
kernel = "/home/xen/kernel/vmlinuz-2.6.12-xenU"
memory = 64
name = "domU-0"
ip = "192.168.20.249"
netmask = "255.255.255.0"
gateway = "192.168.20.5"
hostname = "domU-0"
nics = 1
vif = ['mac=AE:DA:C0:A8:14:F9','bridge=xenbr0']
disk = ['phy:vg01/domU-0,sda1,w']
root = "/dev/sda1 ro"
domU-2.cfg
kernen = "/home/xen/kernel/vmlinuz-2.6.12-xenU"
memory = 64
name = "domU-2"
ip = "192.168.24.251"
netmask = "255.255.255.0"
gateway = "192.168.24.5"
hostname = "domU-2"
nics = 1
vif = ['mac=AE:DA:C0:A8:14:FA','bridge=xenbr2']
disk = ['phy:vg01/domU-2,sda1,w']
root = "/dev/sda1 ro"
ifconfig
eth0 Link encap:Ethernet HWaddr 00:11:25:AA:74:0E
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:27338 errors:0 dropped:0 overruns:0 frame:0
TX packets:9160 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3305171 (3.1 MiB) TX bytes:1059713 (1.0 MiB)
Base address:0x2000 Memory:d0120000-d0140000
eth1 Link encap:Ethernet HWaddr 00:13:49:09:D9:4C
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:17 Base address:0x2000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:10466 errors:0 dropped:0 overruns:0 frame:0
TX packets:10466 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:832274 (812.7 KiB) TX bytes:832274 (812.7 KiB)
xenbr0 Link encap:Ethernet HWaddr 00:11:25:AA:74:0E
inet addr:192.168.20.2 Bcast:192.168.20.255
Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:21616 errors:0 dropped:0 overruns:0 frame:0
TX packets:3747 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2049862 (1.9 MiB) TX bytes:518771 (506.6 KiB)
xenbr1 Link encap:Ethernet HWaddr 00:13:49:09:D9:4C
inet addr:XXX.XXX.XXX.XXX Bcast:XXX.XXX.XXX.XXX
Mask:255.255.255.248
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:168 (168.0 b)
xenbr2 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:192.168.24.5 Bcast:192.168.24.255
Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:16 errors:0 dropped:0 overruns:0 frame:0
TX packets:55 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1232 (1.2 KiB) TX bytes:3710 (3.6 KiB)
brctl show
xenbr0 8000.001125aa740e no eth0
xenbr1 8000.00134909d94c no eth1
xenbr2 8000.000000000000 no can't get
port info: Fu nction not implemented
----------------------------------------------------------------------------
Now start xenbr0 domU
xm create -c domU-0.cfg
ifconfig
...
vif11.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:47 errors:0 dropped:0 overruns:0 frame:0
TX packets:39 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3828 (3.7 KiB) TX bytes:5572 (5.4 KiB)
vif11.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:3 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
...
brctl show
xenbr0 8000.001125aa740e no eth0
vif11.0
vif11.1
xenbr1 8000.00134909d94c no eth1
xenbr2 8000.000000000000 no can't
get port info: Function not implemented
ssh 192.168.20.249
All OK
----------------------------------------------------------------------------
Now start xenbr2 domU
xm create -c domU-2.cfg
ifconfig
...
vif12.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:19 errors:0 dropped:0 overruns:0 frame:0
TX packets:67 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1122 (1.0 KiB) TX bytes:8352 (8.1 KiB)
vif12.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:3 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
...
brctl show
bridge name bridge id STP enabled interfaces
xenbr0 8000.001125aa740e no eth0
vif11.0
vif11.1
vif12.0
xenbr1 8000.00134909d94c no eth1
xenbr2 8000.feffffffffff no vif12.1
LOOK AT vif12.X different bridge !
ssh 192.168.20.249
FAILED
i must change manually vif assigniment
brctl delif xenbr0 vif12.0
brctl addif xenbr2 vif12.0
ssh 192.168.20.249
ALL OK
----------------------------------------------------------------------------
Investigation:
log of /etc/xen/scripts/vif-bridge
vif-bridge up vif=vif12.0 domain=squirrelmail mac=ae:da:c0:a8:14:fb
bridge=xenbr0
vif-bridge up vif=vif12.1 domain=squirrelmail mac=aa:00:00:1f:d2:ce
bridge=xenbr2
it pass xenbr2 only for .1 interfaces for xenbr0
FINAL:
xend create and associate bridge for vifX.0 based on
/etc/xen/xend-config.sxp
create and associate bridge for vifX.1 based on
/etc/xen/auto/domU.cfg
this work only for 1 bridge configuration
Now i make a orrible workaround with vif-bridge script
but it should be corrected on xend daemon (i suppose)
bye
reply other threads:[~2005-09-28 13:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=433A9451.8070909@vulcaniasystem.it \
--to=paolo.marinelli@vulcaniasystem.it \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.