All of lore.kernel.org
 help / color / mirror / Atom feed
From: Soubir Acharya <acharya@kubisys.com>
To: James Harper <james.harper@bendigoit.com.au>
Cc: Paul Durrant <Paul.Durrant@citrix.com>, xen-devel@lists.xensource.com
Subject: Re: XCP PV driver
Date: Tue, 01 Feb 2011 09:42:22 -0500	[thread overview]
Message-ID: <4D481BCE.8080806@kubisys.com> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D01BB946D@trantor>

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

  reply	other threads:[~2011-02-01 14:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-30  1:53 XCP PV driver Soubir Acharya
2011-02-01 13:14 ` Paul Durrant
2011-02-01 13:27   ` James Harper
2011-02-01 14:42     ` Soubir Acharya [this message]
2011-02-01 14:49       ` Paul Durrant
2011-02-01 14:55         ` Soubir Acharya
2011-02-01 17:59     ` Soubir Acharya
2011-02-01 22:21       ` James Harper
2011-02-02  8:34         ` Ian Campbell
2011-02-02  8:41           ` James Harper
2011-02-02 10:03             ` Ian Campbell
2011-02-02  9:51           ` Pasi Kärkkäinen
2011-02-02 10:08             ` Ian Campbell
2011-02-02 10:13               ` Pasi Kärkkäinen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D481BCE.8080806@kubisys.com \
    --to=acharya@kubisys.com \
    --cc=Paul.Durrant@citrix.com \
    --cc=james.harper@bendigoit.com.au \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.