Hi
There exists a Windows driver for NMVe devices (http://www.nvmexpress.org/resources/). The source code is vailable here (http://www.openfabrics.org/svnrepo/nvmewin/trunk/source/). I have a few question considering how to make the NVMe device available to guests running upon the Hyper-V.
I will start from simple to hard:
Q1: Is is possible to use in Hyper-V drivers developed for Windows without any changes?
Q2: In case the answer to Q1 is positive, does VSP transparently maps the hardware to the VSC or not? In case of transparent mapping how should I see the underling nvme device (as a scsi one or nvme). The http://www.openfabrics.org/svnrepo/nvmewin/trunk/source/nvme.inf contains
Class=SCSIAdapter
…
LoadOrderGroup = SCSI miniport
AddReg = pnpsafe_pci_addreg
AddReg = Parameters
Q3: In case I’m using a guest operating systems that support Enlightened I/O, can I relay that the advantage of VMBus will be directly taken?
Q4: NVMe devices are supporting several so called namespaces. One can treate them as a separate storage devices (like LUNs).Now the question is twofold. If Hyper-V maps up the underling NVMe device as a scsi device, is it reasonable to assume that the namespaces managements (aka LUNs) is done via Hyper-V configuration CLI or Microsoft Management Console just like SCSI LUNs. If Hyper-V doesn’t maps the NVME device as a scsi, can the configuration CLI be extended to support namespace configuration?
Thanks
David