On 8/26/08, Jun Kamada <kama@xxxxxxxxxxxxxx> wrote:
> Hi,
>
> The ptaches you are using are very old, so I can't remember detail about
> them. Only I can say is:
>
> - "Attach" operation is needed in order to attach specfied HBA to
> guest domain. (To do so, some information should be wriiten to
> xenstore. However, these patches did not contain tool to do it,
> meybe, because the patches were just for RFC.)
> - After that operation, you can see SCSI disks under the HBA as
> /dev/sd?? on the guest domain.
> - If you can successfully see the disks, you can see any information
> about FC transport layer at /sys/class/*.
after using PCI-PASSTHROUG FC-HBA is visible in the domU.
1.
-----------
domU output:
root@guest03:~# lspci
01:05.0 Fibre Channel: QLogic Corp. ISP2312-based 2Gb Fibre Channel to
PCI-X HBA (rev 02)
2.
------
root@guest03:~# cat /proc/scsi/scsi
Attached devices:
proc/scsi does not show any output.
3. Dmesg for qlogic while booting domU.
qla2xxx 0000:01:05.0: Found an ISP2312, irq 18, iobase 0xc903c000
qla2xxx 0000:01:05.0: Configuring PCI space...
qla2xxx 0000:01:05.0: Configure NVRAM parameters...
qla2xxx 0000:01:05.0: Verifying loaded RISC code...
qla2xxx 0000:01:05.0: Firmware image unavailable.
qla2xxx 0000:01:05.0: Firmware images can be retrieved from:
ftp://ftp.qlogic.com/outgoing/linux/firmware/.
qla2x00_initialize_adapter(): **** FAILED ****
qla2xxx 0000:01:05.0: Failed to initialize adapter
it is complaining about some Firmware image unavailable
4.
--------
/sys/class/fc_host shows nothing
root@guest03:/sys/class# ls -l /sys/class/fc_host/
total 0
root@guest03:/sys/class#
Now how do i access these scsi device in domU using pci passthrough.
Any pointers will be approciated.
thanks
-tej
>
> Best regards,
>
>
> On Tue, 26 Aug 2008 09:09:05 +0530
> Tej <bewith.tej@xxxxxxxxx> wrote:
>
>> On Tue, Aug 26, 2008 at 6:29 AM, Jun Kamada <kama@xxxxxxxxxxxxxx> wrote:
>> > Hi Tej-san Mark-san and all,
>> >
>> > Unfortunately, the pvSCSI driver for Xen 3.3 does not support FC
>> > transport layer functionality. I consider that at least new export
>> > mode, which exports whole physical SCSI tree under a HBA to guest
>> > domain, is needed. (FC transport functionality assumes physical
>> > topology, I think.)
>> Actually i am still at compilation and building stage of xen 3.3 and
>> will get back on this.
>> Currently we are using the patches indicated in my previous post. i
>> could get the following.
>> 1. I am able to access and see all the disk on SAN in dom0 i.e. cat
>> /proc/scsi/scsi list all the disk.
>> 2. domU could not able to see that FC HBA driver itself, i will try
>> with directly assigning the PCI device to domU (HTH)
>> Front-back arch. could not be the culprit because this arch. is
>> applicable to dom0 also.
>>
>> so what i am missing?
>>
>> thanks
>> -tej
>> >
>> > Best regards,
>> >
>> >
>> > On Sun, 24 Aug 2008 09:07:25 +0530
>> > Tej <bewith.tej@xxxxxxxxx> wrote:
>> >
>> >> On Sun, Aug 24, 2008 at 6:53 AM, Mark Williamson
>> >> <mark.williamson@xxxxxxxxxxxx> wrote:
>> >> > Actually, the PVSCSI *was* mentioned in the 3.3 release announcement
>> >> > so I
>> >> > think you should find it there...
>> >>
>> >> yaa i was looking at 3.3 release notes, but i couldn't relate PVSCSCI
>> >> to it
>> >> thanks for this pointers
>> >>
>> >> >
>> >> > The header file seems not to have made its way into
>> >> > xen/include/public/io/
>> >> > along with the other front/back interface definitions. It is in the
>> >> > XenLinux
>> >> > copy of that directory, though, which I hadn't checked.
>> >> >
>> >> > 3.3 is probably worth looking at, then ;-)
>> >> >
>> >> > Cheers,
>> >> > Mark
>> >> >
>> >> > On Saturday 23 August 2008, Tej wrote:
>> >> >> On Thu, Aug 21, 2008 at 5:16 AM, Mark Williamson
>> >> >>
>> >> >> <mark.williamson@xxxxxxxxxxxx> wrote:
>> >> >> > On Wednesday 20 August 2008, Tej wrote:
>> >> >> >> Hi All
>> >> >> >>
>> >> >> >> As i was referring to the following link
>> >> >> >> http://lists.xensource.com/archives/html/xen-devel/2007-06/msg00996.html
>> >> >> >>
>> >> >> >> but i can't see this work in official xen 3.2.
>> >> >> >> Is it still in review?
>> >> >> >
>> >> >> > I think I've seen activing reviewing of this patch set fairly
>> >> >> > recently so
>> >> >> > presumably it's still being worked on. It doesn't look like it's
>> >> >> > made it
>> >> >> > into 3.3, so I guess 3.4 would be the soonest we'd expect it...
>> >> >> >
>> >> >> >> Or can i use the same patches to perform some NPIV task.
>> >> >> >
>> >> >> > If you're willing to try experimental software you could probably
>> >> >> > patch
>> >> >> > the code yourself - you might need to be prepared to do some
>> >> >> > merging in
>> >> >> > places if the Xen tree has diverged from the state that the
>> >> >> > patches
>> >> >> > expect...
>> >> >> >
>> >> >> > You should try to make sure you have the most recent patches
>> >> >> > possible -
>> >> >> > I'm sure they've been updated several times since the mailing list
>> >> >> > post
>> >> >> > that you found.
>> >> >>
>> >> >> thanks, i will go ahead with the solution.
>> >> >>
>> >> >> > Cheers,
>> >> >> > Mark
>> >> >> >
>> >> >> >> thanks in advance for any help
>> >> >> >>
>> >> >> >> -TEJ
>> >> >> >
>> >> >> > --
>> >> >> > Push Me Pull You - Distributed SCM tool
>> >> >> > (http://www.cl.cam.ac.uk/~maw48/pmpu/)
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Push Me Pull You - Distributed SCM tool
>> >> > (http://www.cl.cam.ac.uk/~maw48/pmpu/)
>> >> >
>> >>
>> >> _______________________________________________
>> >> Xen-devel mailing list
>> >> Xen-devel@xxxxxxxxxxxxxxxxxxx
>> >> http://lists.xensource.com/xen-devel
>> >
>> >
>> > -----
>> > Jun Kamada
>> >
>> >
>> >
>
>
> -----
> Jun Kamada
>
>
>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|