WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] npiv VS Xen 3.3

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] npiv VS Xen 3.3
From: Joe Togell <togell2000@xxxxxxxx>
Date: Fri, 12 Jun 2009 07:24:15 -0700 (PDT)
Delivery-date: Mon, 15 Jun 2009 03:01:57 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.ca; s=s1024; t=1244816656; bh=9StufxM3c3opdnjxnqJSxrHmiVOk98Qe0X2h/BuOm+M=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=dlphTu/b0nDPgCFtVYXbrJW/cvljBfGRidnaG8imQwgy85INx8LCHGlMJbmcbsnKlxtDUIbLVk5oKrA5bBIIW/mR3rVqMmxrqI9PGKdYT/g2MWYJSuj1+1seMViIZVRDH5yOZu2IA+cV6XwFzJGyNU8nZU7qg5dPQRBwYC/fmcg=
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.ca; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=ScbPn3w4XX8RFBoV3zp9vMJud1EQpdBRX685rMLsi47t0xKjbxCRAjhhyQhqHACfsSaJhc7ChPyB7XV3fO0Pox2ohikm2Nq0qvIy2CoKOzCR2sQ+eRsCcPA9aRfQ2o1IigIY9ko8Wxts6FQudP5Op9UUhnhWk7fU6MX/iQ1fdns=;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
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
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] npiv VS Xen 3.3, Joe Togell <=