From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?windows-1252?Q?J=FCrgen_Gro=DF?= Subject: Re: [PATCH v5 3/5] libxl: add support for vscsi Date: Fri, 15 May 2015 06:11:09 +0200 Message-ID: <555571DD.5050702@suse.com> References: <1430918892-20928-1-git-send-email-olaf@aepfle.de> <1430918892-20928-4-git-send-email-olaf@aepfle.de> <1431528246.8263.307.camel@citrix.com> <1431529969.8263.324.camel@citrix.com> <20150513173116.GA24093@aepfle.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20150513173116.GA24093@aepfle.de> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Olaf Hering , Ian Campbell Cc: Wei Liu , Stefano Stabellini , George Dunlap , Ian Jackson , Chunyan Liu , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On 05/13/2015 07:31 PM, Olaf Hering wrote: > On Wed, May 13, Ian Campbell wrote: >> Is it important/useful that the user be able to configure/control the >> number (and addresses) of the buses themselves and which devices are on >> which, or can we get away with the pvpci model where the libxl user just >> gives the individual devices and the library internally takes care of >> what buses need to be created? > > I do not know if its important for users of vscsi to build a bus with > several devices. Giving each device its own bus would work as well, > which would turn the whole thing into ordinary devices from libxl POV. > > No idea where the initial idea came from. Even if the feature-host thing > is used, the raw passthrough of SCSI commands would continue to work. Are you talking about single LUNs or only targets? Multi-LUN devices do exist and they are required to be presented as those to the guest. Juergen