Hi, oh one error i found by myself. there was this npiv: too much in the source. so i attached the disk again via virsh attach-disk pg4 2100001b321fbc18/c0007dc7560d4905/201400a0b829d674/12 hdd --driver phy --subdriver npiv start the guest and get an error and these messages in the log 2009-12-02 15:52:07: domain 27: vbd/768: debug: parameters: action=add domain=27 vdev=768 2009-12-02 15:52:07: domain 27: vbd/768: debug: parameters: device=xdb1 devclass=vbd febe=backend 2009-12-02 15:52:07: domain 27: vbd/768: debug: parameters: vmdev=/vm/314aa42b-9380-a10a-0dc2-fd3e495be172/device/vbd/768 dryrun= 2009-12-02 15:52:07: domain 27: vbd/768: debug: device specific script is /usr/lib/xen/scripts/vbd-event. 2009-12-02 15:52:07: domain 27: vbd/5696: debug: parameters: action=add domain=27 vdev=5696 2009-12-02 15:52:07: domain 27: vbd/5696: debug: parameters: device=xdb2 devclass=vbd febe=backend 2009-12-02 15:52:07: domain 27: vbd/5696: debug: parameters: vmdev=/vm/314aa42b-9380-a10a-0dc2-fd3e495be172/device/vbd/5696 dryrun= 2009-12-02 15:52:07: domain 27: vbd/5696: debug: device specific script is /usr/lib/xen/scripts/vbd-event. 2009-12-02 15:52:07: domain 27: vbd/768: debug: using script /usr/lib/xen/scripts/vbd-default for action add. 2009-12-02 15:52:07: domain 27: vif/0: debug: parameters: action=add domain=27 vdev=0 2009-12-02 15:52:07: domain 27: vif/0: debug: parameters: device=xnbo1 devclass=vif febe=backend 2009-12-02 15:52:07: domain 27: vif/0: debug: parameters: vmdev=/vm/314aa42b-9380-a10a-0dc2-fd3e495be172/device/vif/0 dryrun= 2009-12-02 15:52:07: domain 27: vif/0: debug: device specific script is /usr/lib/xen/scripts/vif-event. 2009-12-02 15:52:07: domain 27: vbd/5696: debug: using script /usr/lib/xen/scripts/vbd-npiv for action add. 2009-12-02 15:52:07: domain 27: vif/0: debug: using script /usr/lib/xen/scripts/vif-vnic for action add. 2009-12-02 15:52:07: domain 27: vif/0: debug: using MAC 00:16:3e:00:03:04. 2009-12-02 15:52:07: domain 27: vif/0: debug: using NIC nge0. 2009-12-02 15:52:07: domain 27: vif/0: debug: vlan id is not set in backend/vif/27/0/vlanid. 2009-12-02 15:52:07: domain 27: vif/0: debug: using VLAN ID 2009-12-02 15:52:07: domain 27: vif/0: debug: no rate limit set in backend/vif/27/0/rate. 2009-12-02 15:52:07: domain 27: vbd/768: debug: hotplug status: connected. 2009-12-02 15:52:07: domain 27: vif/0: debug: using bandwidth Error has occured. HBA_ScsiReportLUNsV2 failed. reason ERROR 2009-12-02 15:52:07: domain 27: vif/0: debug: using VNIC xvm27_0. 2009-12-02 15:52:07: domain 27: vif/0: debug: hotplug status: connected. Error has occured. HBA_ScsiReportLUNsV2 failed. reason ERROR Error has occured. HBA_ScsiReportLUNsV2 failed. reason ERROR Error has occured. HBA_ScsiReportLUNsV2 failed. reason ERROR Error has occured. HBA_ScsiReportLUNsV2 failed. reason ERROR 2009-12-02 15:52:57: domain 27: vbd/5696: error: Unable to create dev for "2100001b321fbc18/c0007dc7560d4905/201400a0b829d674/12". 2009-12-02 15:52:57: domain 27: vbd/5696: debug: hotplug status: error. 2009-12-02 15:53:13: domain 27: vbd/768: debug: parameters: action=remove domain=27 vdev=768 2009-12-02 15:53:13: domain 27: vif/0: debug: parameters: action=remove domain=27 vdev=0 2009-12-02 15:53:13: domain 27: vbd/5696: debug: parameters: action=remove domain=27 vdev=5696 2009-12-02 15:53:13: domain 27: vif/0: debug: parameters: device=xnbo1 devclass=vif febe=backend 2009-12-02 15:53:13: domain 27: vbd/768: debug: parameters: device=xdb1 devclass=vbd febe=backend 2009-12-02 15:53:13: domain 27: vbd/5696: debug: parameters: device=xdb2 devclass=vbd febe=backend 2009-12-02 15:53:13: domain 27: vif/0: debug: parameters: vmdev= dryrun= 2009-12-02 15:53:13: domain 27: vbd/768: debug: parameters: vmdev= dryrun= 2009-12-02 15:53:13: domain 27: vbd/5696: debug: parameters: vmdev= dryrun= 2009-12-02 15:53:13: domain 27: vif/0: debug: device specific script is /usr/lib/xen/scripts/vif-event. 2009-12-02 15:53:13: domain 27: vbd/768: debug: device specific script is /usr/lib/xen/scripts/vbd-event. 2009-12-02 15:53:13: domain 27: vbd/5696: debug: device specific script is /usr/lib/xen/scripts/vbd-event. 2009-12-02 15:53:13: domain 27: vif/0: debug: using script /usr/lib/xen/scripts/vif-vnic for action remove. 2009-12-02 15:53:13: domain 27: vbd/768: debug: using script /usr/lib/xen/scripts/vbd-default for action remove. 2009-12-02 15:53:13: domain 27: vbd/5696: debug: using script /usr/lib/xen/scripts/vbd-npiv for action remove. 2009-12-02 15:53:14: domain 27: vif/0: debug: destroying VNIC xvm27_0.
best regards, uwe 2009/12/2 Uwe Bartels <[email protected]> > > Uwe Bartels > Systemarchitect - Freelancer > mailto: [email protected] > tel: +49 172 3899006 > profile: https://www.xing.com/profile/Uwe_Bartels > > > 2009/12/2 Mark Johnson <[email protected]> > >> >> >> Uwe Bartels wrote: >> >>> Hi, >>> >>> thanks this problen i could fix with the help of a colleague. the missing >>> piece was "devfsadm -Cv" - reconfiguring the new devices. >>> >>> if you have any idea about npiv that would be great. >>> >> >> >> >> There should be error messages in >> /var/log/xen/xpvd-event.log >> >> 2009-12-02 11:30:11: domain 19: vbd/768: debug: parameters: action=add > domain=19 vdev=768 > 2009-12-02 11:30:11: domain 19: vbd/768: debug: parameters: device=xdb0 > devclass=vbd febe=backend > 2009-12-02 11:30:11: domain 19: vbd/768: debug: parameters: > vmdev=/vm/314aa42b-9380-a10a-0dc2-fd3e495be172/device/vbd/768 dryrun= > 2009-12-02 11:30:11: domain 19: vbd/768: debug: device specific script is > /usr/lib/xen/scripts/vbd-event. > 2009-12-02 11:30:11: domain 19: vbd/832: debug: parameters: action=add > domain=19 vdev=832 > 2009-12-02 11:30:11: domain 19: vbd/832: debug: parameters: device=xdb1 > devclass=vbd febe=backend > 2009-12-02 11:30:11: domain 19: vbd/832: debug: parameters: > vmdev=/vm/314aa42b-9380-a10a-0dc2-fd3e495be172/device/vbd/832 dryrun= > 2009-12-02 11:30:11: domain 19: vbd/832: debug: device specific script is > /usr/lib/xen/scripts/vbd-event. > 2009-12-02 11:30:11: domain 19: vbd/768: debug: using script > /usr/lib/xen/scripts/vbd-default for action add. > 2009-12-02 11:30:11: domain 19: vif/0: debug: parameters: action=add > domain=19 vdev=0 > 2009-12-02 11:30:11: domain 19: vif/0: debug: parameters: device=xnbo0 > devclass=vif febe=backend > 2009-12-02 11:30:11: domain 19: vif/0: debug: parameters: > vmdev=/vm/314aa42b-9380-a10a-0dc2-fd3e495be172/device/vif/0 dryrun= > 2009-12-02 11:30:11: domain 19: vif/0: debug: device specific script is > /usr/lib/xen/scripts/vif-event. > 2009-12-02 11:30:11: domain 19: vbd/832: debug: using script > /usr/lib/xen/scripts/vbd-npiv for action add. > 2009-12-02 11:30:11: domain 19: vif/0: debug: using script > /usr/lib/xen/scripts/vif-vnic for action add. > 2009-12-02 11:30:11: domain 19: vif/0: debug: using MAC 00:16:3e:00:03:04. > 2009-12-02 11:30:11: domain 19: vif/0: debug: using NIC nge0. > 2009-12-02 11:30:11: domain 19: vif/0: debug: vlan id is not set in > backend/vif/19/0/vlanid. > 2009-12-02 11:30:11: domain 19: vif/0: debug: using VLAN ID > 2009-12-02 11:30:11: domain 19: vif/0: debug: no rate limit set in > backend/vif/19/0/rate. > 2009-12-02 11:30:11: domain 19: vif/0: debug: using bandwidth > 2009-12-02 11:30:11: domain 19: vbd/768: debug: hotplug status: connected. > 2009-12-02 11:30:12: domain 19: vif/0: debug: using VNIC xvm19_0. > 2009-12-02 11:30:12: domain 19: vif/0: debug: hotplug status: connected. > Error: HBA port npiv:2100001b321fbc18: not found > 2009-12-02 11:30:12: domain 19: vbd/832: error: Unable to create dev for > "npiv:2100001b321fbc18/c0007dc7560d4905/201400a0b829d674/12". > 2009-12-02 11:30:12: domain 19: vbd/832: debug: hotplug status: error. > > I setup the whole chose again, according ti this blog: > http://blogs.sun.com/protoss/entry/nport_id_virtualization but failed > again. > << > virsh attach-disk <domian-name> <npiv:physical port wwn/virtual port > wwn/array port wwn/LUN number> <target> > On Dom0 run > bash-3.2# virsh attach-disk 4632dom > npiv:210000e08b84e3ea/1000000000000020/20030003ba13f3fa/1 5 > >> > > the command was: > virsh attach-disk pg4 > npiv:2100001b321fbc18/c0007dc7560d4905/201400a0b829d674/12 hdb --driver phy > --subdriver npiv > > > this is my configuration after my new configurations of the hba npiv > config. > > global: r...@node1:~ > fcinfo hba-port > HBA Port WWN: 2100001b321fbc18 > Port Mode: Initiator > Port ID: 10700 > OS Device Name: /dev/cfg/c7 > Manufacturer: QLogic Corp. > Model: 375-3355-01 > Firmware Version: 05.01.03 > FCode/BIOS Version: BIOS: 1.24; fcode: 1.24; EFI: 1.08; > Serial Number: 0402R00-0724369194 > Driver Name: qlc > Driver Version: 20090924-2.38 > Type: N-port > State: online > Supported Speeds: 1Gb 2Gb 4Gb > Current Speed: 4Gb > Node WWN: 2000001b321fbc18 > Max NPIV Ports: 127 > NPIV port list: > Virtual Port1: > Node WWN: c0007dc7560d4905 > Port WWN: c0007dc7560d4904 > > HBA Port WWN: 210000e08b947697 > Port Mode: Initiator > Port ID: 10000 > OS Device Name: /dev/cfg/c6 > Manufacturer: QLogic Corp. > Model: 375-3355-01 > Firmware Version: 05.01.03 > FCode/BIOS Version: BIOS: 1.24; fcode: 1.24; EFI: 1.08; > Serial Number: 0402R00-0710356221 > Driver Name: qlc > Driver Version: 20090924-2.38 > Type: N-port > State: online > Supported Speeds: 1Gb 2Gb 4Gb > Current Speed: 4Gb > Node WWN: 200000e08b947697 > Max NPIV Ports: 127 > NPIV port list: > Virtual Port1: > Node WWN: c0007da1558998d9 > Port WWN: c0007da1558998d8 > > i hope this helps. > best regards, > Uwe > > > >> From these, what failed exactly? >> >> >> >> MRJ >> >> >> best regards, >>> Uwe >>> >>> >>> >>> 2009/12/2 Mark Johnson <[email protected] <mailto: >>> [email protected]>> >>> >>> >>> >>> >>> Uwe Bartels wrote: >>> >>> Hi, >>> >>> i'm having problems attaching disks from a fc-san to a solaris >>> 10 guest. >>> xen host ist a opensolaris box "SunOS node1 5.11 snv_127 i86pc >>> i386 i86xpv". >>> >>> my xen guest is named pg4. >>> >>> this command works fine. >>> virsh attach-disk pg4 >>> /dev/dsk/c8t600A0B800029D69A000013CA4B00E1ABd0 hdb >>> >>> >>> Really? You should have to supply p0, i.e. cXtYd0p0 >>> >>> This should work. >>> virsh attach-disk pg4 >>> /dev/dsk/c8t600A0B800029D69A000013CA4B00E1ABd0p0 hdb >>> >>> >>> >>> >>> >>> and before i was able to import this volume as a zpool on the >>> xen host - so connection to this volume looks fine. >>> >>> when i run format i only see the file-based disk: >>> global: r...@pg4:~ > format >>> Searching for disks...done >>> >>> >>> AVAILABLE DISK SELECTIONS: >>> 0. c0d0 <DEFAULT cyl 4092 alt 2 hd 128 sec 32> >>> /p...@0,0/pci-...@1,1/i...@0/c...@0,0 >>> Specify disk (enter its number): ^C >>> zsh: 1777 exit 1 format >>> >>> this is the configuration of the guest: >>> global: r...@node1:~ > virsh dumpxml pg4 >>> <domain type='xen' id='16'> >>> <name>pg4</name> >>> <uuid>314aa42b-9380-a10a-0dc2-fd3e495be172</uuid> >>> <memory>17034240</memory> >>> <currentMemory>17034240</currentMemory> >>> <vcpu>8</vcpu> >>> <os> >>> <type>hvm</type> >>> <loader>/usr/lib/xen/boot/hvmloader</loader> >>> <boot dev='hd'/> >>> </os> >>> <features> >>> <acpi/> >>> <apic/> >>> <pae/> >>> </features> >>> <clock offset='localtime'/> >>> <on_poweroff>destroy</on_poweroff> >>> <on_reboot>restart</on_reboot> >>> <on_crash>restart</on_crash> >>> <distro> >>> <type>solaris</type> >>> <variant>solaris10</variant> >>> </distro> >>> <devices> >>> <emulator>/usr/lib/xen/bin/qemu-dm</emulator> >>> <disk type='block' device='disk'> >>> <driver name='phy'/> >>> <source dev='/dev/zvol/dsk/data/xenimages/pg4'/> >>> <target dev='hda' bus='ide'/> >>> </disk> >>> <disk type='block' device='disk'> >>> <driver name='phy'/> >>> <source >>> dev='/dev/dsk/c8t600A0B800029D69A000013CA4B00E1ABd0'/> >>> <target dev='hdb' bus='ide'/> >>> </disk> >>> <interface type='bridge'> >>> <mac address='00:16:3e:00:03:04'/> >>> <source bridge='nge0'/> >>> <script path='/usr/lib/xen/scripts/vif-vnic'/> >>> <target dev='vif16.0'/> >>> </interface> >>> <serial type='pty'> >>> <source path='/dev/pts/1'/> >>> <target port='0'/> >>> </serial> >>> <console type='pty' tty='/dev/pts/1'> >>> <source path='/dev/pts/1'/> >>> <target port='0'/> >>> </console> >>> <input type='tablet' bus='usb'/> >>> </devices> >>> </domain> >>> >>> in /dev/dsk i also only see this one file based disk. >>> Can you help me with this? >>> >>> >>> >>> >>> The second option i found useful and but bad documented is npiv. >>> I create a virtual port for the 2 fc-hbas in the machine via >>> fcadm create-npiv-port -p 2000000000000001 -n 2100000000000001 >>> 2100001b321fbc18 fcadm create-npiv-port -p 2000000000000002 >>> -n 2100000000000002 210000e08b947697 and the result looks fine: >>> global: r...@node1:~ > fcinfo hba-port >>> HBA Port WWN: 2100001b321fbc18 >>> Port Mode: Initiator >>> Port ID: 10700 >>> OS Device Name: /dev/cfg/c7 >>> Manufacturer: QLogic Corp. >>> Model: 375-3355-01 >>> Firmware Version: 05.01.03 >>> FCode/BIOS Version: BIOS: 1.24; fcode: 1.24; EFI: 1.08; >>> Serial Number: 0402R00-0724369194 >>> Driver Name: qlc >>> Driver Version: 20090924-2.38 >>> Type: N-port >>> State: online >>> Supported Speeds: 1Gb 2Gb 4Gb >>> Current Speed: 4Gb >>> Node WWN: 2000001b321fbc18 >>> Max NPIV Ports: 127 >>> NPIV port list: >>> Virtual Port1: >>> Node WWN: 2100000000000001 >>> Port WWN: 2000000000000001 >>> HBA Port WWN: 210000e08b947697 >>> Port Mode: Initiator >>> Port ID: 10000 >>> OS Device Name: /dev/cfg/c6 >>> Manufacturer: QLogic Corp. >>> Model: 375-3355-01 >>> Firmware Version: 05.01.03 >>> FCode/BIOS Version: BIOS: 1.24; fcode: 1.24; EFI: 1.08; >>> Serial Number: 0402R00-0710356221 >>> Driver Name: qlc >>> Driver Version: 20090924-2.38 >>> Type: N-port >>> State: online >>> Supported Speeds: 1Gb 2Gb 4Gb >>> Current Speed: 4Gb >>> Node WWN: 200000e08b947697 >>> Max NPIV Ports: 127 >>> NPIV port list: >>> Virtual Port1: >>> Node WWN: 2100000000000002 >>> Port WWN: 2000000000000002 >>> >>> >>> Now attaching this to the guest according to >>> >>> http://www.mail-archive.com/[email protected]/msg05181.html >>> fails. >>> virsh attach-disk pg4 >>> /2100001b321fbc18/2000000000000001/3000000000000001/12 hdb >>> --driver phy --subdriver npiv >>> >>> what's wrong? >>> >>> >>> There should be error messages in >>> /var/log/xen/xpvd-event.log >>> >>> >>> From these, what failed exactly? >>> >>> >>> >>> MRJ >>> >>> >>> >
_______________________________________________ xen-discuss mailing list [email protected]
