WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] Improve xenbus timeout error message

To: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Improve xenbus timeout error message
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Fri, 30 Jun 2006 16:58:06 +0100
Cc: Mark McLoughlin <markmc@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 30 Jun 2006 08:59:05 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20060630154433.GG8835@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1151681386.6184.60.camel@xxxxxxxxxxxxxxxxxxxxx> <20060630154433.GG8835@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

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.

 -- Keir


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel