thr3ads.net - Xen users - [Xen-users] help with bridging [Nov 2010]

If this information is useful, please help other people find it:
Share via:

Tino

2010-Nov-12 13:21 UTC

[Xen-users] help with bridging

Hello,

There is a xen setup in which "brctl show" gives the following output.

bridge name     bridge id               STP enabled     interfaces
eth1            8000.003048c9d4df       no               peth1
                                                        vif1.0
                                                        vif2.0
                                                        vif3.0

No other bridge is present
there.
That means the bridge is eth1, but network configuration for one of the vms
looks like the following in the configuration file


Networking
#
vif         = [
        ''ip=192.168.1.158,mac=00:16:3E:19:26:71,bridge=xenbr1''
]

But there is no network interface like xenbr1 when you type ifconfig .
This setup is working fine. I am not sure how this works. I am new to xen,
so if anybody help me to understand this setup.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Todd Deshane

2010-Nov-12 16:48 UTC

head link

Re: [Xen-users] help with bridging

On Fri, Nov 12, 2010 at 8:21 AM, Tino <tino@sparksupport.com>
wrote:> Hello,
>
> There is a xen setup in which "brctl show" gives the following
output.
>
> bridge name     bridge id               STP enabled     interfaces
> eth1            8000.003048c9d4df       no               peth1
>                                                         vif1.0
>                                                         vif2.0
>                                                         vif3.0
>
> No other bridge is present
> there.
> That means the bridge is eth1, but network configuration for one of the vms
> looks like the following in the configuration file
>
>
> Networking
> #
> vif         = [
>         'ip=192.168.1.158,mac=00:16:3E:19:26:71,bridge=xenbr1'
> ]
>
> But there is no network interface like xenbr1 when you type ifconfig .
> This setup is working fine. I am not sure how this works. I am new to xen,
> so if anybody help me to understand this setup.
Are you sure this is working fine?

Could you also provide the output of xm list to match up the vifs with
the ids of the guests?

Thanks,
Todd

-- 
Todd Deshane
http://todddeshane.net
http://runningxen.com

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Mark Pryor

2010-Nov-12 16:51 UTC

head link

Re: [Xen-users] help with bridging

That vif config can work if there is a another network script like network-route
in /etc/xen/xend-config.sxp

