NVMe and Bhyve

mike mike at reifenberger.com
Fri Feb 8 11:49:44 UTC 2019


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 at 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?


More information about the freebsd-virtualization mailing list