From: Stefan Hajnoczi <stefanha@gmail.com>
To: chandrashekar shastri <cshastri@oc2505588478.ibm.com>
Cc: linux-fsdevel@vger.kernel.org, qemu-devel <qemu-devel@nongnu.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
Hannes Reinecke <hare@suse.de>
Subject: Re: [Qemu-devel] Testing NPIV Feature with Qemu-KVM
Date: Thu, 5 Sep 2013 16:15:58 +0200 [thread overview]
Message-ID: <CAJSP0QUEPjqti5ZuJGZs-9o4yXSQWebVJ1O8HMAbf6iv+9FdGw@mail.gmail.com> (raw)
In-Reply-To: <20130902123444.GA25765@oc2505588478.ibm.com>
On Mon, Sep 2, 2013 at 2:34 PM, chandrashekar shastri
<cshastri@oc2505588478.ibm.com> wrote:
> I am testing NPIV feature on upstream Qemu, I have configured the zone
> and able to see the created vport on the storage array.
>
> Since, I am learning on how to setup the NPIV, I haven't created the different zone for
> the vport and the array, I just added in the existing zone.
>
> Now, how do pass the LUN to the qemu, from Dr. Hannes Reineckei mail thread I got to know that lspci command on the host doesn't show the virtual HBA.
>
> I didn't understand why there is limitation on that and if I specify
> /usr/libexec/qemu-kvm -enable-kvm Fedora19 -m 3000 -smp 2 -net nic -net
> \ user -vnc 127.0.0.1:0 -drive if=scsi,file=/dev/sdj
>
> How do I make sure that qemu is using the virtual HBA or (vport)?
>From my limited knowledge of NPIV, after you create the vport on the
host you'll have a new "SCSI host" which scans LUNs. That means new
SCSI devices appear on the host.
You can use "ls -al /sys/class/scsi_host" to see the SCSI hosts that are active.
You can use "virsh nodedev-list --tree" to see the details of the devices.
This should help you find the NPIV LUNs which can be passed to QEMU.
Stefan
next prev parent reply other threads:[~2013-09-05 14:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-02 12:34 [Qemu-devel] Testing NPIV Feature with Qemu-KVM chandrashekar shastri
2013-09-05 14:15 ` Stefan Hajnoczi [this message]
2013-09-05 14:55 ` Love, Robert W
2013-09-05 14:59 ` Love, Robert W
-- strict thread matches above, loose matches on Subject: below --
2013-09-02 12:54 cshastri
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=CAJSP0QUEPjqti5ZuJGZs-9o4yXSQWebVJ1O8HMAbf6iv+9FdGw@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=cshastri@oc2505588478.ibm.com \
--cc=hare@suse.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).