> 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.
So I think you should completly forget that kernel as it should has not been released and it seems nobody is working on it in the CVS (maybe the guy is on holidays after the release of FC6...) so be patient... I think this would be fix in few days. (hope)
Best regards,
G. Bougard
Attachment:
signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=
-- Fedora-xen mailing list Fedora-xen@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-xen
