https://bugzilla.novell.com/show_bug.cgi?id=851338
https://bugzilla.novell.com/show_bug.cgi?id=851338#c48
--- Comment #48 from Mark Starikov
Not really sure why so much fuzz about recompiling kernel - this is a 30 minutes job.
Scale? Management? Future versions? Those things come to mind off the top of my head. Sure, recompiling with one option different is a pretty trivial task. Doing it for several hundred virtual machines across different XenServer pools becomes less trivial.
Those are valid points. Not a solution to those problems, but there is a section in the wiki article that describes how to boot kernel image located inside of Dom0 rather than the one placed inside of a VM. This should minimize efforts of distributing kernel to only copying it across Dom0 of the hosts instead of each VM.
One of the reasons we like openSuSE and use it as one of our standard distributions is because things just work - it isn't that we don't like to tinker, or don't know how to, it's that we don't always have the time to.
I completely understand, and I do apologize for the way that comment came out - I wasn't trying to imply that users are incapable of recompiling kernel, just wanted to point out that this thread was leaning more towards arguing why compatibility level should have stayed at 4.1 rather than discussing what can be done about this whole situation.
Thanks for the info...maybe I'll add my steps for installing EC2 kernel and using that for those who are interested.
That'd be great. I'm not sure what's the permissions are on the wiki, so if you cannot edit it yourself, just email me instructions and I'll make sure to add it to the article.
Maybe we could also get a kernel-xen-compat package created in one of the community repos and maintain backward compatibility from there, that way people could just add that repo and install that package. Then SuSE could continue to push the main kernel-xen package forward in terms of compatibility, but those of us who require running it on some of the hosts that take a little longer to catch up would still have options.
I think this would be the best way to go about it. I'm thinking hosted build service that checks for kernel updates daily, recompiles and pushes it to the repo. That way we probably can come up with a way to boot installtion using EC2 kernel -> add repo with compat kernel -> switch version right during installation and restore regular workflow. Perhaps SUSE guys on this thread can help with spec file so version can be directly switched in zypper/yast or suggestions on how to go about the whole thing. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.