xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Kathy Hadley <Kathy.Hadley@dornerworks.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 1/1] Xen ARINC 653 Scheduler (updated to add support for CPU pools)
Date: Thu, 17 Jun 2010 19:26:47 +0100	[thread overview]
Message-ID: <C8402777.17C7F%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <D3E384327F5C6D48AADCEA84160B7D730147110B@mcbain.dw.local>

On 17/06/2010 19:16, "Kathy Hadley" <Kathy.Hadley@dornerworks.com> wrote:

> line 18, in xshandle
>     xs_handle = xen.lowlevel.xs.xs()
> Error: (2, 'No such file or directory')
> [2010-06-17 13:58:50 2302] INFO (SrvDaemon:220) Xend exited with status
> 1.
> 
> Any suggestions?

Xend no longer automatically starts xenstored for you (that was moved to
example init scripts which you may not have installed). So you need to
'xenstored; xenconsoled; xend start'.

 -- Keir

  reply	other threads:[~2010-06-17 18:26 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-16 15:04 [PATCH 1/1] Xen ARINC 653 Scheduler (updated to add support for CPU pools) Kathy Hadley
2010-06-16 15:50 ` George Dunlap
2010-06-16 16:00   ` Kathy Hadley
2010-06-16 16:13     ` Keir Fraser
2010-06-16 16:14     ` George Dunlap
2010-06-16 16:20       ` Keir Fraser
2010-06-16 16:25         ` Kathy Hadley
2010-06-16 16:31           ` Keir Fraser
2010-06-16 16:40             ` Kathy Hadley
2010-06-16 16:49               ` Keir Fraser
2010-06-16 18:03                 ` Kathy Hadley
2010-06-17  7:04                   ` Keir Fraser
2010-06-17 18:16                     ` Kathy Hadley
2010-06-17 18:26                       ` Keir Fraser [this message]
2010-06-18 17:35                     ` Kathy Hadley
2010-06-18 17:49                       ` Keir Fraser
2010-06-19 11:14                       ` George Dunlap
2010-06-22 19:10                     ` Kathy Hadley
2010-06-22 19:16                       ` Keir Fraser
2010-06-23 19:57                         ` Kathy Hadley
2010-06-23 20:23                           ` Keir Fraser
2010-06-23 21:16                             ` Kathy Hadley
2010-06-23 22:36                               ` Keir Fraser
2010-06-24 12:53                                 ` Kathy Hadley
2010-06-24 13:08                                   ` Dan Magenheimer
2010-06-24 13:18                                     ` Kathy Hadley
2010-06-24 13:23                                     ` Keir Fraser
2010-06-24 13:32                                       ` Kathy Hadley
2010-06-30 20:44                                 ` Kathy Hadley
2010-06-30 20:54                                   ` Keir Fraser
2010-07-14 17:32                                     ` Kathy Hadley
2010-07-14 18:04                                       ` Keir Fraser
2010-06-16 16:25         ` George Dunlap
2010-06-17  5:02         ` Juergen Gross
2010-06-17  6:09           ` Keir Fraser

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=C8402777.17C7F%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=Kathy.Hadley@dornerworks.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).