I just remembered that in another system works a Samsung SM961 with NVMe 1.2 perfectly. Anybody knows why the intel P4600 doesn´t work? Or better, anybody has a solution that the intel works?
Sunday, December 10, 2017, 1:54:35 AM, you wrote: FM> Hi, FM> are there any news regarding NVMe 1.2 in ESXi-passthrough systems or FM> is there any trick? FM> I can´t see the intel P4600 as a blkdev-device (updated omnios-r151024 FM> on ESXi 6.5). FM> prtconv -v produces this: FM> pci8086,4702, instance #0 (retired) FM> Hardware properties: FM> name='pci-msix-capid-pointer' type=int items=1 FM> value=00000050 FM> name='pci-msi-capid-pointer' type=int items=1 FM> value=000000a0 FM> name='pcie-serial' type=byte items=8 FM> value=fa.1a.23.4e.41.2e.cd.55 FM> name='acpi-namespace' type=string items=1 FM> value='\_SB_.PCI0.PE41.S1F0' FM> name='assigned-addresses' type=int items=5 FM> FM> value=83040010.00000000.fcffc000.00000000.00004000 FM> name='reg' type=int items=10 FM> FM> value=00040000.00000000.00000000.00000000.00000000.03040010.00000000.00000000.00000000.00004000 FM> name='compatible' type=string items=13 FM> value='pciex8086,a54.8086.4702.0' + FM> 'pciex8086,a54.8086.4702' + 'pciex8086,a54.0' + 'pciex8086,a54' + FM> 'pciexclass,010802' + 'pciexclass,0108' + FM> 'pci8086,a54.8086.4702.0' + 'pci8086,a54.8086.4702' + FM> 'pci8086,4702' + 'pci8086,a54.0' + 'pci8086,a54' + FM> 'pciclass,010802' + 'pciclass,0108' FM> name='model' type=string items=1 FM> value='Unknown class of pci/pnpbios device' FM> name='power-consumption' type=int items=2 FM> value=00000001.00000001 FM> name='devsel-speed' type=int items=1 FM> value=00000000 FM> name='interrupts' type=int items=1 FM> value=00000001 FM> name='subsystem-vendor-id' type=int items=1 FM> value=00008086 FM> name='subsystem-id' type=int items=1 FM> value=00004702 FM> name='unit-address' type=string items=1 FM> value='0' FM> name='class-code' type=int items=1 FM> value=00010802 FM> name='revision-id' type=int items=1 FM> value=00000000 FM> name='vendor-id' type=int items=1 FM> value=00008086 FM> name='device-id' type=int items=1 FM> value=00000a54 FM> name='vendor-name' type=string items=1 FM> value='Intel Corporation' FM> name='device-name' type=string items=1 FM> value='unknown device' FM> name='subsystem-name' type=string items=1 FM> value='unknown subsystem' FM> my last try was with /kernel/drv/nvme.conf: FM> # FM> # The driver was tested only against devices supporting v1.0 of the FM> # NVMe specification. Uncomment this to be able to use devices conforming FM> # to newer specifications. FM> strict-version=0; FM> # FM> # The driver does currently not support any vendor specific extension to the FM> # specification. By default it will fault the device if it receives a vendor- FM> # specific command status. Uncomment this to disable this behaviour. FM> ignore-unknown-vendor-status=1; FM> # FM> # The maximum length of the admin queue can be overridden here (16-4096). FM> #admin-queue-len=256; FM> # FM> # The maximum length of the individual I/O queues can be overriden here FM> # (16-65536). FM> #io-queue-len=1024; FM> # FM> # The maximum number of outstanding asynchronous event requests can FM> # overridden here. FM> #async-event-limit=10; FM> # FM> # Enable (1) or Disable (0) the volatile write cache, if present. FM> # FM> #volatile-write-cache-enable=1; FM> # FM> # The minimum physical block size to be reported to blkdev. This value must FM> # be a power of 2 greater than or equal to 512. FM> # FM> #min-phys-block-size=512; FM> Greets FM> Frank FM> ------------------------------------------ FM> illumos-discuss FM> Archives: FM> https://illumos.topicbox.com/groups/discuss/discussions/Tf1abe590f93b6754-M60583c71f2526c469c372026 FM> Powered by Topicbox: https://topicbox.com ------------------------------------------ illumos-discuss Archives: https://illumos.topicbox.com/groups/discuss/discussions/Tf1abe590f93b6754-M69e765271a4f8d8cc0a1e9b5 Powered by Topicbox: https://topicbox.com
