From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Help booting Xen under RHEL6 beta2 Date: Tue, 13 Jul 2010 07:19:31 +0100 Message-ID: References: <720e168c-c67f-4166-99b4-a34a9bc89455@default> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <720e168c-c67f-4166-99b4-a34a9bc89455@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: Konrad, "xen-devel@lists.xensource.com" , DonDutile , Rzeszutek Wilk , Young List-Id: xen-devel@lists.xenproject.org On 12/07/2010 22:36, "Dan Magenheimer" wrote: >> Xen-4.0-testing:19983 would be the c/s being discussed there. > > Could you confirm that number? The changeset says > "xend: Fix use of set() for Python 2.3" and it was > 11 months ago which doesn't match the "roll back to > xen-4.0.1-rc3" suggestion in the xen-users thread, > so I'm confused. Sorry it's 21182. I was looking in 3.4 tree by mistake. -- Keir > The device-node minors do match between /dev/xen and /proc/misc. > > I'm in the process of doing a fresh build which will > take awhile. > > Thanks, > Dan > >> -----Original Message----- >> From: Keir Fraser [mailto:keir.fraser@eu.citrix.com] >> Sent: Monday, July 12, 2010 3:10 PM >> To: Dan Magenheimer; Ian Campbell; Stefano Stabellini >> Cc: Young; xen-devel@lists.xensource.com; DonDutile; Konrad Wilk >> Subject: Re: [Xen-devel] Help booting Xen under RHEL6 beta2 >> >> Xen-4.0-testing:19983 would be the c/s being discussed there. You could >> try >> reverting it and see how that goes for you. But if you have >> /dev/xen/evtchn >> and /dev/xen/gntdev then (assuming the device nodes aren't bogus for >> some >> reason, and there's no reason they should be) you should be good to go >> in >> this respect. You could double check by 'ls -l /dev/xen' and compare >> the >> device-node minors to the list in /proc/misc. >> >> -- Keir >> >> On 12/07/2010 21:44, "Dan Magenheimer" >> wrote: >> >>> 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@eu.citrix.com] >>>> Sent: Monday, July 12, 2010 2:39 PM >>>> To: Dan Magenheimer; Ian Campbell; Stefano Stabellini >>>> Cc: Young; xen-devel@lists.xensource.com; DonDutile; Konrad Wilk >>>> Subject: Re: [Xen-devel] Help booting Xen under RHEL6 beta2 >>>> >>>> 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 >>>> >>>> >> >>