[Fedora-xen] kernel-xen0-2.6.18-1.2200.fc5 amusingly unhappy

Daniel P. Berrange berrange at redhat.com
Sat Oct 28 00:19:43 UTC 2006


On Fri, Oct 27, 2006 at 11:13:40PM +0100, Daniel P. Berrange wrote:
> On Fri, Oct 27, 2006 at 11:43:59PM +0200, Guillaume Bougard wrote:
> > Le vendredi 27 octobre 2006 à 16:58 +0100, Daniel P. Berrange a écrit :
> > 
> > > > I think the problem (and fix) has been described pretty well already  
> > > > by Guillaume Bougard:
> > > > 
> > > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=211745
> > > 
> > > I find it very hard to believe that changing 'Xend changeset: unavailable"
> > > to list an explicit changeset has anything at all todo with the problem.
> > > All fedora & RHEL xen builds have the changeset info disabled, and it is
> > > not used in any functional codepath path related to the hypervisor or 
> > > kernel. It is merely a bit of user facing info.
> > > 
> > > Dan.
> > 
> > 
> > Hi all,
> > 
> > just a comment here, what I found is not "changing something to list an
> > explicit changeset", for me this was just a clue to understand the
> > problem.
> > 
> > In fact, when I study a little the xen patch really applied with the
> > kernel-xen0-2.6.18-1.2200.fc5, I discovered the patch is based on xen
> > 3.0.3 which has totally different API than the one expected by the
> > xen-3.0.2 installed in FC5 at that time... What I do to fix the problem
> > is to find the really patch that should be applied (and it's based on
> > xen-3.0.2) and recompiled the kernel, and it was working.
> 
> The RPM version number here is a little misleading. The xen-3.0.2-5.FC5
> RPM is actually based off a very recent pre-release of the 3.0.3 tree
> (changeset 11540). The kernel-xen0-2.6.18-1.20.fc5 is also based off
> a pre-release of the 3.0.3 tree (the same changeset  11540) so they
> match exactly.

Ok, the CVS logs were confusing me here - the hypervisor is on 11540,
but the actual kernel is on 11740 - as Guillaume correctly points out
in his BZ ticket. Since 11740 is only 30 changesets before the 3.0.3
release tar.gz, and those 30 changesets contain some pretty important
bugfixes I plan to just sync the userspace xen RPM upto 3.0.3 official
tar.gz. This should give FC5 a fully operational Xen stack again.

Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 




More information about the Fedora-xen mailing list