Hi,
Junjiro from AUFS solves my problem. He gave a patch to apply in my kernel
sources. After the compilation, I tested checkpointing and retore a VE with
AUFS root and everthing works.
Attached, the patch for who wants to use AUFS and OpenVZ.
On Fri, May 22, 2009 at 12:07:05AM -0300, Josiney
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:
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=msggoto=27142;
To fix this issue, recompile
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
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
