Date: Fri, 8 Feb 2019 09:29:55 +0000 From: Matt Churchyard <matt.churchyard@userve.net> To: Yuri Pankov <yuripv@yuripv.net>, Michael Reifenberger <Michael@reifenberger.com>, "virtualization@freebsd.org" <virtualization@freebsd.org> Subject: RE: NVMe and Bhyve Message-ID: <0994a847b82d46999b6f2c5933568a90@SERVER.ad.usd-group.com> In-Reply-To: <5121268a-1ead-9858-86a7-27f75048feb2@yuripv.net> References: <20190207174453.Horde.hWBGfoLlymCpipxLv8WUJo9@app.eeeit.de> <5121268a-1ead-9858-86a7-27f75048feb2@yuripv.net>
index | next in thread | previous in thread | raw e-mail
Michael Reifenberger wrote: > Hi, > first I tried to install windows10 ltsc 2019 onto a nvme disk. > This failed, the windows installer did not find a disk to install. > > Then I tried the following setup: > ... > disk0_type="ahci-hd" > disk0_dev="zvol" > disk0_name="disk0" > disk1_type="nvme" > disk1_dev="zvol" > disk1_name="disk1" > disk1_type="ahci-cd" > disk1_name="disk2.img" >If this is exact copy/paste, shouldn't the 2 lines above use disk2 prefix instead? There's definitely an issue with the configuration file, but vm-bhyve retrieves config settings by looking through the file (which is loaded into a variable) line by line and returning the first match. As such, it will likely be ignoring the ahci-cd & disk2.img settings. Strange why the last disk is a CD and pointing at a .img file though. More useful would be the actual bhyve command from /path/to/guest/vm-bhyve.log, and maybe also confirmation that the zvol path that appears in that command line correctly points to an existing zvol. Matt > ... > > And Installed windows on disk0. > Disk0 is found as expected, disk1 is not. > > The devicemanager reports an error: > https://imgur.com/a/zrHx23y > > Shouldn't nvme be supported in behyve? _______________________________________________ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebsd.org"help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0994a847b82d46999b6f2c5933568a90>