On Fri, 2006-06-30 at 16:58 +0100, Keir Fraser wrote:
> On 30 Jun 2006, at 16:44, Ewan Mellor wrote:
>
> >> The problem is that the timeout occurs before the xennet module can
> >> ever be loaded, which is to be expected. Anything that can be done to
> >> avoid the timeout in this case?
> >
> > The timeout is there to ensure that the boot does not proceed until
> > all the
> > devices needed during boot are available. In this case, since it's a
> > vif, if
> > you were using an NFS root then your boot would presumably fail.
> >
> > If you need to improve this, you will have to have some way to tell
> > the tools
> > "these devices I need for boot, these I don't", and then have the
> > tools put a
> > flag in the store so that Xenbus knows that it doesn't need to wait
> > for them.
>
> The obvious thing to do here is work out which devices haven't been
> picked up by any driver, and not wait on those since they are obviously
> not going to connect! We should either silently ignore those, or maybe
> print a list of them for information.
Good point, how about this patch then?
Cheers,
Mark.
linux-2.6.16-xenbus-timeout-message.patch
Description: Text Data
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home