Hallo xen-user, after compile and install src/xen-3.3.0 xenbr0 missing. Network to DomU works, but xenbr0 missing. Is xenbr0 no more needed? I need xenbr0 for the binding TAP for qemu on dom0. Whats going wrong? I accomplished some tests. Without result. regards Torsten ----------------------------------------------------------------- lati:~# ifconfig | grep "^[a-z]" eth0 Link encap:Ethernet HWaddr 00:15:C5:BE:8F:93 lo Link encap:Local Loopback peth0 Link encap:Ethernet HWaddr 00:15:C5:BE:8F:93 lati:~# ifconfig -a | grep "^[a-z]" eth0 Link encap:Ethernet HWaddr 00:15:C5:BE:8F:93 lo Link encap:Local Loopback peth0 Link encap:Ethernet HWaddr 00:15:C5:BE:8F:93 veth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 veth1 Link encap:Ethernet HWaddr 00:00:00:00:00:00 veth2 Link encap:Ethernet HWaddr 00:00:00:00:00:00 veth3 Link encap:Ethernet HWaddr 00:00:00:00:00:00 vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF vif0.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF vif0.2 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF vif0.3 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF lati:~# xm create vm1 -c - network to vm1 works. but xenbr0 missing lati:~# brctl show bridge name bridge id STP enabled interfaces eth0 8000.0015c5be8f93 no peth0 vif1.0 vm1 # halt lati:~# ifconfig | grep "^[a-z]" eth0 Link encap:Ethernet HWaddr 00:15:C5:BE:8F:93 lo Link encap:Local Loopback peth0 Link encap:Ethernet HWaddr 00:15:C5:BE:8F:93 lati:~# ifconfig -a | grep "^[a-z]" eth0 Link encap:Ethernet HWaddr 00:15:C5:BE:8F:93 lo Link encap:Local Loopback peth0 Link encap:Ethernet HWaddr 00:15:C5:BE:8F:93 veth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 veth1 Link encap:Ethernet HWaddr 00:00:00:00:00:00 veth2 Link encap:Ethernet HWaddr 00:00:00:00:00:00 veth3 Link encap:Ethernet HWaddr 00:00:00:00:00:00 vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF vif0.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF vif0.2 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF vif0.3 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF lati:~# brctl show bridge name bridge id STP enabled interfaces eth0 8000.0015c5be8f93 no peth0 lati:~# lati:/etc# egrep -v "^#| #" xen*/scripts/* | egrep "xenbr|tmpbridge" xen.old/scripts/network-bridge:bridge=${bridge:-xenbr${vifnum}} xen/scripts/network-bridge:tdev=tmpbridge xen/scripts/vif-bridge: if [ ! -e "/sys/class/net/$bridge" ] && [ -z "${bridge##xenbr*}" ] xen/scripts/vif-bridge: if [ -e "/sys/class/net/eth${bridge#xenbr}/bridge" ]xen/scripts/vif-bridge: bridge="eth${bridge#xenbr}" - xen-3.0: network-bridge:bridge=${bridge:-xenbr${vifnum}} - xen-3.3: network-bridge:tdev=tmpbridge lati:/etc# grep "^(" xen*/xend-config.sxp | egrep "network|bridge" xen.old/xend-config.sxp:(network-script network-bridge) xen.old/xend-config.sxp:(vif-script vif-bridge) xen/xend-config.sxp:(network-script network-bridge) xen/xend-config.sxp:(vif-script vif-bridge) - identical --------------------------------------------------------------- - test1 restart lati:~# /etc/xen/scripts/network-bridge stop lati:~# /etc/xen/scripts/network-bridge start - no errors no xenbr0 --------------------------------------------------------------- - test2 [2] lati:~# ls /var/lib/xend/state cpu.xml host.xml local_sr network.xml pbd.xml pif.xml ppci.xml sr.xml mv /var/lib/xend/state /var/lib/xend/state.old mkdir /var/lib/xend/state - dito --------------------------------------------------------------- - test3 old network-bridge cd /etc /etc/xen/scripts/network-bridge stop cp -a xen xen-3.3.bak cp -a xen.old/scripts//network-bridge xen/scripts/ lati:/etc# /etc/xen/scripts/network-bridge start - no network on dom0 - eth0 missing: lati:/etc# brctl show bridge name bridge id STP enabled interfaces xenbr0 8000.0015c5be8f93 no vif0.0 peth0 # ifconfig | grep "^[a-z]" lo Link encap:Local Loopback peth0 Link encap:Ethernet HWaddr 00:15:C5:BE:8F:93 vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF xenbr0 Link encap:Ethernet HWaddr 00:15:C5:BE:8F:93 -> not usable --------------------------------------------------------------- - test4 (zu test3) # ifconfig eth0 up # ifconfig | grep "^[a-z]" eth0 Link encap:Ethernet HWaddr 00:15:C5:BE:8F:93 lo Link encap:Local Loopback peth0 Link encap:Ethernet HWaddr 00:15:C5:BE:8F:93 vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF xenbr0 Link encap:Ethernet HWaddr 00:15:C5:BE:8F:93 - new: eth0 /etc/init.d/networking restart # ifconfig | grep "^[a-z]" lo Link encap:Local Loopback peth0 Link encap:Ethernet HWaddr 00:15:C5:BE:8F:93 vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF xenbr0 Link encap:Ethernet HWaddr 00:15:C5:BE:8F:93 - eth0 removed --------------------------------------------------------------- - test5 rm -fR /etc/xen src/xen-3.3.0# make install-tools cp -p /etc/xen.old/vm* /etc/xen reboot # ifconfig | grep "^[a-z]" eth0 Link encap:Ethernet HWaddr 00:15:C5:BE:8F:93 lo Link encap:Local Loopback peth0 Link encap:Ethernet HWaddr 00:15:C5:BE:8F:93 - no xenbr0 --------------------------------------------------------------- - test6 ppp0 # pon dsl # xm create vm1 -c # ifconfig | grep "^[a-z]" eth0 Link encap:Ethernet HWaddr 00:15:C5:BE:8F:93 lo Link encap:Local Loopback peth0 Link encap:Ethernet HWaddr 00:15:C5:BE:8F:93 ppp0 Link encap:Point-to-Point Protocol # ifconfig -a | grep "^[a-z]" eth0 Link encap:Ethernet HWaddr 00:15:C5:BE:8F:93 lo Link encap:Local Loopback peth0 Link encap:Ethernet HWaddr 00:15:C5:BE:8F:93 ppp0 Link encap:Point-to-Point Protocol tmpbridge Link encap:Ethernet HWaddr 00:00:00:00:00:00 veth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 veth1 Link encap:Ethernet HWaddr 00:00:00:00:00:00 veth2 Link encap:Ethernet HWaddr 00:00:00:00:00:00 veth3 Link encap:Ethernet HWaddr 00:00:00:00:00:00 vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF vif0.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF vif0.2 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF vif0.3 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF - new: tmpbridge what is tmpbridge? --------------------------------------------------------------- [1] http://lists.xensource.com/archives/html/xen-users/2008-11/msg00626.html [Xen-users] eth0 is down in dom0 [2] http://lists.xensource.com/archives/html/xen-users/2007-05/msg00257.html [Xen-users] Re: network-bridge fails leaving tmpbridge around rm -r /var/lib/xend/state _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Joseph L. Casale
2008-Dec-06 21:43 UTC
RE: [Xen-users] xen-3.3 missing xenbr0 new tmpbridge
>after compile and install src/xen-3.3.0 >xenbr0 missing.>lati:~# brctl show >bridge name bridge id STP enabled interfaces >eth0 8000.0015c5be8f93 no peth0vif1.0 Torsten, Notice your brctl show output? A while ago, xenbr{n} was renamed to match the physical nic name while the physcial nic was renamed to peth{n}, so replace xenbr0 with eth0 in your vif bridge selection in the vm config and use the current scripts... jlc _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks, I should be read my article still another 2. time... xenbr0 was renamed to eth0, but why? On [3] "Xen 3.2+ Networking" written: "eth0 and eth1 are the bridge names..." Me too find it is confusing. [3] http://wiki.xensource.com/xenwiki/XenNetworking it contains network-samples, but no config-examples and predivide and disadvantages. on xend-config.sxp written: ---%<--- # To bridge network traffic, like this: # # dom0: ----------------- bridge -> real eth0 -> the network # | # domU: fake eth0 -> vifN.0 -+ # # use # # (network-script network-bridge) .... # The bridge is named xenbr0, by default. To rename the bridge, use # # (network-script ''network-bridge bridge=<name>'') ---%<--- It seen to be description and working to drift apart. Ok... - Test7 overwrite bridge-name # diff xend-config.sxp.org xend-config.sxp 152c152,153 < (network-script network-bridge) ---> #(network-script network-bridge) > (network-script ''network-bridge bridge=xenbr0'')## network-bridge stop .. start || reboot # brctl show bridge name bridge id STP enabled interfaces eth0 8000.0015c5be8f93 no peth0 -> not working How must it are configured that xenbr0 showing as before version 3.2 ? regards torsten _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Am Sonntag, den 07.12.2008, 20:30 +0100 schrieb Torsten:> Thanks, > > I should be read my article still another 2. time... > xenbr0 was renamed to eth0, but why? > > On [3] "Xen 3.2+ Networking" written: "eth0 and eth1 are the bridge names..." > Me too find it is confusing. > > [3] http://wiki.xensource.com/xenwiki/XenNetworking > > it contains network-samples, but no config-examples and > predivide and disadvantages. > > > on xend-config.sxp written: > ---%<--- > > # To bridge network traffic, like this: > # > # dom0: ----------------- bridge -> real eth0 -> the network > # | > # domU: fake eth0 -> vifN.0 -+ > # > # use > # > # (network-script network-bridge) > .... > # The bridge is named xenbr0, by default. To rename the bridge, use > # > # (network-script ''network-bridge bridge=<name>'') > > ---%<--- > > It seen to be description and working to drift apart. > > Ok... > > - Test7 overwrite bridge-name > > # diff xend-config.sxp.org xend-config.sxp > 152c152,153 > < (network-script network-bridge) > --- > > #(network-script network-bridge) > > (network-script ''network-bridge bridge=xenbr0'') > > ## network-bridge stop .. start || reboot > > # brctl show > bridge name bridge id STP enabled interfaces > eth0 8000.0015c5be8f93 no peth0 > > -> not working > > How must it are configured that xenbr0 showing as before version 3.2 ?i would recommend to write your own network-script something like # vim /etc/xen/script/network-mynet ---------snip---------------- #!/bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 netdev=eth0 bridge=xenbr0 ------------snap------- # chmod +x /etc/xen/script/network-mynet edit xend-config.sxp # /etc/init.d/xend restart should do the job.> > regards torstenhth, Thomas _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Sun, Dec 7, 2008 at 2:30 PM, Torsten <tlehmann@fh-lausitz.de> wrote:> Thanks, > > I should be read my article still another 2. time... > xenbr0 was renamed to eth0, but why? >The reason for the change for xenbr0 to eth0: http://xen.markmail.org/search/?q=xenbr0+eth0+list%3Acom.xensource.lists.xen-devel+rename#query:xenbr0%20eth0%20list%3Acom.xensource.lists.xen-devel%20rename+page:3+mid:t4amamj24lk2cswx+state:results Cheers, Todd -- Todd Deshane http://todddeshane.net http://runningxen.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users