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>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, yes its a typo but not relevant for the mentioned problem=2E It just leads to not adding disk2=2E Disk0 and the nvme get added to bhyve=2E Only windows is unwilling to use nvme=2E Greetings =2E=2E=2E Mike On February 7, 2019 9:08:53 PM GMT+01:00, Yuri Pankov <yuripv@yuripv=2Enet= > wrote: >Michael Reifenberger wrote: >> Hi, >> first I tried to install windows10 ltsc 2019 onto a nvme disk=2E >> This failed, the windows installer did not find a disk to install=2E >>=20 >> Then I tried the following setup: >> =2E=2E=2E >> disk0_type=3D"ahci-hd" >> disk0_dev=3D"zvol" >> disk0_name=3D"disk0" >> disk1_type=3D"nvme" >> disk1_dev=3D"zvol" >> disk1_name=3D"disk1" >> disk1_type=3D"ahci-cd" >> disk1_name=3D"disk2=2Eimg" > >If this is exact copy/paste, shouldn't the 2 lines above use disk2 >prefix instead? > >> =2E=2E=2E >>=20 >> And Installed windows on disk0=2E >> Disk0 is found as expected, disk1 is not=2E >>=20 >> The devicemanager reports an error: >> https://imgur=2Ecom/a/zrHx23y >>=20 >> Shouldn't nvme be supported in behyve?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA5F3504-35DF-4CFB-990A-515BA5F33AAB>