From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jun Kamada Subject: Re: [PATCH 0/6] pvSCSI (SCSI pass through) driver Date: Mon, 05 Nov 2007 11:05:58 +0900 Message-ID: <20071105105812.031C.KAMA@jp.fujitsu.com> References: <20071030193908.4416.KAMA@jp.fujitsu.com> <1193919281.6422.11.camel@sisko.scot.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1193919281.6422.11.camel@sisko.scot.redhat.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Stephen C. Tweedie" Cc: kama@jp.fujitsu.com, "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org Hi Stephen-san, On Thu, 01 Nov 2007 12:14:41 +0000 "Stephen C. Tweedie" wrote: > On Tue, 2007-10-30 at 19:39 +0900, Jun Kamada wrote: > > Is this using the same syntax for HBA reservation that we used to have, > ie. simply enumerated using the scsi host number on the dom0? Yes. > If so, that is rather fragile. The scsi host number can change from > kernel to kernel depending on HBA driver probe order and PCI bus > enumeration order. It changes when hardware is rearranged. And how do > we deal with migrate, when we'll need to select a completely different > HBA on a different host? > > Selecting the HBA by scsi host number is good enough for a demonstration > that the code works, but I don't think it's going to be robust enough > for production deployment. We also recognize that more sophisticated interface is needed. WWPN can be used for FC-SCSI, however pure SCSI does not have any unique ID. Do you have any idea? > Also, has there been any progress towards exposing individual LUNs to > the guest rather than a whole HBA? > > Cheers, > Stephen > Jun Kamada Linux Technology Development Div. Server Systems Unit Fujitsu Ltd. kama@jp.fujitsu.com