[Xen-users] npiv VS Xen 3.3

[Joe Togell <togell2000@xxxxxxxx>]

Hello all,


I'm doing some testing with Xen and NPIV disk on the platform SLES 10 SP2 and SLES 11 (xen 3.3). On SLES 10 sp2, I have not encountered major problems during the tests (exept with live migration). I was able to attach a disk with the command "xm block-attach npiv:..." an I am also able to start a VM using a bootable NPIV disk.

On sles11, after changing the script block-npiv to work with the new sysfs structure of the he FC qlogic driver on SLES 11, I was able to attached a NPIV disk to a virtual machine without problem. The bootable disk of this VM is on a file device.  The problem is when I try to start a VM from a bootable NPIV disk.  I receive the error "Error: Device 51952 not connected".  I found that the XENBUS_PATH is set to /local/domain/0/backend/vbd/0.  This is not the same when I start a VM (ex.: domain id = 1) that the bootable disk is on a file and I do "xm block-attach npiv:...".  In this case, the XENBUS_PATH used is /local/domain/0/backend/vbd/1.

I think that the disk is not suppose to be attach to the domain 0 but to the new domain.


I am confuse, it is a bug or a miss something ?

Where the variable XENBUS_PATH is set ?


Here is my config file to create the VM:

name="sles11-2"
memory=4096
vcpus=4



localtime=0
builder="linux"
bootloader="/usr/bin/pygrub"
bootargs=""
extra=" "
disk=['npiv:100000051e022b19-2100001b3214face-2000001b3214face-50060e801042c152-7,xvda,w']
vif=[ 'mac=', ]
vfb=['type=vnc,vncunused=1']
loglevel=all



Thank,


joel

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users