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/
Home Products Support Community News


Re: [Xen-devel] pvscsi broken

To: Jun Kamada <kama@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] pvscsi broken
From: Andrew Lyon <andrew.lyon@xxxxxxxxx>
Date: Tue, 31 Mar 2009 16:08:28 +0100
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, James Harper <james.harper@xxxxxxxxxxxxxxxx>, Masaki Kanno <kanno.masaki@xxxxxxxxxxxxxx>
Delivery-date: Tue, 31 Mar 2009 08:08:59 -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=6obevu2le/HWyPvYPb2SD0UCw1T8hNijvbFwKU/PCFY=; b=ZHPxFCoNgP/1ONw0bdn1NHxLPffz9i4zyhAJX0HTvpMSFaQ87l8UB1ETrO/4BquyE3 cc4islvfrEHkPGL+PGO58mgTVWOJs19wG/FKrGpUwBA2iOKiDdzqbXHlDJ1RulpvwtJo v3H/bQdJS61ckgU3yPGL42RNNcG6TwUPgHeBw=
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=qSFhN30DAV4gjfLe2wyXpJum/OSijcPd8umtWwQKChJMae7T5OZxuit30Bmmi55+Zx F0hjN9BsqqmKjba9UrQ6t3GEPAczopy5Hq55dgqaNOOzAN3TjTrM1NmLUVgLmkQFujM2 R0ifpRuOd8QCpysnxa9MjDqo+PHaoBtcVlkFk=
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".

That does not work:

xm scsi-attach 1 /dev/st0 host = ok

But if I use the syntax you described:         vscsi=['/dev/st0, host]

# xm create 2008_32_snap.cfg
Using config file "./2008_32_snap.cfg".
Error: Errors were found at line 32 while processing ./2008_32_snap.cfg:
        vscsi=['/dev/st0, host]

Or did I misunderstand the syntax?


> 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,
> -----
> Jun Kamada
> kama@xxxxxxxxxxxxxx

Xen-devel mailing list

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