Hi Daniel
Thanks a lot for your information. I'll backport the fix today, upload
and request unblock to the debian release team.
Best regards,
// Ola
Quoting Daniel Pittman <dan...@rimspace.net>:
Kir Kolyshkin <k...@openvz.org> writes:
This is caused by newer kernel headers (in this case on a build system
that was used to build this vzctl package), and is fixed in
vzctl-3.0.23. See the following git commit:
vzctl 3.0.23-2 is available in experimental, so I have installed it and
tested it on my machine; it addresses the problem and the VE will again
start.
So the solution is either to upgrade to vzctl-3.0.23 or to backport
this simple fix.
I can confirm that the newer package version resolves the problem.
Ola Lundqvist wrote:
Hi Daniel
This is interesting as it works very well on my systems. On other
hand that system is a 686 based one.
You write that you have not significantly changed your system, but at
the same time you write that you are not sure that it has ever worked
with the 2.6.26 kernel.
Sorry, I see I was unclear: I have upgraded to sid, which significantly
changed the system, but the OpenVZ configuration remained stable.
I thought that the VE had started successfully under 2.6.26 before, but
could only confirm from my logs that I had used it under 2.6.24.
Sorry for being so unclear, and thankfully Kir has saved me by
identifying the problem despite my poor communication.
Regards,
Daniel
--
--- Inguza Technology AB --- MSc in Information Technology ----
/ o...@inguza.com Annebergsslingan 37 \
| o...@debian.org 654 65 KARLSTAD |
| http://inguza.com/ Mobile: +46 (0)70-332 1551 |
\ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 /
---------------------------------------------------------------
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
