Hi. I''m trying to run Xen 3.0 unstable, compiled from source on a CentOS 4.2 machine. I notice that the networking breaks as soon as xend starts on the machine. Only on restarting xend does networking come back again. The boot order is 1. networking starts - I can ping the machine 2. xend starts by startup scripts - ping stops Only lo and xenbr0 interfaces are present. As soon as I restart the xend service on the machine. eth0 becomes available, networking comes back and I can ping dom0 again. How do I solve this issue? I have keyboard/video access to the machine only now. The machine is a compute node on a cluster, and I cant go and restart xend on the machine everytime networking breaks. Please help. Thanks, Anoop _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Anoop Rajendra wrote:> > 1. networking starts - I can ping the machine > 2. xend starts by startup scripts - ping stops >You want to let xend handle starting your networking, rather than starting it manually yourself. If you let Xend do it then it *should* get it right... Alex -- Alex Brett alex.brett@loho.co.uk http://www.loho.co.uk/ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
And that exactly the problem. xend starts from a startup script and shuts down eth0. I have to physically login to the machine and restart xend using /etc/ init.d/xend restart, and only then eth0 comes up again along with all the other virtual interfaces. -Anoop On May 5, 2006, at 6:28 PM, Alex Brett wrote:> Anoop Rajendra wrote: >> 1. networking starts - I can ping the machine >> 2. xend starts by startup scripts - ping stops > > You want to let xend handle starting your networking, rather than > starting it manually yourself. If you let Xend do it then it > *should* get it right... > > Alex > > -- > Alex Brett > alex.brett@loho.co.uk > http://www.loho.co.uk/ >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Anoop Rajendra wrote:> And that exactly the problem. > > xend starts from a startup script and shuts down eth0. > > I have to physically login to the machine and restart xend using > /etc/init.d/xend restart, and only then eth0 comes up again along with > all the other virtual interfaces. >Networking is breaking because eth0 is *already* up when xend starts. You need to tell your distro not to start eth0 automatically (in centos I believe you need to edit the /etc/sysconfig/network-scripts/ifcfg-eth0 file), and simply let xend do it. It should then start it up in the correct state. Alex -- Alex Brett alex.brett@loho.co.uk http://www.loho.co.uk/ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks. I did solve it by changing the boot priority of the xend startup script from 98 to 09. This way it would start before eth0 would come up. Wow! I didn''t know xend had to be up before network interfaces were brought up. Could you or someone tell me why? Or point to a place which explains this? Thanks -Anoop On May 5, 2006, at 6:38 PM, Alex Brett wrote:> Anoop Rajendra wrote: >> And that exactly the problem. >> xend starts from a startup script and shuts down eth0. >> I have to physically login to the machine and restart xend using / >> etc/init.d/xend restart, and only then eth0 comes up again along >> with all the other virtual interfaces. > > Networking is breaking because eth0 is *already* up when xend > starts. You need to tell your distro not to start eth0 > automatically (in centos I believe you need to edit the /etc/ > sysconfig/network-scripts/ifcfg-eth0 file), and simply let xend do > it. It should then start it up in the correct state. > > Alex >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 06/05/06, Anoop Rajendra <anoop.rajendra@gmail.com> wrote:> Wow! I didn''t know xend had to be up before network interfaces were > brought up. Could you or someone tell me why? Or point to a place > which explains this?Read the networking faq, if you haven''t already: http://wiki.xensource.com/xenwiki/XenNetworking _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users