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
--0000000000007bf2d205e6b18b22 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello Chuck! `doas vm configure Windows10`: --- loader=3D"uefi" graphics=3D"yes" graphics_res=3D"1920x1080" xhci_mouse=3D"yes" cpu=3D4 memory=3D4G # 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=3D"8" # ideally this should be changed to virtio-net and drivers installed in the guest # e1000 works out-of-the-box network0_type=3D"virtio-net" # OK #network0_type=3D"e1000" # OK network0_switch=3D"public" #disk0_type=3D"nvme" # NOK: INACCESSIBLE BOOT DEVICE #disk0_type=3D"ahci-hd" # OK disk0_type=3D"virtio-blk" # OK #disk0_type=3D"virtio-scsi" # NOK: loader doesn't to see this driver disk0_name=3D"disk0.img" #disk1_type=3D"ahci-cd" #disk1_dev=3D"custom" #disk1_name=3D"/work/ISO/virtio-win-0.1.221.iso" # windows expects the host to expose localtime by default, not UTC utctime=3D"no" uuid=3D"fcabf7ce-bf4b-4a83-be49-46c51ae8610e" network0_mac=3D"58:9c:fc:0b:d1:fa" # sound #bhyve_options=3D"-s 6,hda,play=3D/dev/dsp,rec=3D/dev/dsp" # SAMPLE bhyve_options=3D"-s 1,hda,play=3D/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=C3=A1bado, 20/08/2022 =C3= =A0(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 BOO= T > 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 > --=20 Nuno Teixeira FreeBSD Committer (ports) --0000000000007bf2d205e6b18b22 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>Hello Chuck!</div><div><br></div><div>`doas vm config= ure Windows10`:</div><div>---</div><div>loader=3D"uefi"<br>graphi= cs=3D"yes"<br>graphics_res=3D"1920x1080"<br>xhci_mouse= =3D"yes"<br>cpu=3D4<br>memory=3D4G<br><br># put up to 8 disks on = a single ahci controller.<br># without this, adding a disk pushes the follo= wing network devices onto higher slot numbers,<br># which causes windows to= see them as a new interface<br>ahci_device_limit=3D"8"<br><br># = ideally this should be changed to virtio-net and drivers installed in the g= uest<br># e1000 works out-of-the-box<br>network0_type=3D"virtio-net&qu= ot; # OK<br>#network0_type=3D"e1000" # OK<br>network0_switch=3D&q= uot;public"<br><br>#disk0_type=3D"nvme" # NOK: INACCESSIBLE = BOOT DEVICE<br>#disk0_type=3D"ahci-hd" # OK<br>disk0_type=3D"= ;virtio-blk" # OK<br>#disk0_type=3D"virtio-scsi" # NOK: load= er doesn't to see this driver<br>disk0_name=3D"disk0.img"<br>= <br>#disk1_type=3D"ahci-cd"<br>#disk1_dev=3D"custom"<br= >#disk1_name=3D"/work/ISO/virtio-win-0.1.221.iso"<br><br># window= s expects the host to expose localtime by default, not UTC<br>utctime=3D&qu= ot;no"<br>uuid=3D"fcabf7ce-bf4b-4a83-be49-46c51ae8610e"<br>n= etwork0_mac=3D"58:9c:fc:0b:d1:fa"<br><br># sound<br>#bhyve_option= s=3D"-s 6,hda,play=3D/dev/dsp,rec=3D/dev/dsp" # SAMPLE<br>bhyve_o= ptions=3D"-s 1,hda,play=3D/dev/dsp" # OK, why and how we know wha= t device to use? '-s slot,emulation[,conf]'</div><div>---</div><div= ><br></div><div>Cheers,<br></div></div><br><div class=3D"gmail_quote"><div = dir=3D"ltr" class=3D"gmail_attr">Chuck Tuffli <<a href=3D"mailto:chuck@t= uffli.net">chuck@tuffli.net</a>> escreveu no dia s=C3=A1bado, 20/08/2022= =C3=A0(s) 18:15:<br></div><blockquote class=3D"gmail_quote" style=3D"margi= n: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=3D"mailto:edua= rdo@freebsd.org" target=3D"_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 &quo= t;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=3D"all"><br>-- <br><div dir=3D"ltr" class=3D"g= mail_signature"><div dir=3D"ltr"><span style=3D"color:rgb(102,102,102)">Nun= o Teixeira<br>FreeBSD Committer (ports)</span></div></div> --0000000000007bf2d205e6b18b22--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFDf7UKKNePeRfkQVc4UTW2JJ=hb6201vjr2u-h-wpkZON%2B89A>