Summary: | file-backed VMs virtioblock report dev blocksize == underlying ZFS recordsize | ||
---|---|---|---|
Product: | Base System | Reporter: | James Blachly <james.blachly> |
Component: | bhyve | Assignee: | freebsd-virtualization (Nobody) <virtualization> |
Status: | New --- | ||
Severity: | Affects Some People | CC: | allanjude |
Priority: | --- | ||
Version: | 12.1-RELEASE | ||
Hardware: | amd64 | ||
OS: | Any |
Description
James Blachly
2020-01-29 04:11:17 UTC
On the illumos side, Hans Rosenfeld reports that the actual issue is that for file-backed virtio-block devices, bhyve reports the block size is equal to the recordsize of the underlying ZFS system, i.e. 128k in my case. This is larger than ASHIFT_MAX thus pool creation fails. The :lba-access-ok flag is then unrelated but still of note. (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=logical[/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. |