Comment 2 for bug 634900

I just updated my 10.04 LTS to 10.04.1 and fell into this trap. It is very annoying and I think the importance should be increased. The problem is that the original /etc/init.d/ssh included a test for virtual environments (searching for some string in /proc/self/status, it's gone after the update, of course) and prevented oom manipulation in these environments. It seems that this test has not found its way into upstart when handling the "oom" keyword.

In my case, I do not have any console access to the virtual environment. So I had absolutely no way of fixing this. Luckily, I had a very recent full backup and I could restore the system from the container management console.