On Tue, Jan 19, 2021 at 07:18:16PM +0100, Klaus Jensen wrote: > On Jan 20 02:01, Minwoo Im wrote: > > Run with: > > -device nvme,serial=qux,id=nvme3 > > -device nvme-ns,id=ns3,drive=drv12,nsid=3,bus=nvme3 > > > > -device nvme-subsys,id=subsys0 > > -device nvme,serial=foo,id=nvme0,subsys=subsys0 > > -device nvme,serial=bar,id=nvme1,subsys=subsys0 > > -device nvme,serial=baz,id=nvme2,subsys=subsys0 > > -device nvme-ns,id=ns1,drive=drv10,nsid=1,subsys=subsys0,detached=true > > -device nvme-ns,id=ns2,drive=drv11,nsid=2,bus=nvme2 > > > > nvme-cli: > > root@vm:~/work# nvme list -v > > > > NVM Express Subsystems > > > > > > > > Subsystem Subsystem-NQN > > Controllers > > ---------------- > > ------------------------------------------------------------------------------------------------ > > ---------------- > > nvme-subsys0 nqn.2019-08.org.qemu:qux > > nvme0 > > nvme-subsys1 nqn.2019-08.org.qemu:subsys0 > > nvme1, nvme2, nvme3 > > > > > > NVM Express Controllers > > > > > > > > Device SN MN FR > > TxPort Address Subsystem Namespaces > > -------- -------------------- ---------------------------------------- > > -------- ------ -------------- ------------ ---------------- > > nvme0 qux QEMU NVMe Ctrl > > 1.0 pcie 0000:00:06.0 nvme-subsys0 > > Shouldn't nvme0n1 be listed under Namespaces for nvme0?
Minwoo, try pulling the most current nvme-cli. There was a sysfs scanning bug for non-mpath drives that should be fixed now.
