Short Version; Need documentation on second interface in for Xen4.0 on debian squeeze for hvm and paravirt domU''s. Long Version; I am looking for something definitive on multi-network configurations in xen 4.0. I have tried both of these; wiki.debian.org/Xen#Dom0_.28host.29 and searchservervirtualization.techtarget.com/tip/Creating-additional-Xen-virtual-network-bridges I can create the interface after it is booted with this command; ./network-bridge netdev=eth1 bridge=xenbr1 start and it gives me a bridge; root@xen-07:/var/log/xen# brctl show bridge name bridge id STP enabled interfaces eth0 8000.0026b9fedf98 no peth0 xenbr1 8000.0026b9fedf9a no peth1 tap7.0 vif7.0 But my domU''s can not see that interface. Finally on the xen wiki I found this but I am unsure what it means; vif = [ ''mac=00:16:5e:72:04:01,bridge=xenbr0,script=your_custom_script1'', ''mac=00:16:5e:72:04:02,bridge=xenbr1,script=your_custom_script2'' ] Mostly because I never get a xenbr0 here is my ifconfig print out; root@hou-xen-07:~# ifconfig eth0 Link encap:Ethernet HWaddr 00:26:b9:fe:df:98 inet addr:10.0.14.153 Bcast:10.0.14.255 Mask:255.255.255.0 inet6 addr: fe80::226:b9ff:fefe:df98/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:171813 errors:0 dropped:0 overruns:0 frame:0 TX packets:15362 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:22392933 (21.3 MiB) TX bytes:2287966 (2.1 MiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8483 errors:0 dropped:0 overruns:0 frame:0 TX packets:8483 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1103730 (1.0 MiB) TX bytes:1103730 (1.0 MiB) peth0 Link encap:Ethernet HWaddr 00:26:b9:fe:df:98 inet6 addr: fe80::226:b9ff:fefe:df98/64 Scope:Link UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:219181 errors:0 dropped:0 overruns:0 frame:0 TX packets:40454 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:82814249 (78.9 MiB) TX bytes:4307386 (4.1 MiB) Interrupt:36 Memory:da000000-da012800 peth1 Link encap:Ethernet HWaddr 00:26:b9:fe:df:9a inet6 addr: fe80::226:b9ff:fefe:df9a/64 Scope:Link UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:57686 errors:0 dropped:0 overruns:0 frame:0 TX packets:18 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3789122 (3.6 MiB) TX bytes:1476 (1.4 KiB) Interrupt:48 Memory:dc000000-dc012800 tap7.0 Link encap:Ethernet HWaddr 3a:e1:76:b6:69:7f inet6 addr: fe80::38e1:76ff:feb6:697f/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:21534 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:0 (0.0 B) TX bytes:1253292 (1.1 MiB) vif7.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:21534 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) xenbr1 Link encap:Ethernet HWaddr 00:26:b9:fe:df:9a inet addr:10.0.11.87 Bcast:0.0.0.0 Mask:255.255.255.0 inet6 addr: fe80::226:b9ff:fefe:df9a/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:57164 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2526816 (2.4 MiB) TX bytes:468 (468.0 B) I am sure it is not working ... cause I am not doing it right. Any help would be appreciated. I currently run debian squeeze and xen4.0. regards, E./ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com lists.xensource.com/xen-users
On Tue, Aug 9, 2011 at 7:33 PM, EredicatorX <eredicatorx@hugedesigns.net> wrote:> Short Version; > Need documentation on second interface in for Xen4.0 on debian squeeze for > hvm and paravirt domU''s. >Setting up networking manually is the easiest way to accomplish this: wiki.xensource.com/xenwiki/HostConfiguration/Networking (Xen 4.1 is not required) You can simply add two bridge entries to your interfaces file. Also disable the bridge scripts in the xend config. Thanks, Todd -- Todd Deshane linkedin.com/in/deshantm xen.org/products/cloudxen.html runningxen.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com lists.xensource.com/xen-users
On Wed, Aug 10, 2011 at 6:33 AM, EredicatorX <eredicatorx@hugedesigns.net> wrote:> Short Version; > Need documentation on second interface in for Xen4.0 on debian squeeze for > hvm and paravirt domU''s. > > Long Version; > > I am looking for something definitive on multi-network configurations in xen > 4.0. I have tried both of these; > > wiki.debian.org/Xen#Dom0_.28host.29 > and > searchservervirtualization.techtarget.com/tip/Creating-additional-Xen-virtual-network-bridges > > I can create the interface after it is booted with this command; > ./network-bridge netdev=eth1 bridge=xenbr1 startNot recommended. Like Todd said, better setup bridges manually, something like wiki.debian.org/BridgeNetworkConnections#A.2BAC8-etc.2BAC8-network.2BAC8-interfaces_and_bridging Create one bridge for each physical interface you need, with each bridge (obviously) have one physical interface on "bridge_ports" line> and it gives me a bridge; > > root@xen-07:/var/log/xen# brctl show > bridge name bridge id STP enabled interfaces > eth0 8000.0026b9fedf98 no peth0 > xenbr1 8000.0026b9fedf9a no peth1 > tap7.0 > vif7.0 > > But my domU''s can not see that interface. > > Finally on the xen wiki I found this but I am unsure what it means; > vif = [ ''mac=00:16:5e:72:04:01,bridge=xenbr0,script=your_custom_script1'', > ''mac=00:16:5e:72:04:02,bridge=xenbr1,script=your_custom_script2'' ] > > Mostly because I never get a xenbr0Duh. Your brctl shows the bridge name is eth0, not xenbr0 :P Some explanations on vif line: vif = [ ''mac=00:16:5e:72:04:01,bridge=xenbr0,script=your_custom_script1'', ''mac=00:16:5e:72:04:02,bridge=xenbr1,script=your_custom_script2'' ] (1) note the two lines quoted by single quote? That means you''re creating two NICs for domU. (2) "mac" is what you want that particular domU NIC''s mac to be (3) "bridge" is the name of the bridge on dom0 that the NIC will be attached to (4) "script" is the script name that will be used to setup the NIC on dom0. Usually you can just remove this section, as the default vif-bridge script should work just fine. Also try "xm create --help_config", and look for "vif=". That would show all available options for vif line. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com lists.xensource.com/xen-users