Ola,
We plan to have it ready in two weeks. The patch that fixes the issue is
in git [1] and I suggest you to take it and build a bugfix update to 3.0.22
[1]
http://git.openvz.org/?p=vzctl;a=commit;h=0d6bfad92c7cb6a193801ce8dac3a0dc64396ca8
Ola Lundqvist wrote:
Hi
Ok, I see. This is a problem on all other platforms than i386. The reason
is that they are automatically built. If the kernel information is wrong
on the build machine it will get this problem.
When is the next release?
Best regards,
// Ola
On Tue, May 27, 2008 at 12:47:50PM +0400, Kir Kolyshkin wrote:
It's just that vzctl needs a header (capability.h, usually this is
/usr/include/linux/capability.h) from an older kernel (i.e. pre 2.6.24).
We hope to fix this in the next vzctl release.
Ola Lundqvist wrote:
Hej Marcus
I'll try to get some comments from upstream about this. I was not
aware of the build dependency towards the kernel.
Kir or anyone else in the openvz group, can you describe this to me?
Best regards,
// Ola
On Mon, May 26, 2008 at 12:28:25PM +0200, Marcus Better wrote:
Package: vzctl
Severity: grave
Version: 3.0.22-8
This started happening recently:
~# vzctl start 107
Starting VE ...
VE is mounted
Unable to set capability: Invalid argument
Unable to set capability
VE start failed
VE is unmounted
Downgrading temporarily to 3.0.11-13 fixed it, but I believe the
problem was introduced in 3.0.22-7. According to upstream it is caused
by compiling against a mis-matched version of
/usr/include/linux/capability.h.
I'm running a self-compiled 2.6.24 OpenVZ kernel.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.25-melech (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
