On 4/15/07, Asrai khn <asraikhn@xxxxxxxxx> wrote:
So what choice we have left, last kernel that worked for us and still working is 2.6.19-1.2911.6.5.fc6xen the last two kernel-xen updates just broke working installations.
Do we put kernel-xen in our yum.conf 'exclude' or role our own kernel. I love to do it via yum however look like in end we will left with no working kernel-xen if we keep updating kernel-xen from fc6 repo.
I wonders if anyone "accepting" our host reboots/crashing or its just unacceptable bugs?
Thanks.
Askar Ali
On 4/15/07, s@xxxxxxxxxxx < s@xxxxxxxxxxx> wrote:
It is still broken in kernel-xen 2.6.20-1.2944.fc6.
The last stable release appears to be: 2.6.19-1.2911.6.5.fc6xen
Yes you are 100% correct 2nd buggy kernel-xen from fedora folks. Here I fill a bug, however they will look into it and accept it as bug. :-S
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=236474
Machine was randomly rebooting, after sometime once gain fall back to last working kernel ' 2.6.19-1.2911.6.5.fc6xen'
So what choice we have left, last kernel that worked for us and still working is 2.6.19-1.2911.6.5.fc6xen the last two kernel-xen updates just broke working installations.
Do we put kernel-xen in our yum.conf 'exclude' or role our own kernel. I love to do it via yum however look like in end we will left with no working kernel-xen if we keep updating kernel-xen from fc6 repo.
I wonders if anyone "accepting" our host reboots/crashing or its just unacceptable bugs?
Thanks.
Askar Ali
-- Fedora-xen mailing list Fedora-xen@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-xen
