RE: [Xen-devel] Help booting Xen under RHEL6 beta2

[Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>]

This recent thread from xen-users with the exact symptoms:
http://www.gossamer-threads.com/lists/xen/users/177223 
(see last in thread) implies that this is the result of
a regression since xen-4.0.1-rc3, though it's vague on
exactly what regressed ("evtchn stuff"?).

I'll try rebuilding to confirm.

> -----Original Message-----
> From: Keir Fraser [mailto:keir.fraser@xxxxxxxxxxxxx]
> Sent: Monday, July 12, 2010 2:39 PM
> To: Dan Magenheimer; Ian Campbell; Stefano Stabellini
> Cc: Young; xen-devel@xxxxxxxxxxxxxxxxxxx; DonDutile; Konrad Wilk
> Subject: Re: [Xen-devel] Help booting Xen under RHEL6 beta2
> 
> On 12/07/2010 21:19, "Dan Magenheimer" <dan.magenheimer@xxxxxxxxxx>
> 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
> 
> 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel