First off, I am rather new to Xen and looked through the archives but could not locate a solution to my problem . In my Dom0 configuration I have 2 nics (eth0 & eth1. Eth0 and Eth1 are boned and appear as bond0. I installed Xen and all network traffic over bond works fine. I installed a Redhat ES 5 as DomU. When I boot the image, it does not pickup any networking from Dom0. I have tried editing xend-config.sxp and changed the line: (network-script network-bridge) To (network-script ''network-bridge netdev=bond0'') Still nothing. I even went as far as removing the bonded interface and running eth0/eth1 as normal and I still am not able to get networking up for DomU. When I added the netdev=bond0 it killed all networking for Dom0 and DomU. What am I doing wrong? There is nothing in the documentation about this... Any help would be great. Thanks Andrew _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Mon, Dec 22, 2008 at 8:20 AM, Andrew Deagman < andrew.deagman@callfinity.com> wrote:> First off, I am rather new to Xen and looked through the archives but > could not locate a solution to my problem . In my Dom0 configuration I have > 2 nics (eth0 & eth1. Eth0 and Eth1 are boned and appear as bond0. I > installed Xen and all network traffic over bond works fine. I installed a > Redhat ES 5 as DomU. When I boot the image, it does not pickup any > networking from Dom0. I have tried editing xend-config.sxp and changed the > line: > > (network-script network-bridge) To (network-script ''network-bridge > netdev=bond0'') > > Still nothing. I even went as far as removing the bonded interface and > running eth0/eth1 as normal and I still am not able to get networking up for > DomU. When I added the netdev=bond0 it killed all networking for Dom0 and > DomU. What am I doing wrong? There is nothing in the documentation about > this... Any help would be great. > > Thanks > Andrew > > Andrew,Xen renames eth0 to peth0 and creates a bridge named eth0. Are you sure that your bond is working after xend starts up? Generally you have to rename the actual physical device eth0 or use custom network-scripts to keep this from happening with a bond. Grant _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Mon, Dec 22, 2008 at 8:59 AM, Andrew Deagman < andrew.deagman@callfinity.com> wrote:> From what I can tell the bond is still working. I can get to the physical > server (Dom0). When I login to DomU from the console I can not ping the > gateway or get in/out. Here is the output of ifconfig –a > > [adeagman@bns1 ~]$ badm01::# ifconfig -a > bond0 Link encap:Ethernet HWaddr 00:21:9B:FB:D4:F1 > inet addr:10.10.8.11 Bcast:10.10.8.255 Mask:255.255.255.0 > inet6 addr: fe80::221:9bff:fefb:d4f1/64 Scope:Link > UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1 > RX packets:5385 errors:0 dropped:0 overruns:0 frame:0 > TX packets:3354 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:640345 (625.3 KiB) TX bytes:461431 (450.6 KiB) > > eth0 Link encap:Ethernet HWaddr 00:21:9B:FB:D4:F1 > 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:16 > > eth1 Link encap:Ethernet HWaddr 00:21:9B:FB:D4:F1 > inet6 addr: fe80::221:9bff:fefb:d4f1/64 Scope:Link > UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 > RX packets:5385 errors:0 dropped:0 overruns:0 frame:0 > TX packets:3354 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:640345 (625.3 KiB) TX bytes:461431 (450.6 KiB) > Interrupt:17 > > 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:73 errors:0 dropped:0 overruns:0 frame:0 > TX packets:73 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:20915 (20.4 KiB) TX bytes:20915 (20.4 KiB) > > peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:18 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:4572 (4.4 KiB) > > sit0 Link encap:IPv6-in-IPv4 > NOARP MTU:1480 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:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > veth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:18 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:4572 (4.4 KiB) TX bytes:0 (0.0 b) > > veth1 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > 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:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) >....> > > xenbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > UP BROADCAST RUNNING NOARP 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:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > badm01::# > > > > On 12/22/08 11:52 AM, "Grant McWilliams" <grantmasterflash@gmail.com> > wrote: > > Xen renames eth0 to peth0 and creates a bridge named eth0. Are you sure > that your bond is working after xend starts up? Generally you have to rename > the actual physical device eth0 or use custom network-scripts to keep this > from happ > > > -- > Andrew Deagman > System Administrator | Callfinity Inc. > E: andrew.deagman@callfinity.com > O: 585-278-1940 x8126 > M: 585-703-8621 > >Can you show the output of brctl show? You must be using xen 3.1 or older by the way the network is looking. Also can you show the contents of /proc/net/bonding/bond0 Grant McWilliams _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I got it working. It was an issue with eth0 being moving out of the way and bonding was not truly working. I added a custom network-bridge script and attached my DomU to a new bridge and every thing is now working. Thanks for the help. Andrew On 12/22/08 1:47 PM, "Grant McWilliams" <grantmasterflash@gmail.com> wrote:> On Mon, Dec 22, 2008 at 8:59 AM, Andrew Deagman > <andrew.deagman@callfinity.com> wrote: >> From what I can tell the bond is still working. I can get to the physical >> server (Dom0). When I login to DomU from the console I can not ping the >> gateway or get in/out. Here is the output of ifconfig a >> >> [adeagman@bns1 ~]$ badm01::# ifconfig -a >> bond0 Link encap:Ethernet HWaddr 00:21:9B:FB:D4:F1 >> inet addr:10.10.8.11 Bcast:10.10.8.255 Mask:255.255.255.0 >> inet6 addr: fe80::221:9bff:fefb:d4f1/64 Scope:Link >> UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1 >> RX packets:5385 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:3354 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:0 >> RX bytes:640345 (625.3 KiB) TX bytes:461431 (450.6 KiB) >> >> eth0 Link encap:Ethernet HWaddr 00:21:9B:FB:D4:F1 >> 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:16 >> >> eth1 Link encap:Ethernet HWaddr 00:21:9B:FB:D4:F1 >> inet6 addr: fe80::221:9bff:fefb:d4f1/64 Scope:Link >> UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 >> RX packets:5385 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:3354 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:640345 (625.3 KiB) TX bytes:461431 (450.6 KiB) >> Interrupt:17 >> >> 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:73 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:73 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:0 >> RX bytes:20915 (20.4 KiB) TX bytes:20915 (20.4 KiB) >> >> peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF >> inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:18 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:0 >> RX bytes:0 (0.0 b) TX bytes:4572 (4.4 KiB) >> >> sit0 Link encap:IPv6-in-IPv4 >> NOARP MTU:1480 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:0 >> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) >> >> veth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 >> BROADCAST MULTICAST MTU:1500 Metric:1 >> RX packets:18 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:0 >> RX bytes:4572 (4.4 KiB) TX bytes:0 (0.0 b) >> >> veth1 Link encap:Ethernet HWaddr 00:00:00:00:00:00 >> 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:0 >> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > .... >> >> >> xenbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 >> UP BROADCAST RUNNING NOARP 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:0 >> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) >> >> badm01::# >> >> >> >> On 12/22/08 11:52 AM, "Grant McWilliams" <grantmasterflash@gmail.com >> <http://grantmasterflash@gmail.com> > wrote: >> >>> Xen renames eth0 to peth0 and creates a bridge named eth0. Are you sure that >>> your bond is working after xend starts up? Generally you have to rename the >>> actual physical device eth0 or use custom network-scripts to keep this from >>> happ-- Andrew Deagman System Administrator | Callfinity Inc. E: andrew.deagman@callfinity.com O: 585-278-1940 x8126 M: 585-703-8621 Quietly implementing RFC 1925 wherever I go.... _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Mon, Dec 22, 2008 at 10:53 AM, Andrew Deagman < andrew.deagman@callfinity.com> wrote:> I got it working. It was an issue with eth0 being moving out of the way > and bonding was not truly working. I added a custom network-bridge script > and attached my DomU to a new bridge and every thing is now working. Thanks > for the help. > > Andrew > > > > > On 12/22/08 1:47 PM, "Grant McWilliams" <grantmasterflash@gmail.com> > wrote: > > On Mon, Dec 22, 2008 at 8:59 AM, Andrew Deagman < > andrew.deagman@callfinity.com> wrote: > > From what I can tell the bond is still working. I can get to the physical > server (Dom0). When I login to DomU from the console I can not ping the > gateway or get in/out. Here is the output of ifconfig –a > > [adeagman@bns1 ~]$ badm01::# ifconfig -a > bond0 Link encap:Ethernet HWaddr 00:21:9B:FB:D4:F1 > inet addr:10.10.8.11 Bcast:10.10.8.255 Mask:255.255.255.0 > inet6 addr: fe80::221:9bff:fefb:d4f1/64 Scope:Link > UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1 > RX packets:5385 errors:0 dropped:0 overruns:0 frame:0 > TX packets:3354 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:640345 (625.3 KiB) TX bytes:461431 (450.6 KiB) > > eth0 Link encap:Ethernet HWaddr 00:21:9B:FB:D4:F1 > 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:16 > > > > On 12/22/08 11:52 AM, "Grant McWilliams" <grantmasterflash@gmail.com < > http://grantmasterflash@gmail.com> > wrote: > > Xen renames eth0 to peth0 and creates a bridge named eth0. Are you sure > that your bond is working after xend starts up? Generally you have to rename > the actual physical device eth0 or use custom network-scripts to keep this > from happ > > > -- > Andrew Deagman > System Administrator | Callfinity Inc. > E: andrew.deagman@callfinity.com > O: 585-278-1940 x8126 > M: 585-703-8621 > > Quietly implementing RFC 1925 wherever I go.... >Thats where I was headed. Glad you got it to work. I use Xen with bonded ethernet devices so I had to do the same thing. Grant McWilliams _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users