Date: Tue, 9 Sep 2025 15:33:06 +0100 From: void <void@f-m.fm> To: freebsd-virtualization@freebsd.org Subject: Re: bhyve rw access to host filesystem? Message-ID: <aMA6otBlKSsK-QQM@int21h> In-Reply-To: <aMAwFNbSSfKAGh5D@amaryllis.le-fay.org> References: <aMAjoodDyaJIahJl@int21h> <aMAwFNbSSfKAGh5D@amaryllis.le-fay.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, thanks for replying On Tue, Sep 09, 2025 at 02:48:04PM +0100, Lexi Winter wrote: >this is what p9fs(4) is for. I thought it was something like this I saw somewhere :D >to export the filesystem, add a virtio-9p device to bhyve: > bhyve [...] -s 5:0,virtio-9p,myshare=/some/path,rw > 'myshare' should be replaced with a descriptive name for the share, > and change 'rw' to 'ro' to make it read-only. I'd like it to be mounted rw - did you mean that ro is the only correct option or can it be either? >note that unlike NFS, this doesn't work automatically for descendent >mountpoints on the host (e.g., ZFS filesystem hierarchies); instead >you need to export and mount each child filesystem separately. so - in a guest poudriere instance, if i make the mount for /usr/poudriere to be on an imported p9fs, but with respect to the host this would be on a ufs fs without seperate mountpoints. It'd be able to make all of its tmp dirs etc below /usr/poudriere on demand, if I understand correctly. --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aMA6otBlKSsK-QQM>