Hi, > It will be rhel kernels in deb format. I'm going to test out some > aspects to see what kind of obstacles we can face.
Maybe I should try these too... I'm really undecided what to do with my current OpenVZ installations. My machines are old amd64 without CPU virtualisation capabilities, which rules out KVM. That also means Qemu, VirtualBox etc. would be too slow, and wasteful of resources by running a separate instance of the kernel for each guest. I think Xen would be awkward for the same reason, though I'm keeping it in mind as an option. The shared kernel between guests is openvz's particular strength. I'm under the impression that LXC doesn't yet provide the isolation of superuser privileges (due to procfs?) that I need. Also I still suffer from issues in 2.6.32 (and 2.6.26) on my main production box that I haven't been able to reproduce on any spare machine; I haven't been able to test for these problems in Debian 3.x kernels due to the lack of openvz, so the best I can do is probably try one of these rhel kernels. In the long term maybe openvz will come back for the next Debian release after Wheezy (then maybe in Wheezy backports), or maybe LXC will get the extra features I need. Or perhaps by then I can afford shiny new hardware with CPU support for virtualisation. :) > I'm running root system on lvm on cryptfs.. Same here, I run these on top of mdraid. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f2f88b5.1030...@pyro.eu.org