[Users] Debian 8 packages for OpenVZ as a HN?

[Jonathan Ballet]

Hi,

On 05/10/2015 05:05 PM, Pavel Odintsov wrote:
> Well, well. But why my 2.6.32 kernel become broken after change
> Wheezy's init system to systemd? Standard 3.2 kernel from Debian works
> perfectly with systemd.
>
> If this problems is not related with kdbus but it's still it broke
> ability to run OpenVZ kernel on modern distros.
>
> If somebody will fix this issue I will be very pleased.

I tried booting one of the latest OpenVZ release on Debian Jessie with 
systemd, and I got the error:

   Failed to mount /sys/fs/cgroup: No such file or directory.

This is related to this bug :

   https://bugzilla.redhat.com/show_bug.cgi?id=628004

Basically (AFAIU), the OpenVZ kernel lacks support for mounting cgroups 
at the required place, which make systemd choke when starting up in the 
early phase.
As mentioned in the bug report above, applying the patch from [1] might 
be enough to "fix" the problem, but I haven't tested this one and I'm 
not sure about the consequences.

In the meanwhile, I removed systemd from my Jessie installations and 
switched back to sysvinit-core instead. It works, although that would be 
cool to be able to use systemd.

  Jonathan

[1] 
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=676db4af043014e852f67ba0349dae0071bd11f3

> On Sun, May 10, 2015 at 2:40 PM, Marco d'Itri <md-k2GhghHVRtY at public.gmane.org> wrote:
>> On May 10, Pavel Odintsov <pavel.odintsov-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org> wrote:
>>
>>> Unfortunately, we can't run OpenVZ 2/6/32 kernel on top of systemd
>>> aware system because it lacks kdbus subsystem. But if you changed init
>> All upstream kernels lack kdbus, and systemd does not depend on it.
>>
>> --
>> ciao,
>> Marco