OpenVZ Forum


Home » General » Support » There is great concern that OpenVZ is no longer being supported.
Re: There is great concern that OpenVZ is no longer being supported. [message #38394 is a reply to message #38390] Sun, 13 December 2009 17:50 Go to previous messageGo to previous message
pva0xd is currently offline  pva0xd
Messages: 24
Registered: February 2008
Junior Member

kir wrote on Sun, 13 December 2009 19:28

What I said (and you can clearly see this from my quote above)
(1) is you do not have to use RHEL in order to use RHEL-based OpenVZ kernels;
(2) You can run RHEL5 based OpenVZ kernel on most of the other (i.e. non-RHEL5) distros.

Now, you are telling me it's nonsense and provide some information about what kernels some distros are using.

I am sorry but I can not get the connection here -- why the information that ALTLINUX uses 2.6.27-based kernel (and Mandriva uses 2.6.26-based one, and so on) lead you to the conclusion that I'm telling nonsense (i.e. either my point (1) or (2) above (or both) is/are invalid)?


Ok, let me explain this. I showed you that distributions do not use RHEL kernels. Since there is zero probability that anyone manages to dig openvz related fixes from one big hunk of code you provide us with (RHEL5 patchset + openvz patchset in one go), I'm sure that very few recent openvz related fixes get to distributions. This means that openvz upstream does not support all distributions but RHEL based and since the topic of this discussion is "There is great concern that OpenVZ is no longer being supported." repetition that 2.6.18 based kernels are supported is nonsense or at least does not justify that openvz is supported anywhere beside RHEL5.

kir wrote on Sun, 13 December 2009 19:28
Believe me or not, we are doing the best we can -- for now we only have resources to support RHEL5-based kernels, plus I hope we will start porting to 2.6.32/RHEL6 in some non-too-distant future.


While new branch sounds great, without change in workflow it just makes problem a bit less visible, but still new branch will not fix the problem. The greatest concern is that at some point of time after creation of new branch it will stop to evolve and while we will see new RHEL based kernels and ChangeLog will tell us that some openvz related fixes are there, git will keep silence and these fixes became inaccessible for those who are unable to use RHEL kernels. The only change in workflow I'm looking for is - please, update git whenever something was fixed in openvz. It is understandable why you use RHEL patchset after all and why production kernels are based on it, but it's hard to see why patches are provided as one big hunk of code without real possibility to separate RHEL changes from openvz. So, please, if you start new branch do not abandon it, like it is now! Just commit fixes there so we could see, test and use the progress. As a side result of this workflow you will have more beta testers and this will help you to release more well tested kernels (then with internal testing process you have now). This workflow looks easy but probably I'm completely wrong here and there are reasons to drop git at some point of time and leave community with known bugs.

Any way thanks, that you still answer here, Kir. It's really appreciated that upstream at least tries to hear us.
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: No networking, tried everything
Next Topic: more than vps on server node keep restart itself
Goto Forum:
  


Current Time: Mon Aug 11 20:35:11 GMT 2025

Total time taken to generate the page: 0.39116 seconds