openvz 2.6.18 is not an old kernel at all, it is the best maintained *stable* kernel out there, with hundreds of backports fixes, based on the stable redhat5 kernel.
I had in my beginnings various problems with oopses and panics using 24 and 27 kernels, and all disappeared running 2.6.18. Heck, even 2.6.9 redhat kernel is considered *superstable* for use as host server. The next host-kernel which will be considered stable for openvz will either be 2.6.32 or 2.6.31, i dearly hope it will be 32, the decision will be based on what redhat will take as next stable kernel for redhat6, soon to be released (midyear). So, basically there will be rather a long-time usage of 2.6.18 as stable servers and I definitly want ubuntu lucid server vps's ... I second that this bug HAS to be fixed somehow and can not be considered: "non-fixable, kernel to old". There has to be a way to check the dependencys for this mountall stuff and if the kernel is not supported, than fallback to something not so shiny! Heck, lucid will be LTS, the next big upgrade for all which depend on a stable, long supported operating system, and a hellload of people are using VPSes today for a number of reasons, and you can not tell a client with huge openvz host that serves x-vps'es to upgrade to a kernel which has not yet been proven to be as stable as the current stable! ----SNIP---- Ok, with lucid as guest vps the hack above with openvz.conf file does not work for me either! the init.log states: starting init logger init: openvz pre-start process (22408) terminated with status 32 -- OpenVZ kernel out of date, karmic requires 2.6.27 https://bugs.launchpad.net/bugs/436130 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
