Date: Sat, 19 Mar 2016 20:52:59 -0700 From: "Russell L. Carter" <rcarter@pinyon.org> To: Paul Vixie <paul@redbarn.org> Cc: freebsd-virtualization@freebsd.org Subject: Re: UFS vs. ZFS inside bhyve hosted on ZFS Message-ID: <56EE1E9B.2050101@pinyon.org> In-Reply-To: <56EE1CC0.9020903@redbarn.org> References: <56ECAFEB.8060305@pinyon.org> <56EE1468.5050503@pinyon.org> <56EE1550.4060403@redbarn.org> <56EE19E9.7040403@pinyon.org> <56EE1CC0.9020903@redbarn.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/19/16 20:45, Paul Vixie wrote: > > > Russell L. Carter wrote: >> >> >> On 03/19/16 20:13, Paul Vixie wrote: >>> >>> >>>> root@vm1:~ # ahcich0: Timeout on slot 29 port 0 >>>> ahcich0: is 00000008 cs 00000000 ss 00000000 rs bfffffff tfd 50 serr >>>> 00000000 cmd 0001dd17 >>>> (ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 40 70 dc 3a 40 00 00 >>>> 00 00 00 00 >>>> (ada0:ahcich0:0:0:0): CAM status: Command timeout >>>> (ada0:ahcich0:0:0:0): Retrying command >>> >>> two questions: >>> >>> why ada rather than vtblk? >> >> No idea. I chose the default UFS selection in the iso installer. >> Happy to change it to something better. > > you're starting your bhyve with a -s that specifies the ahci-hd driver. > the guest kernel therefore sees an 'ahcich0' device. > > if you start bhyve with a -s that specifies the virtio-blk driver, then > your guest kernel will see a 'vtblk' device. > > this may matter, since the kernel timeout you showed was in the ahci > driver. i have never used this driver in bhyve. > Ah! Ok, that makes sense. I have been hacking on the script already so it's going to be a day or so before I report back. I want everything easily reproducible. Thanks, Russell
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56EE1E9B.2050101>