From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Konrad Wilk <konrad.wilk@oracle.com>,
Keir Fraser <keir.fraser@eu.citrix.com>,
Ian Campbell <Ian.Campbell@eu.citrix.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
xen-de
Subject: RE: Help booting Xen under RHEL6 beta2
Date: Tue, 13 Jul 2010 16:55:06 -0700 (PDT) [thread overview]
Message-ID: <5145e706-b158-4e15-b8ec-1eae862800b1@default> (raw)
In-Reply-To: <20100713013004.GA8022@phenom.dumpdata.com>
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@lists.xensource.com; 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?
>
next prev parent reply other threads:[~2010-07-13 23:55 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
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 [this message]
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=5145e706-b158-4e15-b8ec-1eae862800b1@default \
--to=dan.magenheimer@oracle.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=keir.fraser@eu.citrix.com \
--cc=konrad.wilk@oracle.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).