From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Young <m.a.young@durham.ac.uk>,
xen-devel@lists.xensource.com, DonDutile <ddutile@redhat.com>,
Konrad Wilk <konrad.wilk@oracle.com>
Subject: RE: Help booting Xen under RHEL6 beta2
Date: Mon, 12 Jul 2010 13:19:29 -0700 (PDT) [thread overview]
Message-ID: <4a7f9b7c-0f2d-4f6c-898d-9716d55e1ace@default> (raw)
In-Reply-To: <1278945437.24714.171.camel@zakaz.uk.xensource.com>
OK, so here's another interesting piece of information:
The xend.log python error trace ends with:
xs_handle = xen.lowlevel.xs.xs()
Error: (111, 'Connection refused')
So I rebooted (with xend disabled), manually started xenstored,
and ensured xenstored is indeed running with ps -ef.
Then I tried "xenstore-ls" and all I get is:
tool = ""
xenstored = ""
local = ""
I tried this on a EL5-based distro running a 2.6.18.8-xen
dom0 (with xend disabled on boot) and xenstore-ls gives
me a long list of dom0 related registry entries.
So maybe xenstored is dependent on some distro configuration
that is missing on RHEL6b2?
Thanks,
Dan
P.S. I checked /dev/xen and it does contain evtchn and gntdev
and my kernel config does have CONFIG_XEN_DEV_EVTCHN=y
> -----Original Message-----
> From: Ian Campbell [mailto:Ian.Campbell@citrix.com]
> Sent: Monday, July 12, 2010 8:37 AM
> To: Stefano Stabellini
> Cc: Dan Magenheimer; xen-devel@lists.xensource.com; Konrad Rzeszutek
> Wilk; DonDutile; Young
> Subject: Re: [Xen-devel] Help booting Xen under RHEL6 beta2
>
> On Mon, 2010-07-12 at 15:06 +0100, Stefano Stabellini wrote:
> > On Mon, 12 Jul 2010, Dan M @ Oracle wrote:
> > > Is xencommons in 4.0-testing? If so, where?
> >
> > in the sources:
> >
> > tools/hotplug/Linux/init.d/xencommons
> >
> > it should be installed in /etc/init.d
>
> That change is only in xen-unstable, isn't it? In xen-4.0-testing it
> looks to me like tools/misc/xend still takes care of it so if you've
> switched to xl in that branch you might still need to start stuff by
> hand.
>
> Ian.
>
>
next prev parent reply other threads:[~2010-07-12 20:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 22:16 Help booting Xen under RHEL6 beta2 Dan Magenheimer
2010-07-09 5:30 ` Pasi Kärkkäinen
2010-07-09 14:09 ` Don Dutile
2010-07-09 17:44 ` Konrad Rzeszutek Wilk
2010-07-09 18:09 ` M A Young
2010-07-09 20:01 ` Konrad Rzeszutek Wilk
2010-07-09 22:48 ` Dan Magenheimer
2010-07-09 23:27 ` M A Young
2010-07-10 21:42 ` Dan Magenheimer
2010-07-11 2:24 ` Dan Magenheimer
2010-07-12 10:37 ` Stefano Stabellini
2010-07-12 13:59 ` Dan M @ Oracle
2010-07-12 14:06 ` Stefano Stabellini
2010-07-12 14:30 ` Keir Fraser
2010-07-12 14:37 ` Ian Campbell
2010-07-12 20:19 ` Dan Magenheimer [this message]
2010-07-12 20:38 ` Keir Fraser
2010-07-12 20:44 ` Dan Magenheimer
2010-07-12 21:10 ` Keir Fraser
2010-07-12 21:36 ` Dan Magenheimer
2010-07-13 6:19 ` Keir Fraser
2010-07-13 0:39 ` Dan Magenheimer
2010-07-13 1:30 ` Konrad Rzeszutek Wilk
2010-07-13 23:55 ` Dan Magenheimer
2010-07-14 15:31 ` Dan Magenheimer
[not found] <4a7f9b7c-0f2d-4f6c-898d-9716d55e1ace@defaultC8613BEA.3186%keir.fraser@eu.citrix.com>
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=4a7f9b7c-0f2d-4f6c-898d-9716d55e1ace@default \
--to=dan.magenheimer@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=ddutile@redhat.com \
--cc=konrad.wilk@oracle.com \
--cc=m.a.young@durham.ac.uk \
--cc=stefano.stabellini@eu.citrix.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).