From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Help booting Xen under RHEL6 beta2 Date: Mon, 12 Jul 2010 21:38:50 +0100 Message-ID: References: <4a7f9b7c-0f2d-4f6c-898d-9716d55e1ace@default> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4a7f9b7c-0f2d-4f6c-898d-9716d55e1ace@default> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Dan Magenheimer , Ian Campbell , Stefano Stabellini Cc: "xen-devel@lists.xensource.com" , DonDutile , Konrad Wilk , Young List-Id: xen-devel@lists.xenproject.org On 12/07/2010 21:19, "Dan Magenheimer" wrote: > 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. Those dom0 registry entries would be written by xend. If you just run xenstored, you'd expect the database to be pretty empty. Looks like xenstored is running okay. Perhaps xend is trying to connect to xenstored in a different way to xenstore-ls. There are two different ways to connect -- via a Unix domains socket /var/run/xenstored/socket; or via a kernel device /proc/xen/xenbus. -- Keir