Re: [CentOS] Xen and bonding on Centos 5.2
If you are using kernel 92.1.6 it's because apparently there is a bug. I haven't tried 92.1.10 to check if it has been solved. On 5.2 stock kernel on the other hand I have no problems. Francesco Policlinico San Marco Italy - Original Message - From: Dirk H. Schulz [EMAIL PROTECTED] To: CentOS mailing list centos@centos.org Sent: Friday, 8 August, 2008 5:33:09 PM GMT +01:00 Amsterdam / Berlin / Bern / Rome / Stockholm / Vienna Subject: [CentOS] Xen and bonding on Centos 5.2 Hi folks, I am stuck with a weird phenomenon. I have set up two servers as xen servers with bonded interfaces (mode 1). The bond interface works fine on both servers as long as xen is not used. When using xen's network-bridge script (with netdev=bond0), one server works fine without problems, and the other starts upping and downing the slave interfaces of the bond in a very fast manner (several runs per second). Both configurations are identical, the only difference is: - the working server has tg3 nic drivers - the dysfunctional server has e100 nic drivers. Does it really depend on the nic driver if bonding works? And why does it not work in xen, but work fine without xen? What can I do to analyse the problem? I know I could ask this on the xen list, but I fear that this is a redhat/centos specific phenomenon. Any hint or help is appreciated. Dirk ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Xen and bonding on Centos 5.2
Francesco, --On 10. August 2008 20:18:28 +0200 Francesco Camisa [EMAIL PROTECTED] wrote: If you are using kernel 92.1.6 it's because apparently there is a bug. I haven't tried 92.1.10 to check if it has been solved. On 5.2 stock kernel on the other hand I have no problems. The server that has no problem with bonding at all has been using 92.1.6 for weeks now - the server having the problem is still running 53 - I try updating it to 92.1.10 now. Dirk Francesco Policlinico San Marco Italy - Original Message - From: Dirk H. Schulz [EMAIL PROTECTED] To: CentOS mailing list centos@centos.org Sent: Friday, 8 August, 2008 5:33:09 PM GMT +01:00 Amsterdam / Berlin / Bern / Rome / Stockholm / Vienna Subject: [CentOS] Xen and bonding on Centos 5.2 Hi folks, I am stuck with a weird phenomenon. I have set up two servers as xen servers with bonded interfaces (mode 1). The bond interface works fine on both servers as long as xen is not used. When using xen's network-bridge script (with netdev=bond0), one server works fine without problems, and the other starts upping and downing the slave interfaces of the bond in a very fast manner (several runs per second). Both configurations are identical, the only difference is: - the working server has tg3 nic drivers - the dysfunctional server has e100 nic drivers. Does it really depend on the nic driver if bonding works? And why does it not work in xen, but work fine without xen? What can I do to analyse the problem? I know I could ask this on the xen list, but I fear that this is a redhat/centos specific phenomenon. Any hint or help is appreciated. Dirk ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos -- Dirk H. Schulz IT Systems Service Wiesenweg 12, 85567 Grafing Tel. 0 80 92/86 25 68 Fax. 0 80 92/86 25 72 -- Technik vom Feinsten - und das nötige Tuning ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Xen and bonding on Centos 5.2
Hi folks, I am stuck with a weird phenomenon. I have set up two servers as xen servers with bonded interfaces (mode 1). The bond interface works fine on both servers as long as xen is not used. When using xen's network-bridge script (with netdev=bond0), one server works fine without problems, and the other starts upping and downing the slave interfaces of the bond in a very fast manner (several runs per second). Both configurations are identical, the only difference is: - the working server has tg3 nic drivers - the dysfunctional server has e100 nic drivers. Does it really depend on the nic driver if bonding works? And why does it not work in xen, but work fine without xen? What can I do to analyse the problem? I know I could ask this on the xen list, but I fear that this is a redhat/centos specific phenomenon. Any hint or help is appreciated. Dirk ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
