| Re: There is great concern that OpenVZ is no longer being supported. [message #38391 is a reply to message #38385] |
Sun, 13 December 2009 16:31   |
 |
aTan
Messages: 29
Registered: March 2008
|
Junior Member |
|
|
| Paparaciz wrote on Sun, 13 December 2009 15:35 | | aTan wrote on Sun, 13 December 2009 15:39 | I'm aware of it, but 2.6.18 is just old. And as it was said above doesn't fulfill todays needs even with some backported stuff. Could you just say you won't support newer kernels in the near future (maybe until RH customers will need it), so people can stop hoping for it and try find some other solutions for their needs or at least put up with this? I guess people will appreciate it and also won't bother you with this question in the future. Sticking it in Support forum will be also fine.
|
what exactly doesn't work for you in rhel kernel 2.6.18?
also keep in mind that in next year redhat should release rhel6 version which will be based on newer kernel (i guess that it would be 2.6.3x).
|
For me (small company's needs) it's just: no xtables, no upstream IPv6, some 3rd party patches (imq, (e)sfq, etc) are provided only for new kernels, it's slower (not such a big deal). And I'm sure there will be a lot more issues if I'll try to downgrade from 2.6.27 (udev needs at leas 2.6.25 since version 145, newer toolchain (gcc4.4, binutils 2.20) can has problems with 2.6.18, etc). And I'm sure there must be a lot other problems I'm not aware of. It's not only about last number in a kernel version.
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
