Date: Tue, 03 Jan 2017 16:47:31 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 215740] [bhyve] utilizing passthru breaks raw device usage with virtio-blk | ahci-hd Message-ID: <bug-215740-6@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215740 Bug ID: 215740 Summary: [bhyve] utilizing passthru breaks raw device usage with virtio-blk | ahci-hd Product: Base System Version: 11.0-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: misc Assignee: freebsd-bugs@FreeBSD.org Reporter: bugzilla.freebsd@omnilan.de CC: freebsd-amd64@FreeBSD.org CC: freebsd-amd64@FreeBSD.org Using a passthru device with bhyve(8) for hosting guests with a physical de= vice as storage backend (regardless if accessed through virtio-blk or ahci-hd) corrupts guest-disk access, while file-backed ahci-hd (or virtio-blk) doesn= 't show that problem with passthru. Steps to reproduce: Use any harddrive containing any installed OS. On the host: 'hd /dev/ada6 | less' See MBR/PMBR code. Use the same device (ada6 in that example) and conncet it to a FreeBSD-Live= -DVD guest with a passthru device involved (e. g. bhyveload -d ./releases/ISO-IMAGES/11.0/FreeBSD-11.0-RELEASE-amd64-disc1.is= o -S -m 2G ppttest && bhyve -u -A -H -P -s 0,hostbridge -s 3,ahci,cd:./releases/ISO-IMAGES/11.0/FreeBSD-11.0-RELEASE-amd64-disc1.iso,h= d:/dev/ada6 -s 5,passthru,0/25/0 -s 31,lpc -l com1,stdio -S -m 2G -c 4 ppttest ) Inside the guest, 'hd /dev/ada0 | less' doesn't work anymore (endless I/O) Using 'dd if=3D/dev/ada6 count=3D1 | hd' shows only 0x0 instead of the outp= ut you saw on the host! Simply repeating this without the passthru device in place solves the probl= em, you see exactly the same bytes inside the guest as on the host. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-215740-6>