Description of problem: When I boot my machine with Xen it takes xend about roughly 95 seconds to start. Version-Release number of selected component (if applicable): xen-3.0.3-0.1.rc3 How reproducible: Always Steps to Reproduce: 1. install all xen stuff in fc6 2. boot 3. Actual results: xend takes 1.5 minutes to start. Expected results: Faster boot time, and/or better progress information Additional info: So, I don't know if this is actually a bug, or expected behaviour. All I can say is that it takes a looong time to load.
xend starts in a few seconds for me. What's your networking configuration? I suspect it's getting stuck somewhere in setting up the network; does xen networking look OK after it does finally start?
There is one DHCP server (FreeBSD with ISC dhcpd), devices get DHCP leases from that. Sometimes I use wireless, sometimes I use wired networking. Networking seems to be just fine afterwards. Could it be the network devices that timeout?
Yes, could be; alt-sysrq-t ought to be able to show if it's hanging in dhcpcd or somewhere similar.
When I connect the network cable and everything all works fine. Only when I have it disconnected it takes that long. So, it is not an error and therefore this bug can be closed. I'm wondering if the start scripts for xend could benefit from the fact that the networking script has already determined a few seconds earlier that there is nothing on my wired interface. Or is that impossible to do?
Not impossible; but _lots_ of networking bits and pieces are likely to function badly without any networking enabled. Handling it more gracefully is probably not actually a Xen problem, more that ifup itself might handle it more rapidly.