Date: Thu, 16 Jul 2020 16:42:04 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 243692] file-backed VMs virtioblock report dev blocksize == underlying ZFS recordsize Message-ID: <bug-243692-27103-Qvd6PtR10P@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-243692-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-243692-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D243692 Allan Jude <allanjude@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |allanjude@FreeBSD.org --- Comment #2 from Allan Jude <allanjude@FreeBSD.org> --- (In reply to James Blachly from comment #1) When you are configuring the bhyve, when you create the virtio-blk device, = it can take an optional parameter: sectorsize=3Dlogical[/physical] So you can force the block size exposed to be smaller than that reported by= ZFS Possibly, you might want to set the zfs record size to be smaller, since you likely don't want that degree of write amplification in your file-backed VM images anyway. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-243692-27103-Qvd6PtR10P>