Date: Wed, 29 Jan 2020 04:11:17 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 243692] file-backed VMs do not have LBA flag set in virtio-block Message-ID: <bug-243692-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D243692 Bug ID: 243692 Summary: file-backed VMs do not have LBA flag set in virtio-block Product: Base System Version: 12.1-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: bhyve Assignee: virtualization@FreeBSD.org Reporter: james.blachly@gmail.com Summary: Briefly, file-backed virtio-block devices in bhyve are exposed differently = than zvol backed VMs. This causes ZFS in illumos to segfault when a file-backed virtio-block device is used. In illumos, the only difference in the block devices, as far as I can tell,= is that zvol-backed devices have the ":lba-access-ok" flag set. Possible cause: The virtio block driver has a set of flags that expose supposed capabilitie= s: https://github.com/freebsd/freebsd/blob/0f0a35a04846fc4f4bdb6caa2852336d7de= 9447d/usr.sbin/bhyve/pci_virtio_block.c#L70-L84 However, these differ between file-backed VMs and zvol-backed VMs, possibly here: https://github.com/freebsd/freebsd/blob/0f0a35a04846fc4f4bdb6caa2852336d7de= 9447d/usr.sbin/bhyve/pci_virtio_block.c#L366-L377 (if not specifically there, seems likely in that function, pci_vtblk_init) This manifests in illumos as a segmentation fault when the command `zpool create` is issued on a bhyve-exposed virtio block device that is backed by a file. I also filed an issue with illumos: https://www.illumos.org/issues/12237 Thanks in advance for help. --=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>