OpenVZ Forum


Home » Mailing lists » Users » ovz on Slackware
ovz on Slackware [message #8755] Tue, 05 December 2006 13:22 Go to next message
barf is currently offline  barf
Messages: 4
Registered: December 2006
Location: Christcurch, New Zealand
Junior Member
Hello everyone
I'm trying to setup OpenVZ on a Slackware 10.2 HN
So far compiled and modified scripts to use the BSD init scripts (no
/etc/sysconfig) but I get this error:

# vzctl start 101
Starting VE ...
VE is mounted
Unable to set capability: Operation not permitted
Unable to set capability
VE start failed
VE is unmounted
#

Can anyone provide me with some insight into possible causes of this error?
What is "vps.mount" and is it not included in the source code tarballs
for a reason?

Thanks
-Stuart

--
Stuart MacIntosh
IT Consultancy & Technical Services
Phone: +64 21 2259576
Email: stuart@linuxsecurity.co.nz
Re: ovz on Slackware [message #8756 is a reply to message #8755] Tue, 05 December 2006 14:54 Go to previous messageGo to next message
Vasily Tarasov is currently offline  Vasily Tarasov
Messages: 1345
Registered: January 2006
Senior Member
Hello,

can you, please, specify kernel version you're using and output of
`cat /proc/sys/kernel/cap-bound` command.

Thanks,
Vasily.


Stuart MacIntosh wrote:
> Hello everyone
> I'm trying to setup OpenVZ on a Slackware 10.2 HN
> So far compiled and modified scripts to use the BSD init scripts (no
> /etc/sysconfig) but I get this error:
>
> # vzctl start 101
> Starting VE ...
> VE is mounted
> Unable to set capability: Operation not permitted
> Unable to set capability
> VE start failed
> VE is unmounted
> #
>
> Can anyone provide me with some insight into possible causes of this
> error?
> What is "vps.mount" and is it not included in the source code tarballs
> for a reason?
>
> Thanks
> -Stuart
>
> ------------------------------------------------------------ ------------
>
Re: ovz on Slackware [message #8758 is a reply to message #8756] Tue, 05 December 2006 15:41 Go to previous messageGo to next message
barf is currently offline  barf
Messages: 4
Registered: December 2006
Location: Christcurch, New Zealand
Junior Member
I fixed it!
Upon digging through the forums I found CONFIG_SECURITY seems to break
OpenVZ and I had the kernel (2.6.18-028test005) compiled with that
option. But thanks anyway!

Vasily Tarasov wrote:
> Hello,
>
> can you, please, specify kernel version you're using and output of
> `cat /proc/sys/kernel/cap-bound` command.
>
> Thanks,
> Vasily.
>
>
> Stuart MacIntosh wrote:
>
>> Hello everyone
>> I'm trying to setup OpenVZ on a Slackware 10.2 HN
>> So far compiled and modified scripts to use the BSD init scripts (no
>> /etc/sysconfig) but I get this error:
>>
>> # vzctl start 101
>> Starting VE ...
>> VE is mounted
>> Unable to set capability: Operation not permitted
>> Unable to set capability
>> VE start failed
>> VE is unmounted
>> #
>>
>> Can anyone provide me with some insight into possible causes of this
>> error?
>> What is "vps.mount" and is it not included in the source code tarballs
>> for a reason?
>>
>> Thanks
>> -Stuart
>>
>> ------------------------------------------------------------ ------------
>>
--
Stuart MacIntosh
IT Consultancy & Technical Services
Phone: +64 21 2259576
Email: stuart@linuxsecurity.co.nz
Re: ovz on Slackware [message #8763 is a reply to message #8755] Tue, 05 December 2006 17:44 Go to previous message
kir is currently offline  kir
Messages: 1645
Registered: August 2005
Location: Moscow, Russia
Senior Member

Stuart MacIntosh wrote:
> Hello everyone
> I'm trying to setup OpenVZ on a Slackware 10.2 HN
> So far compiled and modified scripts to use the BSD init scripts (no
> /etc/sysconfig) but I get this error:
BTW feel free to contribute your Slackware-specific initscript for vz
and we will include it into next vzctl release ;)
Previous Topic: iptables are not working under 2.6.18-028test005.1 in VE
Next Topic: OpenVZ 2.6.18-ovz028test005.1 crashing on DELL PE 2950
Goto Forum:
  


Current Time: Sun Oct 06 08:35:15 GMT 2024

Total time taken to generate the page: 0.07901 seconds