Hi, Xend takes around 2 minutes to load, I''ve compiled the unstable version and tested it on two different computers... any idea why it takes so much time? Thanks, David. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> Xend takes around 2 minutes to load, I''ve compiled the unstable > version and tested it on two different computers... any idea why it > takes so much time?Before starting xend, try running the /etc/xen/scripts/network-bridge script on its own. I suspect this is where all the time goes. I''ve seen this happen with certain network cards, but not for a long time. What version are you using? Ian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Thu, Jan 25, 2007 at 02:00:49PM -0000, Ian Pratt wrote:> > Xend takes around 2 minutes to load, I''ve compiled the unstable > > version and tested it on two different computers... any idea why it > > takes so much time? > > > Before starting xend, try running the /etc/xen/scripts/network-bridge > script on its own. > > I suspect this is where all the time goes. I''ve seen this happen with > certain network cards, but not for a long time. What version are you > using?Is there any work scheduled on the Xen roadmap yet to remove the need to use netloop driver in Dom0 ? It would be very desirable to eliminate the complicated peth0/eth0/vif0 interface renaming/duplication for Dom0 so that the regular OS distro provided networking scripts ''just work'' with Xen. So if people wanted a bridged setup they can simply create their regular /etc/sysconfig/network-scripts/ifcfg-br0 (or equivalant) - so XenD would only need to worry about the vif-* scripts, and we can kill off network-* scripts. Having Xen init scripts mess around with networking is causing all sorts of other pain like breaking bonding, not working with netconsole, breaking NFS root or complicating other network based storage booting like AoE/iSCSI. This is unfortunately giving Xen a bad reputation as being very hard to manage wrt to networking, which would be nice to address. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Thanks for your replay! The network card is Intel 82573L Gigabit, I''m using an IBM T60 notebook, with the intel ICH7 chipset. I will check the network-bridge script alone at the next boot, it might be it becuase a restart is being performed fast. On 1/25/07, Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> wrote:> > Xend takes around 2 minutes to load, I''ve compiled the unstable > > version and tested it on two different computers... any idea why it > > takes so much time? > > > Before starting xend, try running the /etc/xen/scripts/network-bridge > script on its own. > > I suspect this is where all the time goes. I''ve seen this happen with > certain network cards, but not for a long time. What version are you > using? > > Ian >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 25/1/07 14:13, "Daniel P. Berrange" <berrange@redhat.com> wrote:> Is there any work scheduled on the Xen roadmap yet to remove the need to > use netloop driver in Dom0 ? It would be very desirable to eliminate the > complicated peth0/eth0/vif0 interface renaming/duplication for Dom0 so that > the regular OS distro provided networking scripts ''just work'' with Xen. So > if people wanted a bridged setup they can simply create their regular > /etc/sysconfig/network-scripts/ifcfg-br0 (or equivalant) - so XenD would > only need to worry about the vif-* scripts, and we can kill off network-* > scripts.You can set things up today without the loopback. But if domU<->dom0 traffic is allowed then you can end up with all domU tx slots tied up in dom0 socket buffers for unbounded time. If domU<->dom0 traffic is disallowed, or just not done, then the loopback serves no other purpose. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Thu, Jan 25, 2007 at 03:38:25PM +0000, Keir Fraser wrote:> On 25/1/07 14:13, "Daniel P. Berrange" <berrange@redhat.com> wrote: > > > Is there any work scheduled on the Xen roadmap yet to remove the need to > > use netloop driver in Dom0 ? It would be very desirable to eliminate the > > complicated peth0/eth0/vif0 interface renaming/duplication for Dom0 so that > > the regular OS distro provided networking scripts ''just work'' with Xen. So > > if people wanted a bridged setup they can simply create their regular > > /etc/sysconfig/network-scripts/ifcfg-br0 (or equivalant) - so XenD would > > only need to worry about the vif-* scripts, and we can kill off network-* > > scripts. > > You can set things up today without the loopback. But if domU<->dom0 traffic > is allowed then you can end up with all domU tx slots tied up in dom0 socket > buffers for unbounded time. If domU<->dom0 traffic is disallowed, or just > not done, then the loopback serves no other purpose.Yes, I was specifically thinking about the ideas that have been brought up every now & then about fixing the netback side of things to avoid the dom0 socket buffers being pinned indefinitely. So we can safely have the DomU <-> Dom0 traffic without needing netloop. Regar,ds Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> > You can set things up today without the loopback. But if domU<->dom0 > traffic > > is allowed then you can end up with all domU tx slots tied up indom0> socket > > buffers for unbounded time. If domU<->dom0 traffic is disallowed, orjust> > not done, then the loopback serves no other purpose. > > Yes, I was specifically thinking about the ideas that have beenbrought> up every now & then about fixing the netback side of things to avoidthe> dom0 socket buffers being pinned indefinitely. So we can safely havethe> DomU <-> Dom0 traffic without needing netloop.Herbert Xu would be the man to do this in an upstream-friendly way :-) Ian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel