Date: Mon, 26 Apr 2021 13:39:52 -0400 From: Mark Johnston <markj@freebsd.org> To: =?utf-8?B?SW9udcib?= Mihalache <ionut.mihalache1506@gmail.com> Cc: freebsd-hackers@freebsd.org Subject: Re: cap_sysctlbyname for hw.vmm.destroy Message-ID: <YIb66AlmFG0DPn%2BG@nuc> In-Reply-To: <CAOxbktY6GZY2rfyYMoTquyn04rM2GB5S2opAF1gDxh2177frLg@mail.gmail.com> References: <CAOxbktY6GZY2rfyYMoTquyn04rM2GB5S2opAF1gDxh2177frLg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Apr 26, 2021 at 05:16:14PM +0300, Ionuț Mihalache wrote: > Hello, > > I am working on adding capsicum support for the bhyve snapshot feature. At > the end of the suspend process, the guest should be destroyed and the code > handles this part with a sysctlbyname call which is not working in > capability mode. I don't know what is the problem but even when using > cap_sysctlbyname I still get the same error code (EPERM). I tried the > example from the documentation aswell [1] and still the same error code. > What could be the problem? I have a FreeBSD13 host and a FreeBSD13 guest. I'm not sure why it would happen unless the casper process is somehow running as a non-root user. Can you share the code you're testing somewhere?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YIb66AlmFG0DPn%2BG>