Re: [nvme]: Windows10: inaccessible boot device

Hello Chuck!

`doas vm configure Windows10`:
---
loader="uefi"
graphics="yes"
graphics_res="1920x1080"
xhci_mouse="yes"
cpu=4
memory=4G

# put up to 8 disks on a single ahci controller.
# without this, adding a disk pushes the following network devices onto
higher slot numbers,
# which causes windows to see them as a new interface
ahci_device_limit="8"

# ideally this should be changed to virtio-net and drivers installed in the
guest
# e1000 works out-of-the-box
network0_type="virtio-net" # OK
#network0_type="e1000" # OK
network0_switch="public"

#disk0_type="nvme" # NOK: INACCESSIBLE BOOT DEVICE
#disk0_type="ahci-hd" # OK
disk0_type="virtio-blk" # OK
#disk0_type="virtio-scsi" # NOK: loader doesn't to see this driver
disk0_name="disk0.img"

#disk1_type="ahci-cd"
#disk1_dev="custom"
#disk1_name="/work/ISO/virtio-win-0.1.221.iso"

# windows expects the host to expose localtime by default, not UTC
utctime="no"
uuid="fcabf7ce-bf4b-4a83-be49-46c51ae8610e"
network0_mac="58:9c:fc:0b:d1:fa"

# sound
#bhyve_options="-s 6,hda,play=/dev/dsp,rec=/dev/dsp" # SAMPLE
bhyve_options="-s 1,hda,play=/dev/dsp" # OK, why and how we know what
device to use? '-s slot,emulation[,conf]'
---

Cheers,

Chuck Tuffli <chuck@tuffli.net> escreveu no dia sábado, 20/08/2022 à(s)
18:15:

> On Fri, Aug 19, 2022 at 12:55 PM Nuno Teixeira <eduardo@freebsd.org>
> wrote:
> >
> > Hello,
> >
> > I'm running bhyve at main-n257521-97be6fced7db and I'm trying to use
> 'nvme' to access Windows disk but it fails with message "INACCESSIBLE BOOT
> DEVICE".
> >
> > I've read that nvme was fixed in recent commit.
> > Do I missing some config params?
> >
> > I use vm-bhyve with virtio net and blk drivers atm.
>
> What does the vm configuration file contain?
>
> --chuck
>


-- 
Nuno Teixeira
FreeBSD Committer (ports)