WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] pvscsi broken

To: Jun Kamada <kama@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] pvscsi broken
From: Andrew Lyon <andrew.lyon@xxxxxxxxx>
Date: Mon, 30 Mar 2009 11:35:10 +0100
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, James Harper <james.harper@xxxxxxxxxxxxxxxx>, Masaki Kanno <kanno.masaki@xxxxxxxxxxxxxx>
Delivery-date: Mon, 30 Mar 2009 03:36:17 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=JawkVlkoFhQA44pxLogKOh1kiW/iuwZqmEl/3AQR1Hs=; b=JnqPQrwH2Q5YHEgWFlJDVvEXvUEBYpoESD3Gv55HMyHu72Ity6mJOCIVYU6EFHdfQL jsvI26kcqpoUYfCsSz3Uz6sY58V0vyZ+0R81BOFn8rBZSV5ggz5tuV1aVsWfGUBeCf9e 5JHCvy35r3CEwH+poxy3xEf/WEUKYOvbO5Uek=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Ropv+JnbriRHhKlUZDBybDA3TO9iXIWpWll2i2GMViKYvLtn9Xy2UtKIeKttoIMd2u +5d69ngYMBjX1vpRXfZveGF/xPvQZ63laT0CyGG7Zrvd/ESNvjbGKC8K/Kg/4vyz1cBD xMQi4ia2QYEJHod8x37XujAtO8Ab3u3UhEQuM=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20090330192313.0911.EB2C8575@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20090330182845.08F9.EB2C8575@xxxxxxxxxxxxxx> <f4527be0903300249w79743c13v61df092116800b46@xxxxxxxxxxxxxx> <20090330192313.0911.EB2C8575@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Mon, Mar 30, 2009 at 11:34 AM, Jun Kamada <kama@xxxxxxxxxxxxxx> wrote:
> Hi,
>
> On Mon, 30 Mar 2009 10:49:57 +0100
> Andrew Lyon <andrew.lyon@xxxxxxxxx> wrote:
>
>> On Mon, Mar 30, 2009 at 10:39 AM, Jun Kamada <kama@xxxxxxxxxxxxxx> wrote:
>> > Hi Andrew-san,
>> >
>> > Which assignment mode, LUN mode or Host mode, do you use? If you used
>> > the LUN mode, only mandatory SCSI commands can work and almost all
>> > tape related commands will fail.
>> >
>> > Could you try the Host mode? Please see
>> > "http://lists.xensource.com/archives/html/xen-devel/2009-02/msg00505.html";
>> > for usage of the Host mode.
>> >
>> > Best regards,
>> >
>> >
>>
>>
>> I used a config setting like this: #vscsi=['/dev/st0, 0:0:0:0'] which
>> I guess must be LUN mode, I removed the setting and used a "xm attach
>> <dom>  8:0:5:0 host" which was successful and "xm scsi-list" shows the
>> device is attached, but nothing was detected in windows, perhaps it
>> needs to be there as soon as windows is booted, what is the syntax to
>> specify host mode in the config file?
>
> Syntax is as same as in case of "xm scsi-attach". Please replace
> "0:0:0:0" with keyword "host".
>
> BTW, I suppose the problem you are facing is caused by inconsistency
> between backend driver and xend. (The xend support host mode but the
> driver does not support it, maybe.) I reccomend you to use xen unstable
> to avoid such a problem.
>
> Best regards,


I am running unstable, up to date as of 9am GMT today.

Andy

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>