Date: Sat, 20 Aug 2022 20:51:35 +0100 From: Nuno Teixeira <eduardo@freebsd.org> To: Chuck Tuffli <chuck@tuffli.net> Cc: FreeBSD virtualization <freebsd-virtualization@freebsd.org> Subject: Re: [nvme]: Windows10: inaccessible boot device Message-ID: <CAFDf7UKKNePeRfkQVc4UTW2JJ=hb6201vjr2u-h-wpkZON%2B89A@mail.gmail.com> In-Reply-To: <CAM0tzX1ggWJZrBcmeXsKNfWp3Yi3TAbQMFDMnBV3K%2B%2BaVFXnXA@mail.gmail.com> References: <CAFDf7UKUZjtVJmN8oZkjN3DQKmLoCpkkMOZoZ3UWFUQ3D5f0uQ@mail.gmail.com> <CAM0tzX1ggWJZrBcmeXsKNfWp3Yi3TAbQMFDMnBV3K%2B%2BaVFXnXA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] 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) [-- Attachment #2 --] <div dir="ltr"><div>Hello Chuck!</div><div><br></div><div>`doas vm configure Windows10`:</div><div>---</div><div>loader="uefi"<br>graphics="yes"<br>graphics_res="1920x1080"<br>xhci_mouse="yes"<br>cpu=4<br>memory=4G<br><br># put up to 8 disks on a single ahci controller.<br># without this, adding a disk pushes the following network devices onto higher slot numbers,<br># which causes windows to see them as a new interface<br>ahci_device_limit="8"<br><br># ideally this should be changed to virtio-net and drivers installed in the guest<br># e1000 works out-of-the-box<br>network0_type="virtio-net" # OK<br>#network0_type="e1000" # OK<br>network0_switch="public"<br><br>#disk0_type="nvme" # NOK: INACCESSIBLE BOOT DEVICE<br>#disk0_type="ahci-hd" # OK<br>disk0_type="virtio-blk" # OK<br>#disk0_type="virtio-scsi" # NOK: loader doesn't to see this driver<br>disk0_name="disk0.img"<br><br>#disk1_type="ahci-cd"<br>#disk1_dev="custom"<br>#disk1_name="/work/ISO/virtio-win-0.1.221.iso"<br><br># windows expects the host to expose localtime by default, not UTC<br>utctime="no"<br>uuid="fcabf7ce-bf4b-4a83-be49-46c51ae8610e"<br>network0_mac="58:9c:fc:0b:d1:fa"<br><br># sound<br>#bhyve_options="-s 6,hda,play=/dev/dsp,rec=/dev/dsp" # SAMPLE<br>bhyve_options="-s 1,hda,play=/dev/dsp" # OK, why and how we know what device to use? '-s slot,emulation[,conf]'</div><div>---</div><div><br></div><div>Cheers,<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Chuck Tuffli <<a href="mailto:chuck@tuffli.net">chuck@tuffli.net</a>> escreveu no dia sábado, 20/08/2022 à(s) 18:15:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Fri, Aug 19, 2022 at 12:55 PM Nuno Teixeira <<a href="mailto:eduardo@freebsd.org" target="_blank">eduardo@freebsd.org</a>> wrote:<br> ><br> > Hello,<br> ><br> > 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".<br> ><br> > I've read that nvme was fixed in recent commit.<br> > Do I missing some config params?<br> ><br> > I use vm-bhyve with virtio net and blk drivers atm.<br> <br> What does the vm configuration file contain?<br> <br> --chuck<br> </blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><span style="color:rgb(102,102,102)">Nuno Teixeira<br>FreeBSD Committer (ports)</span></div></div>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFDf7UKKNePeRfkQVc4UTW2JJ=hb6201vjr2u-h-wpkZON%2B89A>