From: Grant Albitz <GAlbitz@All-Bits.com>
To: Sagi Grimberg <sagi@grimberg.me>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: RE: NVMET Target with esxi 7
Date: Thu, 7 May 2020 16:58:44 +0000 [thread overview]
Message-ID: <b06a4d85bd764d67bf81b9ef2f959bff@All-Bits.com> (raw)
In-Reply-To: <263971f2-dc9e-fc53-06e9-9c3c80ddb8e3@grimberg.me>
Thank you sagi, I am unfamiliar with fused commands and the concept, but I will look into it further. I appreciate the response, I can atleast stop trying for now =)
-----Original Message-----
From: Sagi Grimberg <sagi@grimberg.me>
Sent: Thursday, May 7, 2020 12:20 PM
To: Grant Albitz <GAlbitz@All-Bits.com>; linux-nvme@lists.infradead.org
Subject: Re: NVMET Target with esxi 7
> Hello,
Hey Grant,
> I was trying to configure vmware to connect to nvmet based target. I did not have much luck. VMwares official stance is a very small vendor list. I did see the recent additions such as metadata info. I was curious if anyone developing nvmet was willing/able to test nvmet as a datastore target for vmware to possibly add this functionality. At the moment I am not sure if there are a large number of reasons its not working or a very small check.
The linux nvme target does not support fused commands so there is no support for VMware currently.
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
prev parent reply other threads:[~2020-05-07 16:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 13:47 NVMET Target with esxi 7 Grant Albitz
2020-05-01 14:20 ` Max Gurtovoy
2020-05-01 14:27 ` Grant Albitz
2020-05-05 20:18 ` Grant Albitz
2020-05-07 16:19 ` Sagi Grimberg
2020-05-07 16:58 ` Grant Albitz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b06a4d85bd764d67bf81b9ef2f959bff@All-Bits.com \
--to=galbitz@all-bits.com \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox