Date: Fri, 08 Feb 2019 12:49:38 +0100 From: mike <mike@reifenberger.com> To: Yuri Pankov <yuripv@yuripv.net>,virtualization@freebsd.org Subject: Re: NVMe and Bhyve Message-ID: <CA5F3504-35DF-4CFB-990A-515BA5F33AAB@reifenberger.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
Hi, yes its a typo but not relevant for the mentioned problem. It just leads to not adding disk2. Disk0 and the nvme get added to bhyve. Only windows is unwilling to use nvme. Greetings ... Mike On February 7, 2019 9:08:53 PM GMT+01:00, Yuri Pankov <yuripv@yuripv.net> wrote: >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? > >> ... >> >> 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?help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA5F3504-35DF-4CFB-990A-515BA5F33AAB>