Bug#513310: [Debian] Re: Bug#513310: vzctl fails to set capabilities, and subsequently fails to start any VE

2009-01-29 Thread Daniel Pittman
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

Bug#513310: [Debian] Re: Bug#513310: vzctl fails to set capabilities, and subsequently fails to start any VE

2009-01-29 Thread Ola Lundqvist
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

Bug#513310: [Debian] Re: Bug#513310: vzctl fails to set capabilities, and subsequently fails to start any VE

2009-01-29 Thread Ola Lundqvist
This was already corrected in vzctl (3.0.22-9) unstable; urgency=low * Correction of capability problem on some platforms. Closes: #482974. -- Ola Lundqvist o...@debian.org Sat, 7 Jun 2008 19:26:21 +0200 Do you have any other idéa? // Ola On Thu, Jan 29, 2009 at 08:54:13AM +0100, Ola

Bug#513310: [Debian] Re: Bug#513310: vzctl fails to set capabilities, and subsequently fails to start any VE

2009-01-29 Thread Ola Lundqvist
Hi Kir and Daniel When I started to backport this fix, I realized that this fix was already backported to the version running. This means that we have some other problem that has been fixed in the 3.0.23 version available in experimental. Best regards, // Ola On Thu, Jan 29, 2009 at

Bug#513310: [Debian] Re: Bug#513310: vzctl fails to set capabilities, and subsequently fails to start any VE

2009-01-29 Thread Kir Kolyshkin
I'm not really sure but maybe this one can help: http://git.openvz.org/?p=vzctl;a=commitdiff;h=bca585d9c7c9e72bad99fc3f48bd8245ab21848c Daniel, can you try it out? If that does not work I need straces from both working and non-working versions. Ola Lundqvist wrote: This was already

Bug#513310: [Debian] Re: Bug#513310: vzctl fails to set capabilities, and subsequently fails to start any VE

2009-01-29 Thread Ola Lundqvist
Hi Daniel If you could try this fix out it would be really great. A built package for amd64 is available at: http://apt.inguza.org/vzctl/ // Ola On Thu, Jan 29, 2009 at 07:57:54PM +0300, Kir Kolyshkin wrote: I'm not really sure but maybe this one can help:

Bug#513310: [Debian] Re: Bug#513310: vzctl fails to set capabilities, and subsequently fails to start any VE

2009-01-29 Thread Daniel Pittman
Ola Lundqvist o...@inguza.com writes: If you could try this fix out it would be really great. A built package for amd64 is available at: http://apt.inguza.org/vzctl/ Ah. I am on amd64, and that is an i386 package without source. Anyway, I grabbed the source, manually applied the patch and

Bug#513310: [Debian] Re: Bug#513310: vzctl fails to set capabilities, and subsequently fails to start any VE

2009-01-28 Thread Kir Kolyshkin
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: http://git.openvz.org/?p=vzctl;a=commit;h=0d6bfad92c7cb6a193801ce8dac3a0dc64396ca8 So the solution is either to

Bug#513310: [Debian] Re: Bug#513310: vzctl fails to set capabilities, and subsequently fails to start any VE

2009-01-28 Thread Ola Lundqvist
Hi Kir I will backport this fix. I thought I already did that. Thanks! // Ola Quoting Kir Kolyshkin k...@openvz.org: 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: