Hi
I''m working on the implementation on XEN in my company, I''ve
got a strange issue.
I''ve installed a CentOS 5.2 x86_64 Xen server on a Dell PowerEdge 1955
Server.
We use automated installation trough home made scripts (more than 150 servers
and keep growing fast), we use this architecture :
dom0
domU
Eth0--------------
|
|------xenbr0-------------------eth0------
| |
| |
| |
| |-----bond0----bond0.11
|-----bond0---bond0.11
|-----eth1-------| |--------bond0.120
| |------bond0.120
Eth1--------------
We try to do the same on domU on PE 1955 but only the native VLAN (bond0) can go
trough.
We use 2.6.18-92.1.13.el5xen kernel with Broadcom Corporation NetXtreme II
BCM5708S Gigabit Ethernet (rev 12) nic cards.
I''ve saw on the internet that this may be an issue with the driver
included with the kernel, I''ve rebuilt the driver picked from Broadcom
site and it still the same issue.
If anyone can help me with that thx
Thomas
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Hi
Nobody to help me please ?
I''m totally stuck and I don''t find any help on my problem.
De : xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] De la part de Thomas Menard
Envoyé : mercredi 7 janvier 2009 15:42
À : xen-users@lists.xensource.com
Objet : [Xen-users] Xen 3 Bonding VLAN issue
Hi
I''m working on the implementation on XEN in my company, I''ve
got a strange issue.
I''ve installed a CentOS 5.2 x86_64 Xen server on a Dell PowerEdge 1955
Server.
We use automated installation trough home made scripts (more than 150 servers
and keep growing fast), we use this architecture :
dom0
domU
Eth0--------------
|
|------xenbr0-------------------eth0------
| |
| |
| |
| |-----bond0----bond0.11
|-----bond0---bond0.11
|-----eth1-------| |--------bond0.120
| |------bond0.120
Eth1--------------
We try to do the same on domU on PE 1955 but only the native VLAN (bond0) can go
trough.
We use 2.6.18-92.1.13.el5xen kernel with Broadcom Corporation NetXtreme II
BCM5708S Gigabit Ethernet (rev 12) nic cards.
I''ve saw on the internet that this may be an issue with the driver
included with the kernel, I''ve rebuilt the driver picked from Broadcom
site and it still the same issue.
If anyone can help me with that thx
Thomas
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On Thu, Jan 8, 2009 at 4:05 AM, Thomas Menard <TMenard@emailvision.com>wrote:> Hi > > Nobody to help me please ? > > > > I'm totally stuck and I don't find any help on my problem. > > > > *De :* xen-users-bounces@lists.xensource.com [mailto: > xen-users-bounces@lists.xensource.com] *De la part de* Thomas Menard > *Envoyé :* mercredi 7 janvier 2009 15:42 > *À :* xen-users@lists.xensource.com > *Objet :* [Xen-users] Xen 3 Bonding VLAN issue > > > > Hi > > I'm working on the implementation on XEN in my company, I've got a strange > issue. > > > > I've installed a CentOS 5.2 x86_64 Xen server on a Dell PowerEdge 1955 > Server. > > > > We use automated installation trough home made scripts (more than 150 > servers and keep growing fast), we use this architecture : > > > > > > dom0 > > domU > > Eth0-------------- > > | > |------xenbr0-------------------eth0------ > > | > | | > | > > | > | | > |-----bond0----bond0.11 > > |-----bond0---bond0.11 > |-----eth1-------| |--------bond0.120 > > | |------bond0.120 > > Eth1-------------- > > > > We try to do the same on domU on PE 1955 but only the native VLAN (bond0) > can go trough. > > > > We use 2.6.18-92.1.13.el5xen kernel with Broadcom Corporation NetXtreme II > BCM5708S Gigabit Ethernet (rev 12) nic cards. > > > > I've saw on the internet that this may be an issue with the driver included > with the kernel, I've rebuilt the driver picked from Broadcom site and it > still the same issue. > > > > If anyone can help me with that thx > > > > Thomas >I wasn't really following your diagram. Could you put it in an image or explain it again? I do bonding and Xen but I place the bonded device in a bridge and then have the VMs also in the same bridge. Or have an internal bridge and have on VM straddle the internal bridge and the bonded network device. Grant McWilliams Some people, when confronted with a problem, think "I know, I'll use Windows." Now they have two problems. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
You figure is not that clear to me. From what I see is that you are
trying to bond (call it bond0) eth0 and eth1 at dom0. And then you create a
xenbr with bond0. On domU you wish to create another bond using eth0 and eth1.
From what I see from your figure you are providing domU with eth0 and eth1 from
same XenBr????
I am not the best of the judges as your case can be different, but this
arrangement is kinda dodgey. You will not see any gain in bandwidth or fault
tolerance in domU. If fault tolerance is what you are after, providing domU
with only one NIC (eth0) is sufficient with your arrangement. If thats the
bandwidth you are after then good luck, because I am yet to see anyone actually
benefitting from link aggregation for domU using similar mechanism. (that
includes me as well).
Best Regards,
Muhammad Atif
________________________________
From: Thomas Menard <TMenard@Emailvision.com>
To: xen-users@lists.xensource.com
Sent: Thursday, January 8, 2009 11:05:52 PM
Subject: [Xen-users] RE: Xen 3 Bonding VLAN issue
Hi
Nobody to help me
please ?
I’m totally stuck and
I don’t find any help on my problem.
De :xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] De la part de Thomas Menard
Envoyé : mercredi 7 janvier 2009 15:42
À : xen-users@lists.xensource.com
Objet : [Xen-users] Xen 3 Bonding VLAN issue
Hi
I’m working on the implementation on XEN in
my company, I’ve got a strange issue.
I’ve installed a CentOS 5.2 x86_64 Xen
server on a Dell PowerEdge 1955 Server.
We use automated installation trough home
made scripts (more than 150 servers and keep growing fast), we use this
architecture :
dom0
domU
Eth0--------------
|
|------xenbr0-------------------eth0------
|
|
|
|
|
|
|
|-----bond0----bond0.11
|-----bond0---bond0.11
|-----eth1-------|
|--------bond0.120
|
|------bond0.120
Eth1--------------
We try to do the same on domU on PE 1955
but only the native VLAN (bond0) can go trough.
We use 2.6.18-92.1.13.el5xen kernel
with Broadcom Corporation NetXtreme II BCM5708S Gigabit Ethernet (rev 12)
nic cards.
I’ve saw on the internet that this may be
an issue with the driver included with the kernel, I’ve rebuilt the driver
picked from Broadcom site and it still the same issue.
If anyone can help me with that thx
Thomas
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On Wed, Jan 7, 2009 at 9:42 AM, Thomas Menard <TMenard@emailvision.com> wrote:> Hi > > I''m working on the implementation on XEN in my company, I''ve got a strange > issue. > > > > I''ve installed a CentOS 5.2 x86_64 Xen server on a Dell PowerEdge 1955 > Server. > > > > We use automated installation trough home made scripts (more than 150 > servers and keep growing fast), we use this architecture : >This doesn''t address your question, but once you get the bonding issues worked out, you may want to consider a really nice deployment tool called cobbler: https://fedorahosted.org/cobbler/ Best of luck. 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