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 12:59:45 -0500 [thread overview]
Message-ID: <4D484A11.3000909@kubisys.com> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D01BB946D@trantor>
Is the latest GP PV driver, signed and will it install on 2008 without
requiring "bcdedit driver signing off"?
Soubir
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?
>
> James
>
>> Paul
>>
>>> -----Original Message-----
>>> From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-
>>> bounces@lists.xensource.com] On Behalf Of Soubir Acharya
>>> Sent: 30 January 2011 01:53
>>> To: xen-devel@lists.xensource.com
>>> Subject: [Xen-devel] XCP PV driver
>>>
>>> The XCP PV driver does not like the SCSI Op codes for
>>> RESERVE/RELEASE
>>> and possibly RESET.
>>>
>>> I am trying to install Microsoft Failover Clustering on a HVM with
>>> the
>>> XCP PV drivers installed and disk arbitration is broken.
>>>
>>> Is there a registry setting or otherwise to enable this behavior?
>>>
>>> Or can code be changed to return success if these opcodes are seen
>>> in
>>> the CDB?
>>>
>>> I am fairly certain that this will make clustering work and serve as
>>> a
>>> valuable tool to play with clustered Windows configurations.
>>>
>>> Soubir
>>>
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xensource.com
>>> http://lists.xensource.com/xen-devel
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2011-02-01 17:59 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
2011-02-01 14:49 ` Paul Durrant
2011-02-01 14:55 ` Soubir Acharya
2011-02-01 17:59 ` Soubir Acharya [this message]
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=4D484A11.3000909@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.