Bug#655385: "Cannot allocate memory" when doing "cat, /proc/self/mountinfo" inside a vm
Am 2012-06-30 13:24, schrieb Tim Small:
> Doesn't that look like dropping Debian+OpenVZ users in it a bit?
I totally agree.
> Suddenly they have to switch to a non-Debian kernel (or otherwise a
> completely different virtualisation technology) half way through a
> stable release with no notice, and then manually track security updates
> outside of the Debian security infrastructure etc.?
You are talking out of my soul.
I can add one additional argument for patching one line (!) in the
Debian kernel over using a totally unofficial RedHat kernel:
OpenVZ's RedHat kernel does not feature everything the Debian kernel
does, especially DRBD!
I cannot live without DRBD, but it got mainline with only 2.6.33, while
RHEL 6 uses 2.6.32 and RedHat refused to backport DRBD in favour of a
similar appoach by themselves.
Proxmox (Debian based virtualization distro) also uses that RedHat
kernel, but at least they don't just alienate it, they add features like
DRBD and rebuild it as Debian package.
So please, either
- integrate that patch
- point us to a replacement kernel that does not cut out DRBD (proxmox?)
> Is LXC considered to be a practical OpenVZ replacement by now? It
> doesn't really seem to be getting much attention, and I can't say I know
> anyone who's using it...
I tried that once, shortly after it became mainline.
At that time it did'nt work with most guest distros because it did'nt
even try to solve the udev mess.
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact email@example.com