try
grep ''^('' /etc/xen/xend-config.sxp

and see if there is a custom network script or network-nat is uncommented.
If there is a network-foo uncommented, then copy it from /etc/xen/scripts so we
can see it.

I guess that you have some custom setup which mixes bridge and route/nat.

-- 
Mark
--- On Fri, 11/12/10, Tino <tino@sparksupport.com> wrote:

From: Tino <tino@sparksupport.com>
Subject: [Xen-users] help with bridging
To: xen-users@lists.xensource.com
Date: Friday, November 12, 2010, 5:21 AM

Hello,

There is a xen setup in which "brctl show" gives the following output.

bridge name     bridge id               STP enabled     interfaces
eth1            8000.003048c9d4df       no               peth1

                                                        vif1.0
                                                        vif2.0
                                                        vif3.0

 No other bridge is present
there.                                                     

That means the bridge is eth1, but network configuration for one of the vms 
looks like the following in the configuration file


Networking
#
vif         = [
        ''ip=192.168.1.158,mac=00:16:3E:19:26:71,bridge=xenbr1''

]

But there is no network interface like xenbr1 when you type ifconfig .
This setup is working fine. I am not sure how this works. I am new to xen, so if
anybody help me to understand this setup.




      

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Tino

2010-Nov-12 18:49 UTC

head link

Re: [Xen-users] help with bridging

ifconfig result

-------------------
eth0      Link encap:Ethernet  HWaddr 00:30:48:c9:d4:de
          inet addr:"PUBLIC IP"  Bcast:"PUBLIC" 
Mask:255.255.255.224
          inet6 addr: fe80::230:48ff:fec9:d4de/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:883890 errors:0 dropped:0 overruns:0 frame:0
          TX packets:102459 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:203379365 (193.9 MB)  TX bytes:18424671 (17.5 MB)
          Base address:0x2000 Memory:da020000-da040000

eth1      Link encap:Ethernet  HWaddr 00:30:48:c9:d4:df
          inet addr:192.168.1.150  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::230:48ff:fec9:d4df/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1018398 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:188294216 (179.5 MB)  TX bytes:7606 (7.4 KB)

eth3      Link encap:Ethernet  HWaddr 00:15:17:b8:f7:13
          inet addr:192.168.63.167  Bcast:192.168.63.255
Mask:255.255.255.255
          inet6 addr: fe80::215:17ff:feb8:f713/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:9000  Metric:1
          RX packets:118334 errors:0 dropped:0 overruns:0 frame:0
          TX packets:75077 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:448954816 (428.1 MB)  TX bytes:6505002 (6.2 MB)
          Base address:0x3020 Memory:da260000-da280000

eth4      Link encap:Ethernet  HWaddr 00:15:17:b8:f7:12
          inet addr:192.168.64.167  Bcast:192.168.64.255
Mask:255.255.255.255
          inet6 addr: fe80::215:17ff:feb8:f712/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:9000  Metric:1
          RX packets:118331 errors:0 dropped:0 overruns:0 frame:0
          TX packets:75073 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:449012872 (428.2 MB)  TX bytes:6494668 (6.1 MB)
          Base address:0x3000 Memory:da220000-da240000

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:50310 errors:0 dropped:0 overruns:0 frame:0
          TX packets:50310 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:4778318 (4.5 MB)  TX bytes:4778318 (4.5 MB)

peth1     Link encap:Ethernet  HWaddr 00:30:48:c9:d4:df
          inet6 addr: fe80::230:48ff:fec9:d4df/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:16387535 errors:0 dropped:0 overruns:0 frame:0
          TX packets:20271302 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:6438222923 (5.9 GB)  TX bytes:13798016030 (12.8 GB)
          Base address:0x2020 Memory:da060000-da080000

vif1.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:1406955 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2093366 errors:0 dropped:34 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:1231935340 (1.1 GB)  TX bytes:548072636 (522.6 MB)

vif10.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:255561 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1324464 errors:0 dropped:329 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:129778631 (123.7 MB)  TX bytes:359612025 (342.9 MB)

vif11.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:113373 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1131379 errors:0 dropped:347 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:11825801 (11.2 MB)  TX bytes:232674428 (221.8 MB)

vif12.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:619083 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1506337 errors:0 dropped:1516 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:342405605 (326.5 MB)  TX bytes:453940144 (432.9 MB)

vif13.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:13213451 errors:0 dropped:0 overruns:0 frame:0
          TX packets:11304978 errors:0 dropped:1496 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:8610234170 (8.0 GB)  TX bytes:4640469622 (4.3 GB)

vif14.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:145895 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1151270 errors:0 dropped:824 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:46700758 (44.5 MB)  TX bytes:236953638 (225.9 MB)

vif15.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:360088 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1280599 errors:0 dropped:1443 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:286356239 (273.0 MB)  TX bytes:254933091 (243.1 MB)

vif16.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:331459 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1266609 errors:0 dropped:1097 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:210553564 (200.7 MB)  TX bytes:282418222 (269.3 MB)

vif17.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:252131 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1213399 errors:0 dropped:344 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:184884766 (176.3 MB)  TX bytes:246718005 (235.2 MB)

vif18.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:125730 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1031620 errors:0 dropped:1043 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:65909777 (62.8 MB)  TX bytes:221155798 (210.9 MB)

vif19.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:290074 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1249814 errors:0 dropped:7891 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:206884342 (197.3 MB)  TX bytes:259322573 (247.3 MB)

vif2.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:31332 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1063980 errors:0 dropped:81 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:3856883 (3.6 MB)  TX bytes:213583053 (203.6 MB)

vif3.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:36 errors:0 dropped:1032197 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:0 (0.0 B)  TX bytes:4425 (4.3 KB)

vif3.1    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:582670 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1613873 errors:0 dropped:100 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:878266531 (837.5 MB)  TX bytes:343299896 (327.3 MB)

vif4.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:401353 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1044405 errors:0 dropped:137 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:73380264 (69.9 MB)  TX bytes:191409778 (182.5 MB)

vif5.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:141959 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1152192 errors:0 dropped:93 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:42085784 (40.1 MB)  TX bytes:237239330 (226.2 MB)

vif6.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:130789 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1143872 errors:0 dropped:175 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:29370624 (28.0 MB)  TX bytes:235522897 (224.6 MB)

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:483180 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1374548 errors:0 dropped:388 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:428569758 (408.7 MB)  TX bytes:302587524 (288.5 MB)

vif8.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:117501 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1138378 errors:0 dropped:481 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:20073690 (19.1 MB)  TX bytes:238341523 (227.3 MB)

vif9.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:860504 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1814179 errors:0 dropped:178 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:606318444 (578.2 MB)  TX bytes:635945581 (606.4 MB)

------------------------------------------------------------------------------------------------------------------------------------------------

There is no custom scripts or network-nat uncommented in xend-config.sxp. I
have double checked that.
Only thing uncommented in network part is
-------------------

(network-script ''network-bridge netdev=eth1'')
(vif-script vif-bridge)

---------------------
xm list
[no real name given]



Name                                        ID   Mem VCPUs      State
Time(s)
Domain-0                                   0  9278     8     r-----  13697.8
vm1                                           1  1024     1     -b----
3425.7
vm2                                           3  2048     1     -b----
4214.5
 vm3                                          2  1024     1     -b----
2180.2
vm4                                           4   512     1     -b----
2269.7
vm5                                           5  1024     1     -b----
2401.4
vm6                                            6  1024     1     -b----
2251.3
vm7                                           7  1024     1     -b----
2431.8
vm8                                           8  2048     1     -b----
2284.6
vm9                                           9  1024     1     -b----
2933.
vm10                                        10  1024     1     -b----
2495.0
vm11                                        11  1024     1     -b----
2404.3
vm12                                        12  1024     1     -b----
2828.0
vm13                                       13  2048     1     -b----
8366.1
vm14                                       14  1024     1     -b----
2294.7
vm15                                        15  1024     1     -b----
2342.0
vm16                                        16  2048     1     -b----
2726.6
vm17                                         17  1024     1     -b----
2251.1
vm18                                         18  1024     1     -b----
2192.7
vm19                                          19  1024     1     -b----
2335.7

--------------------------------------------------------------------------------------------










On Fri, Nov 12, 2010 at 10:21 PM, Mark Pryor <tlviewer@yahoo.com> wrote:
> That vif config can work if there is a another network script like
> network-route in /etc/xen/xend-config.sxp
>
> try
> grep ''^('' /etc/xen/xend-config.sxp
>
> and see if there is a custom network script or network-nat is uncommented.
> If there is a network-foo uncommented, then copy it from /etc/xen/scripts
> so we can see it.
>
> I guess that you have some custom setup which mixes bridge and route/nat.
>
> --
> Mark
> --- On Fri, 11/12/10, Tino <tino@sparksupport.com> wrote:
>
> From: Tino <tino@sparksupport.com>
> Subject: [Xen-users] help with bridging
> To: xen-users@lists.xensource.com
> Date: Friday, November 12, 2010, 5:21 AM
>
> Hello,
>
> There is a xen setup in which "brctl show" gives the following
output.
>
> bridge name     bridge id               STP enabled     interfaces
> eth1            8000.003048c9d4df       no               peth1
>
>                                                         vif1.0
>                                                         vif2.0
>                                                         vif3.0
>
>  No other bridge is present
> there.
>
> That means the bridge is eth1, but network configuration for one of the
> vms  looks like the following in the configuration file
>
>
> Networking
> #
> vif         = [
>        
''ip=192.168.1.158,mac=00:16:3E:19:26:71,bridge=xenbr1''
>
> ]
>
> But there is no network interface like xenbr1 when you type ifconfig .
> This setup is working fine. I am not sure how this works. I am new to xen,
> so if anybody help me to understand this setup.
>
>
>
>
>
>

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Todd Deshane

2010-Nov-13 01:01 UTC

head link

Re: [Xen-users] help with bridging

On Fri, Nov 12, 2010 at 1:49 PM, Tino <tino@sparksupport.com>
wrote:>
> ifconfig result
> Name                                        ID   Mem VCPUs      State
> Time(s)
> Domain-0                                   0  9278     8     r----- 
13697.8
> vm1                                           1  1024     1     -b----
> 3425.7
> vm2                                           3  2048     1     -b----
> 4214.5
>  vm3                                          2  1024     1     -b----
> 2180.2
> vm4                                           4   512     1     -b----
> 2269.7
> vm5                                           5  1024     1     -b----
> 2401.4
> vm6                                            6  1024     1     -b----
> 2251.3
> vm7                                           7  1024     1     -b----
> 2431.8
> vm8                                           8  2048     1     -b----
> 2284.6
> vm9                                           9  1024     1     -b----
> 2933.
> vm10                                        10  1024     1     -b----
> 2495.0
> vm11                                        11  1024     1     -b----
> 2404.3
> vm12                                        12  1024     1     -b----
> 2828.0
> vm13                                       13  2048     1     -b----
> 8366.1
> vm14                                       14  1024     1     -b----
> 2294.7
> vm15                                        15  1024     1     -b----
> 2342.0
> vm16                                        16  2048     1     -b----
> 2726.6
> vm17                                         17  1024     1     -b----
> 2251.1
> vm18                                         18  1024     1     -b----
> 2192.7
> vm19                                          19  1024     1     -b----
> 2335.7
Which VMs network work and which don't?

From your brctl in the original post, it seems that you only have VMs
1, 3, and 2 connected to the eth0 bridge.

Did I mis-read your original email on what is working/not working?

Thanks,
Todd


-- 
Todd Deshane
http://todddeshane.net
http://runningxen.com

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Tino

2010-Nov-13 04:42 UTC

head link

Re: [Xen-users] help with bridging

sorry,i did not put the complete result of brctl show in my first post. All
vms are working fine here. I am reaching the conclusion that Xen ignores
your bridge=xenbr0 value and only uses what it finds in brctl show as Mark
Pryor said. Is there anything to add regarding this setup ?

On Sat, Nov 13, 2010 at 6:31 AM, Todd Deshane <deshantm@gmail.com> wrote:
> On Fri, Nov 12, 2010 at 1:49 PM, Tino <tino@sparksupport.com> wrote:
> >
> > ifconfig result
> > Name                                        ID   Mem VCPUs      State
> > Time(s)
> > Domain-0                                   0  9278     8     r-----
> 13697.8
> > vm1                                           1  1024     1     -b----
> > 3425.7
> > vm2                                           3  2048     1     -b----
> > 4214.5
> >  vm3                                          2  1024     1     -b----
> > 2180.2
> > vm4                                           4   512     1     -b----
> > 2269.7
> > vm5                                           5  1024     1     -b----
> > 2401.4
> > vm6                                            6  1024     1    
-b----
> > 2251.3
> > vm7                                           7  1024     1     -b----
> > 2431.8
> > vm8                                           8  2048     1     -b----
> > 2284.6
> > vm9                                           9  1024     1     -b----
> > 2933.
> > vm10                                        10  1024     1     -b----
> > 2495.0
> > vm11                                        11  1024     1     -b----
> > 2404.3
> > vm12                                        12  1024     1     -b----
> > 2828.0
> > vm13                                       13  2048     1     -b----
> > 8366.1
> > vm14                                       14  1024     1     -b----
> > 2294.7
> > vm15                                        15  1024     1     -b----
> > 2342.0
> > vm16                                        16  2048     1     -b----
> > 2726.6
> > vm17                                         17  1024     1     -b----
> > 2251.1
> > vm18                                         18  1024     1     -b----
> > 2192.7
> > vm19                                          19  1024     1    
-b----
> > 2335.7
>
> Which VMs network work and which don''t?
>
> From your brctl in the original post, it seems that you only have VMs
> 1, 3, and 2 connected to the eth0 bridge.
>
> Did I mis-read your original email on what is working/not working?
>
> Thanks,
> Todd
>
>
> --
> Todd Deshane
> http://todddeshane.net
> http://runningxen.com
>

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Todd Deshane

2010-Nov-13 21:04 UTC

head link

Re: [Xen-users] help with bridging

On Fri, Nov 12, 2010 at 11:42 PM, Tino <tino@sparksupport.com>
wrote:> sorry,i did not put the complete result of brctl show in my first post. All
> vms are working fine here. I am reaching the conclusion that Xen ignores
> your bridge=xenbr0 value and only uses what it finds in brctl show as Mark
> Pryor said. Is there anything to add regarding this setup ?
Does it still work properly if you use bridge=''eth0'' ?

I''m not sure why it is failing over to "do the right thing",
but I
wouldn''t be too comfortable with keeping configs that may or may not
work based on Xen version, bridge configuration, something in the
environment, or interesting defaults, etc.

Thanks,
Todd


-- 
Todd Deshane
http://todddeshane.net
http://runningxen.com

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Reasonably Related Threads

Search for more maybe matching threads

Xen users - Nov 2010 - help with bridging

[Xen-users] help with bridging

Re: [Xen-users] help with bridging

Re: [Xen-users] help with bridging

Re: [Xen-users] help with bridging

Re: [Xen-users] help with bridging

Re: [Xen-users] help with bridging

Re: [Xen-users] help with bridging

Reasonably Related Threads