From mboxrd@z Thu Jan 1 00:00:00 1970 From: Soubir Acharya Subject: Re: XCP PV driver Date: Tue, 01 Feb 2011 09:42:22 -0500 Message-ID: <4D481BCE.8080806@kubisys.com> References: <4D44C47D.6050802@kubisys.com> <291EDFCB1E9E224A99088639C47620228CFFAD7900@LONPMAILBOX01.citrite.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: James Harper Cc: Paul Durrant , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 2/1/2011 8:27 AM, James Harper wrote: >> No, we don't support I_T nexus registration; the model is a simple > non-shared >> SCSI bus. >> > GPLPV tells windows that these SCSIOP's are supported (just returns > STATUS_SUCCESS), but they don't actually do anything. As Paul implies > there is no mechanism to pass such a message back to the actual device > (which could just be a file on disk anyway). It doesn't block anything > else from accessing the device. > > Maybe you could use iSCSI in the DomU instead? >> True, but not as simple as using files out of dom0 as storage. > James > Thanks. There is no reason the XCP driver could not do the same, right? Shared disks would still be "unsupported" but it would just work on a single physical node. I think the configuration is useful to train/demo/play around with Windows configurations requiring shared disks. Oracle RAC, Fail-over clustering to name a few. Even a single node cluster is a valid configuration for learning. Soubir