From: Kamala Narasimhan <kamala.narasimhan@gmail.com>
To: Christoph Egger <Christoph.Egger@amd.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: libxl: error handling before xenstored runs
Date: Wed, 09 Feb 2011 09:29:55 -0500 [thread overview]
Message-ID: <4D52A4E3.7070907@gmail.com> (raw)
In-Reply-To: <201102091213.06591.Christoph.Egger@amd.com>
Christoph Egger wrote:
> Hi!
>
> When I start a guest *before* xenstored runs
> then I get this list of error messages:
>
> libxl: error: libxl_xshelp.c:109:libxl__xs_get_dompath failed to get dompath
> for 1: Bad file descriptor
> libxl: error: libxl_xshelp.c:109:libxl__xs_get_dompath failed to get dompath
> for 0: Bad file descriptor
> libxl: error: libxl_device.c:116:libxl__device_generic_add xs transaction
> failed: Bad file descriptor
> libxl: error: libxl_xshelp.c:109:libxl__xs_get_dompath failed to get dompath
> for 1: Bad file descriptor
> libxl: error: libxl_xshelp.c:109:libxl__xs_get_dompath failed to get dompath
> for 0: Bad file descriptor
> libxl: error: libxl_device.c:116:libxl__device_generic_add xs transaction
> failed: Bad file descriptor
> libxl: error: libxl_xshelp.c:109:libxl__xs_get_dompath failed to get dompath
> for 1: Bad file descriptor
> libxl: error: libxl_xshelp.c:109:libxl__xs_get_dompath failed to get dompath
> for 0: Bad file descriptor
> libxl: error: libxl_device.c:116:libxl__device_generic_add xs transaction
> failed: Bad file descriptor
> libxl: error: libxl_xshelp.c:109:libxl__xs_get_dompath failed to get dompath
> for 1: Bad file descriptor
> libxl: error: libxl_xshelp.c:109:libxl__xs_get_dompath failed to get dompath
> for 0: Bad file descriptor
> libxl: error: libxl_device.c:116:libxl__device_generic_add xs transaction
> failed: Bad file descriptor
> libxl: error: libxl_xshelp.c:109:libxl__xs_get_dompath failed to get dompath
> for 1: Bad file descriptor
> xl: fatal error: libxl_create.c:487, rc=-3: libxl__create_device_model
> libxl: error: libxl_xshelp.c:109:libxl__xs_get_dompath failed to get dompath
> for 1: Bad file descriptor
> libxl: error: libxl.c:675:libxl_domain_destroy non-existant domain -1
>
>
> IMO a simple message like "xenstored is not running." would be enough.
>
xl now has a check and newer versions of the toolstack should display similar
message when you invoke an xl command. Is it possible you are using a slightly
older version of the toolstack or directly invoking libxl library elsewhere?
Kamala
next prev parent reply other threads:[~2011-02-09 14:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 11:13 libxl: error handling before xenstored runs Christoph Egger
2011-02-09 14:29 ` Kamala Narasimhan [this message]
2011-02-09 14:42 ` Christoph Egger
2011-02-09 14:46 ` Kamala Narasimhan
2011-02-09 15:32 ` Christoph Egger
2011-02-09 15:42 ` Kamala Narasimhan
2011-02-09 15:52 ` Christoph Egger
2011-02-09 15:54 ` Christoph Egger
2011-02-09 17:39 ` Gianni Tedesco
2011-02-10 8:55 ` Ian Campbell
2011-02-10 9:26 ` Vincent Hanquez
2011-02-10 11:24 ` Ian Campbell
2011-02-10 11:32 ` Christoph Egger
2011-02-10 11:43 ` Ian Campbell
2011-02-10 12:23 ` Christoph Egger
2011-02-10 12:42 ` Ian Jackson
2011-02-10 21:55 ` Vincent Hanquez
2011-02-11 8:03 ` Ian Campbell
2011-02-11 9:49 ` Tim Deegan
2011-02-11 11:16 ` Vincent Hanquez
2011-02-10 18:30 ` Gianni Tedesco
2011-02-10 19:33 ` Ian Jackson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D52A4E3.7070907@gmail.com \
--to=kamala.narasimhan@gmail.com \
--cc=Christoph.Egger@amd.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.