qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] Testing NPIV Feature with Qemu-KVM


From: Love, Robert W
Subject: Re: [Qemu-devel] Testing NPIV Feature with Qemu-KVM
Date: Thu, 5 Sep 2013 14:59:08 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5

On 13-09-05 07:15 AM, Stefan Hajnoczi wrote:
> On Mon, Sep 2, 2013 at 2:34 PM, chandrashekar shastri
> <address@hidden> 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.
>

Also, there will be a /sys/class/fc_host, associated with the scsi_host. 
It will have a port_type, that when read, should show "NPIV VPORT".

//Rob


reply via email to

[Prev in Thread] Current Thread [Next in Thread]