|
|
|
|
|
|
|
|
|
|
xen-devel
RE: [Xen-devel] Help booting Xen under RHEL6 beta2
To: |
Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, Konrad Wilk <konrad.wilk@xxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, DonDutile <ddutile@xxxxxxxxxx>, Young <m.a.young@xxxxxxxxxxxx>, Pasi Kärkkäinen <pasik@xxxxxx> |
Subject: |
RE: [Xen-devel] Help booting Xen under RHEL6 beta2 |
From: |
Dan Magenheimer <dan.magenheimer@xxxxxxxxxx> |
Date: |
Wed, 14 Jul 2010 08:31:05 -0700 (PDT) |
Cc: |
|
Delivery-date: |
Wed, 14 Jul 2010 08:32:47 -0700 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
In-reply-to: |
<5145e706-b158-4e15-b8ec-1eae862800b1@default> |
List-help: |
<mailto:xen-devel-request@lists.xensource.com?subject=help> |
List-id: |
Xen developer discussion <xen-devel.lists.xensource.com> |
List-post: |
<mailto:xen-devel@lists.xensource.com> |
List-subscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
List-unsubscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
References: |
<4a7f9b7c-0f2d-4f6c-898d-9716d55e1ace@xxxxxxxxxxxxxxxxxxxx%keir.fraser@eu.citrix.com> <41c3a749-4692-4a27-8a37-8f0fa17ab2e7@default 20100713013004.GA8022@xxxxxxxxxxxxxxxxxxx 5145e706-b158-4e15-b8ec-1eae862800b1@default> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
Just to close this for posterity:
Move along, these are not the droids you are looking for.
In days of debugging this problem (and also during much help
from Konrad), I had always manually started xenstored before
attempting to start xend. And every time I had tried xl,
I had tried it after attempting to start xend, and it had
failed.
Apparently starting xend (in 4.0.1-rcX) AFTER starting
xenstored puts xenstored into a very strange state, after
which neither xm nor xl will work (but xenstore-ls and
friends do work). In this state, all socket connections
fail. So the classic joke: If it hurts when you do that,
don't do that.
Bottom line: RHEL6b2 distro with 2.6.32.x pvops dom0 with
xen-4.0-testing works.
Thanks to everyone for helping on this!
Dan
> -----Original Message-----
> From: Dan Magenheimer
> Sent: Tuesday, July 13, 2010 5:55 PM
> To: Konrad Wilk; Keir Fraser; Ian Campbell; Stefano Stabellini; xen-
> devel@xxxxxxxxxxxxxxxxxxx; DonDutile; Young
> Subject: RE: [Xen-devel] Help booting Xen under RHEL6 beta2
>
> Status update: Still no go.
>
> Konrad and I repeated some of the obvious xenstored related
> possible problems and everything looks fine.
>
> I tried rolling back the pvops evtchn/gntdev naming changes.
> No difference. I tried rolling back the tools evtchn changeset
> (21182). No difference.
>
> Best I can tell so far, this seems to be something unique
> to RHEL6b2 but don't have the xenstored skills to debug
> any further.
>
> Dan
>
> > -----Original Message-----
> > From: Konrad Rzeszutek Wilk
> > Sent: Monday, July 12, 2010 7:30 PM
> > To: Dan Magenheimer
> > Cc: Keir Fraser; Ian Campbell; Stefano Stabellini; xen-
> > devel@xxxxxxxxxxxxxxxxxxx; DonDutile; Young
> > Subject: Re: [Xen-devel] Help booting Xen under RHEL6 beta2
> >
> > On Mon, Jul 12, 2010 at 05:39:34PM -0700, Dan Magenheimer wrote:
> > > > I'm in the process of doing a fresh build which will
> > > > take awhile.
> > >
> > > Backing out to xen-4.0.1-rc3 did not help, though short
> > > of reinstalling the entire system from scratch, I'm not
> > > sure how to ensure I've backed _everything_ out to rc3...
> > > there's too many flying parts.
> >
> > Well, you can try to back-out the two changes in the pv-ops kernel.
> >
> > git revert 376d908f52427591cef4acd172db9c3ef28676ec
> >
> > and
> > git revert 9d85e25edbcb8a684db8470119077475ac4d90b5
> >
> > And that way the pv-ops kernel can run with Xen 4.0 and Xen 4.0-
> > unstable
> > as well.
> >
> > It could also be that you are mixing two versions of Xen. As in you
> > might have the distro's libs and then yours. Perhaps a bit of find /
> > -name libxens*.so could shed some light?
> >
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|