Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 13 Dec 2018 05:33:17 -0800
From:      Chuck Tuffli <chuck@freebsd.org>
To:        yuripv@yuripv.net
Cc:        freebsd-current@freebsd.org
Subject:   Re: nda(4) does not work (reliably) in VMware Workstation
Message-ID:  <CAKAYmMLQpnb0w7YS9KRDgssh8rrZjJCG02hZGb7NeP3Yr55AiA@mail.gmail.com>
In-Reply-To: <CAKAYmM%2Bg9Hd2wy_qizFGPEKyqYUyseXFY5jmPbxydHq6aiYK=w@mail.gmail.com>
References:  <015e28d3-3c6f-b5f3-b41a-5f6d367dddbb@yuripv.net> <CAKAYmM%2BRqymn0DXD6O43GFGMMsh790gDT95c3oQX43iaYFXVBA@mail.gmail.com> <9db60b9c-fea0-c5d6-5f8f-eae051c3f92d@yuripv.net> <CAKAYmM%2Bg9Hd2wy_qizFGPEKyqYUyseXFY5jmPbxydHq6aiYK=w@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Dec 9, 2018 at 3:50 PM Chuck Tuffli <chuck@freebsd.org> wrote:

> On Sun, Dec 9, 2018 at 3:43 PM Yuri Pankov <yuripv@yuripv.net> wrote:
>
>> Chuck Tuffli wrote:
>> > On Sat, Dec 8, 2018 at 12:28 PM Yuri Pankov <yuripv@yuripv.net
>> > <mailto:yuripv@yuripv.net>> wrote:
>> >
>> >     Hi,
>> >
>> >     Running -HEAD in VMware Workstation 15.0.2 VM.  Trying to use nda(4)
>> >     instead of nvd(4) shows the following list of errors, and eventually
>> >     panics:
>> >
>> >     https://people.freebsd.org/~yuripv/nda1.png
>> >     https://people.freebsd.org/~yuripv/nda2.png
>> >
>> >     nvd(4) works without issues in this VM.  nda(4) works as well in
>> VMware
>> >     ESXi VMs.  Is this a problem with WS NVMe emulation?
>> >
>> >
>> > Since I don't have access to ESXi, the attached is a speculative fix. If
>> > 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
>>
>
> OK, that makes sense given the error message and the patch working. I'll
> get this cleaned up and committed. Thanks for the report!
>

Committed r342046 to address this

--chuck



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKAYmMLQpnb0w7YS9KRDgssh8rrZjJCG02hZGb7NeP3Yr55AiA>