Date: Tue, 9 Sep 2025 15:49:19 +0100 From: Lexi Winter <ivy@freebsd.org> To: freebsd-virtualization@freebsd.org Subject: Re: bhyve rw access to host filesystem? Message-ID: <aMA-b-ZHH-_aDWa0@amaryllis.le-fay.org> In-Reply-To: <aMA6otBlKSsK-QQM@int21h> References: <aMAjoodDyaJIahJl@int21h> <aMAwFNbSSfKAGh5D@amaryllis.le-fay.org> <aMA6otBlKSsK-QQM@int21h>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] void: > On Tue, Sep 09, 2025 at 02:48:04PM +0100, Lexi Winter wrote: > > 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? either is fine, i showed "rw" as the example since that's what you asked for, but "ro" is also valid. > > 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. yes, that should work fine. [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQSyjTg96lp3RifySyn1nT63mIK/YAUCaMA+bAAKCRD1nT63mIK/ YNDBAP4nQNpWlzZSculOAyW5ViXLTo+8upzavsE9Nx3PaVbCsgEAvxacd2q367Cj OWci9Eqrqjr2r2Z/P1CQDEuzto1SmQ0= =a5ug -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aMA-b-ZHH-_aDWa0>