Date: Mon, 10 Dec 2018 02:43:29 +0300 From: Yuri Pankov <yuripv@yuripv.net> To: Chuck Tuffli <chuck@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: nda(4) does not work (reliably) in VMware Workstation Message-ID: <9db60b9c-fea0-c5d6-5f8f-eae051c3f92d@yuripv.net> In-Reply-To: <CAKAYmM%2BRqymn0DXD6O43GFGMMsh790gDT95c3oQX43iaYFXVBA@mail.gmail.com> References: <015e28d3-3c6f-b5f3-b41a-5f6d367dddbb@yuripv.net> <CAKAYmM%2BRqymn0DXD6O43GFGMMsh790gDT95c3oQX43iaYFXVBA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --gB9GFwrQqFwzb7gXBqWat0i0I6QmFzSXs Content-Type: multipart/mixed; boundary="nB0WzigCvQmac8WhkUckxehP6lPhOCzsB"; protected-headers="v1" From: Yuri Pankov <yuripv@yuripv.net> To: Chuck Tuffli <chuck@freebsd.org> Cc: freebsd-current@freebsd.org Message-ID: <9db60b9c-fea0-c5d6-5f8f-eae051c3f92d@yuripv.net> Subject: Re: nda(4) does not work (reliably) in VMware Workstation References: <015e28d3-3c6f-b5f3-b41a-5f6d367dddbb@yuripv.net> <CAKAYmM+Rqymn0DXD6O43GFGMMsh790gDT95c3oQX43iaYFXVBA@mail.gmail.com> In-Reply-To: <CAKAYmM+Rqymn0DXD6O43GFGMMsh790gDT95c3oQX43iaYFXVBA@mail.gmail.com> --nB0WzigCvQmac8WhkUckxehP6lPhOCzsB Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Chuck Tuffli wrote: > On Sat, Dec 8, 2018 at 12:28 PM Yuri Pankov <yuripv@yuripv.net > <mailto:yuripv@yuripv.net>> wrote: >=20 > Hi, >=20 > Running -HEAD in VMware Workstation 15.0.2 VM.=C2=A0 Trying to use = nda(4) > instead of nvd(4) shows the following list of errors, and eventuall= y > panics: >=20 > https://people.freebsd.org/~yuripv/nda1.png > https://people.freebsd.org/~yuripv/nda2.png >=20 > nvd(4) works without issues in this VM.=C2=A0 nda(4) works as well = in VMware > ESXi VMs.=C2=A0 Is this a problem with WS NVMe emulation? >=20 >=20 > Since I don't have access to ESXi, the attached is a speculative fix. I= f > it works, I'll clean this up a bit and get it committed. If not, please= > post the output from: > nvmecontrol identtify nvme0 Thank you, it seems to help (was seeing the issue previously immediately after boot). BTW, the ESXi VM works fine with nda, it's only the Workstation that had the problem. Comparing `nvmecontrol identify` output from both, the only difference is (first is WS, second is ESXi): -Dataset Management Command: Not Supported +Dataset Management Command: Supported --nB0WzigCvQmac8WhkUckxehP6lPhOCzsB-- --gB9GFwrQqFwzb7gXBqWat0i0I6QmFzSXs Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEE+Gq3PsPeLT4tL/9wk4vgf7Eq4WwFAlwNqKcACgkQk4vgf7Eq 4WxUmAf/YmfErv8eoZQtlpu8lxQgA+OiHGVgK4Q6hSRipAX0/+pQxmET8LgSCHTu 7itx3JvIPYqPj7hRql0k+tM7W4UwK+/VYbv39iEVEKM7PYAreOaB2I/TvSCVi+PY u+XHvdbWKqR3RrW0NIsP298/3cm9HjhoN9E5yfoBY2AHsjf65fIUl7mTisi+VmdC YUFJYf+Ym/L/yHL5Ay8ArE8C4C+9laWbHnmL7g+81q+59b7KqOdWzOrUIGGoiyjb 7TCTCyNZz7Uk48SHbsLXlLaNePxXhyLTemMPEPVIcMSXCWGcYkk8QTfI7ZkBTW7v JYyCME4D1HOeClK5byREEWIUv7BRwQ== =KGiW -----END PGP SIGNATURE----- --gB9GFwrQqFwzb7gXBqWat0i0I6QmFzSXs--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9db60b9c-fea0-c5d6-5f8f-eae051c3f92d>