I'm honestly not exactly sure of the reason.
When I ran into the -12 error problem you're experiencing, I was applying
the ovz dostoevsky patch to vanilla centos 5.2, salgix 5.0.4 and debian
unstable (both with debian's stock 2.6.26 kernel and a vanilla 2.6.26
kernel). I never received the kernel
A question: This problem I'm getting of "err=-12" is not accompanied by
the noisy kernel dumps mentioned. Does this still sound like a likely cause?
Also, I see that the bug was not fixed:
http://bugzilla.openvz.org/show_bug.cgi?id=802
The last entry was that it worked for the person reporti
John Knight wrote:
To fix this issue, recompile your kernel with this option commented out:
#CONFIG_FAIR_USER_SCHED
#CONFIG_FAIR_GROUP_SCHED
Thanks a lot for the same-day response, John. I think I can use this
tonight on one of our test systems.
--
HostGIS, Open Source solutions for the glob
Hi Greg,
I ran into this problem when building my own ovz kernel, and have since
noted some distro's stock kernels have this issue as well. This seems to be
a symptom of a known bug tied to the kernel scheduling.
http://forum.openvz.org/index.php?t=msg&goto=27142&;
To fix this issue, recompile
I am having a problem creating and starting a new VE.
vzctl start gives me: mounted, container start failed, unmounting.
dmesg shows only this:
CT: 30: stopped
CT: 30: failed to start with err=-12
The verbose log (level 10) is no more useful to me:
Starting container ...
Running: /usr/sbin/vzq
