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/
Home Products Support Community News


Re: [Xen-devel] Re: Timeout connecting to device

On Wed, 2005-08-24 at 09:25 +0100, Christian Limpach wrote:
> On 8/24/05, Rusty Russell <rusty@xxxxxxxxxxxxxxx> wrote:
> > The trace file is actually better in my experience.  Also look for
> > "error" nodes in the store (although Christian removed some of those
> > paths in the merge).
> I only removed the ones which were not fatal because I was under the
> impression initally that adding an error node does indicate a final
> error after which it would be up to a control tool to sort out the
> failure or report it.

Well, I expect there to be an error node at some point in the normal
case: you look in the backend and something isn't there yet, you want to
indicate that, because it may never change (in the normal case, it will
appear soon and we will delete the error node).

The error node idea might be overly simplistic: its non-existence
doesn't tell you the device is ok (it might have just been created).
Makes it harder to synchronously create a device.

Will think more on this...
A bad analogy is like a leaky screwdriver -- Richard Braakman

Xen-devel mailing list