Date: Wed, 16 Aug 2017 16:40:23 -0700 From: Peter Grehan <grehan@freebsd.org> To: John Baldwin <jhb@freebsd.org>, freebsd-current@freebsd.org Cc: Panagiotes Mousikides <paggas1@yandex.com>, Matt Joras <mjoras@freebsd.org>, "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>, allanjude@freebsd.org Subject: Re: Install FreeBSD from source into VM image Message-ID: <ee79f698-2b9f-4d88-cc19-177ef2f0647f@freebsd.org> In-Reply-To: <25569442.iT463nDDSg@ralph.baldwin.cx> References: <8888acfa-4dc8-a68f-8ca8-c4df84e5e74a@yandex.com> <97d0475c-9603-03d8-144d-dc803e5530c7@FreeBSD.org> <9152fc29-125d-1c01-ecfa-740a1cfcaadd@yandex.com> <25569442.iT463nDDSg@ralph.baldwin.cx>
index | next in thread | previous in thread | raw e-mail
>> Error return from kevent monitor: Not permitted in capability mode ... > This sounds like an issue with the bhyve capsicum work. I've cc'd Allan > and Peter who might be able to help track that down. It might be useful > if you can run bhyve under ktrace, e.g.: > > sudo ktrace -i -t p sh /usr/share/examples/bhyve/vmrun.sh -d aaaa.raw vm-aaaa > > And then post the output of 'sudo kdump' I think this is the error now returned when a file doesn't exist or can't be accessed - the code probably needs to be reworked to test for existence before entering capability mode to make the error more meaningful. later, Peter.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ee79f698-2b9f-4d88-cc19-177ef2f0647f>