Storage Performance Development Kit (SPDK)
 help / color / mirror / Atom feed
From: Harris, James R <james.r.harris at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] nvme drive not showing in vm in spdk
Date: Mon, 02 Oct 2017 17:42:33 +0000	[thread overview]
Message-ID: <EE06ED56-92EC-474E-B07E-D7BA36DE285B@intel.com> (raw)
In-Reply-To: CAB3_1NtkLR9bmjLzxtZxtYAaQu5CuST23OL16gu8Ctm_quY2-g@mail.gmail.com

[-- Attachment #1: Type: text/plain, Size: 2598 bytes --]

Hi Nitin,

lspci should show you the virtio-scsi controller PCI device.
lsblk –S should show you the SCSI block devices attached to that virtio-scsi controller.

-Jim


From: SPDK <spdk-bounces(a)lists.01.org> on behalf of Nitin Gupta <nitin.gupta981(a)gmail.com>
Reply-To: Storage Performance Development Kit <spdk(a)lists.01.org>
Date: Monday, October 2, 2017 at 10:38 AM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: Re: [SPDK] nvme drive not showing in vm in spdk

Hi Jim

Thanks for your reply and sorry for my late reply ..
could you please  give one example to know how to identify virtio-scsi controller in the linux
i mean which directory it will be present or which file system ?

Regards
Nitin

On Thu, Sep 28, 2017 at 8:30 PM, Harris, James R <james.r.harris(a)intel.com<mailto:james.r.harris(a)intel.com>> wrote:
Hi Nitin,

You should see a virtio-scsi controller in the VM, not an NVMe device.  This controller should have one LUN attached, which SPDK vhost maps to the NVMe device attached to the host.

-Jim


From: SPDK <spdk-bounces(a)lists.01.org<mailto:spdk-bounces(a)lists.01.org>> on behalf of Nitin Gupta <nitin.gupta981(a)gmail.com<mailto:nitin.gupta981(a)gmail.com>>
Reply-To: Storage Performance Development Kit <spdk(a)lists.01.org<mailto:spdk(a)lists.01.org>>
Date: Thursday, September 28, 2017 at 4:07 AM
To: Storage Performance Development Kit <spdk(a)lists.01.org<mailto:spdk(a)lists.01.org>>
Subject: [SPDK] nvme drive not showing in vm in spdk

Hi All

i am new in spdk development and currently doing spdk setup in that  was able to setup back-end storage with NVME .After running the VM with following command , there is no nvme drive present .

/usr/local/bin/qemu-system-x86_64 -m 1024 -object memory-backend-file,id=mem,size=1G,mem-path=/dev/hugepages,share=on -nographic -no-user-config -nodefaults -serial mon:telnet:localhost:7704,server,nowait -monitor mon:telnet:localhost:8804,server,nowait -numa node,memdev=mem -drive file=/home/qemu/qcows,format=qcow2,if=none,id=disk -device ide-hd,drive=disk,bootindex=0 -chardev socket,id=char0,path=./spdk/vhost.0 -device vhost-user-scsi-pci,id=scsi0,chardev=char0 --enable-kvm


how to identify which is nvme drive ?
is there any way to  enable nvme from qemu command ?

PS:  i have already specified the nvme drive in vhost.conf.in<http://vhost.conf.in>

Regards
Nitin

_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org<mailto:SPDK(a)lists.01.org>
https://lists.01.org/mailman/listinfo/spdk


[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 10697 bytes --]

             reply	other threads:[~2017-10-02 17:42 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-02 17:42 Harris, James R [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-10-13  6:02 [SPDK] nvme drive not showing in vm in spdk Nitin Gupta
2017-10-12 16:04 Nitin Gupta
2017-10-12 14:24 Wodkowski, PawelX
2017-10-12 13:57 Nitin Gupta
2017-10-11 12:23 Wodkowski, PawelX
2017-10-11 10:49 Nitin Gupta
2017-10-11  9:52 Wodkowski, PawelX
2017-10-11  9:07 Nitin Gupta
2017-10-07  4:40 Nitin Gupta
2017-10-06 18:31 Harris, James R
2017-10-06  8:28 Nitin Gupta
2017-10-06  3:58 Harris, James R
2017-10-05 10:49 Nitin Gupta
2017-10-04 18:06 Harris, James R
2017-10-04 17:42 Nitin Gupta
2017-10-04 16:43 Harris, James R
2017-10-03  7:23 Nitin Gupta
2017-10-03  6:00 Nitin Gupta
2017-10-03  5:51 Nitin Gupta
2017-10-02 17:38 Nitin Gupta
2017-09-28 15:00 Harris, James R
2017-09-28 11:07 Nitin Gupta

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=EE06ED56-92EC-474E-B07E-D7BA36DE285B@intel.com \
    --to=spdk@lists.01.org \
    /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