Date: Sun, 20 Mar 2022 18:13:36 +0100 From: Mario Marietto <marietto2008@gmail.com> To: Chuck Tuffli <chuck@tuffli.net> Cc: jason@tubnor.net, FreeBSD virtualization <freebsd-virtualization@freebsd.org> Subject: Re: bhyve NVMe 1.4 support Message-ID: <CA%2B1FSihB6w7Gx39TuLmmyJexRiBqn-FJubz9hq0RJ9oucB%2BzGQ@mail.gmail.com> In-Reply-To: <CA%2B1FSijNU7Nn9UZujU%2BCLgJkaYFrbfdu37RT7s_r%2Be08AMG0Pw@mail.gmail.com> References: <CAM0tzX1W1Do=uqA3PONyksY4dmob%2BZMi-ib7aECVx6AH3XW6Pw@mail.gmail.com> <00bf01d80104$e6ba5de0$b42f19a0$@tubnor.net> <CAM0tzX1EdQfTDUMU1dNtQHxG9SB3VzNP5UGmHuiHCY5HsxL2QA@mail.gmail.com> <CAM0tzX1qJOuqJWv_04oMvTqQrmLNQf8O%2B8PJ6cjLyh9bLqRmNQ@mail.gmail.com> <082b01d80697$64e95030$2ebbf090$@tubnor.net> <CA%2B1FSiijy0YjX0Nju9kRAY8hsYc42Y70V3tu-RfqCnaRhzLa8A@mail.gmail.com> <CAM0tzX3SCOS2nOKaODVF2TCTOY_5F5sdqELA666uFRZ=ZreXpg@mail.gmail.com> <CA%2B1FSijNU7Nn9UZujU%2BCLgJkaYFrbfdu37RT7s_r%2Be08AMG0Pw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--00000000000033afdd05daa98201 Content-Type: text/plain; charset="UTF-8" How can I mount the whole disk ? like this ? (on freebsd) : bhyve -S -c sockets=2,cores=2,threads=2 -m 8G -w -H -A \ -s 0,hostbridge \ -s 1,virtio-blk,/mnt/$vmdisk'p2'/bhyve/os/Linux/impish-cuda-11-5-nvidia-495.img \ -s 2,nvme,/dev/nvd0 \ -s 3,passthru,5/0/0 \ -s 4,passthru,1/0/0 \ -s 8,virtio-net,tap0 \ -s 9,virtio-9p,sharename=/ \ -s 29,fbuf,tcp=0.0.0.0:5900,w=1440,h=900 \ -s 30,xhci,tablet \ -s 31,lpc \ -l bootrom,/usr/local/share/uefi-firmware/BHYVE_BHF_CODE.fd \ vm0 < /dev/null & sleep 2 && vncviewer 0:0 On Linux : mario@marietto-BHYVE:/home/marietto# mount -t auto /dev/nvme0n1 /mnt/nvme0n1 mount: /mnt/nvme0n1: wrong fs type, bad option, bad superblock on /dev/nvme0n1, missing codepage or helper program, or other error. does not work. I don't see which partitions there are inside the disk,I'm not able to understand which kind of file system should I mount. Il giorno dom 20 mar 2022 alle ore 16:12 Mario Marietto < marietto2008@gmail.com> ha scritto: > ----> Help me understand what "not recognized" means. The device nvme0n1 : > > I don't see the partitions that are stored inside the disk nvme. And I'm > not able to mount the NTFS partition that's mapped as nvd0p2 under FreeBSD. > > For example : > > bhyve -S -c sockets=2,cores=2,threads=2 -m 8G -w -H -A \ > -s 0,hostbridge \ > -s 1,virtio-blk,/mnt/$vmdisk'p2'/bhyve/os/Linux/impish-cuda-11-5-nvidia-495.img \ > -s 2,nvme,/dev/nvd0p2 \ > -s 3,passthru,5/0/0 \ > -s 4,passthru,1/0/0 \ > -s 8,virtio-net,tap0 \ > -s 9,virtio-9p,sharename=/ \ > -s 29,fbuf,tcp=0.0.0.0:5900,w=1440,h=900 \ > -s 30,xhci,tablet \ > -s 31,lpc \ > -l bootrom,/usr/local/share/uefi-firmware/BHYVE_BHF_CODE.fd \ > vm0 < /dev/null & sleep 2 && vncviewer 0:0 > > root@marietto-BHYVE:/home/marietto# ntfs-3g /dev/nvme0n1 /mnt/nvme > > ntfs_mst_post_read_fixup_warn: magic: 0x00000000 size: 1024 usa_ofs: 0 > usa_count: 0: Argomento not valid > Record 0 has no FILE magic (0x0) > Failed to load $MFT: Errore di input/output > Failed to mount '/dev/nvme0n1': Errore di input/output > NTFS is either inconsistent, or there is a hardware fault, or it's a > SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows > then reboot into Windows twice. The usage of the /f parameter is very > important! If the device is a SoftRAID/FakeRAID then first activate > it and mount a different device under the /dev/mapper/ directory, (e.g. > /dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation > for more details. > > Il giorno dom 20 mar 2022 alle ore 15:30 Chuck Tuffli <chuck@tuffli.net> > ha scritto: > >> On Sun, Mar 20, 2022 at 3:44 AM Mario Marietto <marietto2008@gmail.com> >> wrote: >> ... >> > on the Ubuntu 21.10 guest os : >> > >> > mario@marietto-BHYVE:/home/marietto# fdisk -l >> > >> > Disk /dev/nvme0n1: 931,51 GiB, 1000204886016 bytes, 1953525168 sectors >> > Disk model: bhyve-NVMe >> > Units: sectors of 1 * 512 = 512 bytes >> > Sector size (logical/physical): 512 bytes / 512 bytes >> > I/O size (minimum/optimal): 512 bytes / 512 bytes >> > >> > >> > The nvme disk is not recognized. >> >> Help me understand what "not recognized" means. The device nvme0n1 >> existing in the guest means that the Linux PCI driver found the >> emulated device and the Linux NVMe driver claimed it. The "n1" at the >> end of the device name implies the Linux NVMe driver successfully sent >> a number of Admin commands to the emulated device and discovered the >> Namespace. And the capacity looks correct. >> >> --chuck >> > > > -- > Mario. > -- Mario. --00000000000033afdd05daa98201 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">How can I mount the whole disk ?<br> <br><div> like this ? (on freebsd) :</div><div><br></div> <pre dir=3D"ltr"><code><span class=3D"gmail-im">bhyve -S -c sockets=3D2,cor= es=3D2,threads=3D2 -m 8G -w -H -A \ -s 0,hostbridge \ -s 1,virtio-blk,/mnt/$vmdisk'p2'/bhyve/os/Linux/impish-cuda-11-</sp= an>5-nvidia-495.img \ -s 2,nvme,/dev/nvd0 \ -s 3,passthru,5/0/0 \ -s 4,passthru,1/0/0 \ -s 8,virtio-net,tap0 \ -s 9,virtio-9p,sharename=3D/ \ -s 29,fbuf,tcp=3D<a href=3D"http://0.0.0.0:5900" target=3D"_blank">0.0.0.0:= 5900</a>,w=3D1440,h=3D900 \ -s 30,xhci,tablet \ -s 31,lpc \ -l bootrom,/usr/local/share/uefi-firmware/BHYVE_BHF_CODE.fd \ vm0 < /dev/null & sleep 2 && vncviewer 0:0<br><br></code></p= re><pre><code>On Linux :<br><br></code></pre> =09 =09 <div class=3D"gmail-bbCodeBlock gmail-bbCodeBlock--screenLimited gmail-bbCo= deBlock--code"> <div class=3D"gmail-bbCodeBlock-title"></div> <div class=3D"gmail-bbCodeBlock-content" dir=3D"ltr"> <pre class=3D"gmail-bbCodeCode" dir=3D"ltr"><code>mario@marietto-BHYVE:/h= ome/marietto# mount -t auto /dev/nvme0n1 /mnt/nvme0n1 mount: /mnt/nvme0n1: wrong fs type, bad option, bad superblock on /dev/nvme= 0n1, missing codepage or helper program, or other error.</code></pre> </div> </div><br> does not work. I don't see which partitions there are inside the disk,I'm not able to understand which kind of file system= =20 should I mount.</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class= =3D"gmail_attr">Il giorno dom 20 mar 2022 alle ore 16:12 Mario Marietto <= ;<a href=3D"mailto:marietto2008@gmail.com">marietto2008@gmail.com</a>> h= a scritto:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0= px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div = dir=3D"ltr"><div><span></span> ----> Help me understand what "not recognized" means. The devi= ce nvme0n1 :</div><div><br></div><div>I don't see the partitions that a= re stored inside the disk nvme. And I'm not able to mount the NTFS part= ition that's mapped as nvd0p2 under FreeBSD.<br></div><div><br></div><d= iv>For example :</div><div><br></div><div><pre dir=3D"ltr"><code>bhyve -S -= c sockets=3D2,cores=3D2,threads=3D2 -m 8G -w -H -A \ -s 0,hostbridge \ -s 1,virtio-blk,/mnt/$vmdisk'p2'/bhyve/os/Linux/impish-cuda-11-5-nv= idia-495.img \ -s 2,nvme,/dev/nvd0p2 \ -s 3,passthru,5/0/0 \ -s 4,passthru,1/0/0 \ -s 8,virtio-net,tap0 \ -s 9,virtio-9p,sharename=3D/ \ -s 29,fbuf,tcp=3D<a href=3D"http://0.0.0.0:5900" target=3D"_blank">0.0.0.0:= 5900</a>,w=3D1440,h=3D900 \ -s 30,xhci,tablet \ -s 31,lpc \ -l bootrom,/usr/local/share/uefi-firmware/BHYVE_BHF_CODE.fd \ vm0 < /dev/null & sleep 2 && vncviewer 0:0<br><br></code></p= re></div><div>root@marietto-BHYVE:/home/marietto# ntfs-3g /dev/nvme0n1 /mnt= /nvme</div><div><br></div><div>ntfs_mst_post_read_fixup_warn: magic: 0x0000= 0000 =C2=A0size: 1024 =C2=A0 usa_ofs: 0 =C2=A0usa_count: 0: Argomento not v= alid<br>Record 0 has no FILE magic (0x0)<br>Failed to load $MFT: Errore di = input/output<br>Failed to mount '/dev/nvme0n1': Errore di input/out= put<br>NTFS is either inconsistent, or there is a hardware fault, or it'= ;s a<br>SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Wind= ows<br>then reboot into Windows twice. The usage of the /f parameter is ver= y<br>important! If the device is a SoftRAID/FakeRAID then first activate<br= >it and mount a different device under the /dev/mapper/ directory, (e.g.<br= >/dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentati= on<br>for more details.<br></div></div><br><div class=3D"gmail_quote"><div = dir=3D"ltr" class=3D"gmail_attr">Il giorno dom 20 mar 2022 alle ore 15:30 C= huck Tuffli <<a href=3D"mailto:chuck@tuffli.net" target=3D"_blank">chuck= @tuffli.net</a>> ha scritto:<br></div><blockquote class=3D"gmail_quote" = style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pa= dding-left:1ex">On Sun, Mar 20, 2022 at 3:44 AM Mario Marietto <<a href= =3D"mailto:marietto2008@gmail.com" target=3D"_blank">marietto2008@gmail.com= </a>> wrote:<br> ...<br> > on the Ubuntu 21.10 guest os :<br> ><br> > mario@marietto-BHYVE:/home/marietto# fdisk -l<br> ><br> > Disk /dev/nvme0n1: 931,51 GiB, 1000204886016 bytes, 1953525168 sectors= <br> > Disk model: bhyve-NVMe<br> > Units: sectors of 1 * 512 =3D 512 bytes<br> > Sector size (logical/physical): 512 bytes / 512 bytes<br> > I/O size (minimum/optimal): 512 bytes / 512 bytes<br> ><br> ><br> > The nvme disk is not recognized.<br> <br> Help me understand what "not recognized" means. The device nvme0n= 1<br> existing in the guest means that the Linux PCI driver found the<br> emulated device and the Linux NVMe driver claimed it. The "n1" at= the<br> end of the device name implies the Linux NVMe driver successfully sent<br> a number of Admin commands to the emulated device and discovered the<br> Namespace. And the capacity looks correct.<br> <br> --chuck<br> </blockquote></div><br clear=3D"all"><br>-- <br><div dir=3D"ltr">Mario.<br>= </div> </blockquote></div><br clear=3D"all"><br>-- <br><div dir=3D"ltr" class=3D"g= mail_signature">Mario.<br></div> --00000000000033afdd05daa98201--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2B1FSihB6w7Gx39TuLmmyJexRiBqn-FJubz9hq0RJ9oucB%2BzGQ>