All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jun Kamada <kama@jp.fujitsu.com>
To: Andrew Lyon <andrew.lyon@gmail.com>
Cc: kama@jp.fujitsu.com, Xen-devel <xen-devel@lists.xensource.com>,
	James Harper <james.harper@bendigoit.com.au>,
	Masaki Kanno <kanno.masaki@jp.fujitsu.com>
Subject: Re: pvscsi broken
Date: Mon, 30 Mar 2009 19:34:00 +0900	[thread overview]
Message-ID: <20090330192313.0911.EB2C8575@jp.fujitsu.com> (raw)
In-Reply-To: <f4527be0903300249w79743c13v61df092116800b46@mail.gmail.com>

Hi,

On Mon, 30 Mar 2009 10:49:57 +0100
Andrew Lyon <andrew.lyon@gmail.com> wrote:

> On Mon, Mar 30, 2009 at 10:39 AM, Jun Kamada <kama@jp.fujitsu.com> 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,

-----
Jun Kamada
kama@jp.fujitsu.com

  reply	other threads:[~2009-03-30 10:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-14 12:43 pvscsi broken Andrew Lyon
2009-03-14 12:56 ` James Harper
2009-03-14 13:15   ` Andrew Lyon
2009-03-14 13:19     ` James Harper
2009-03-17  2:00       ` Masaki Kanno
2009-03-23 14:58         ` Andrew Lyon
2009-03-25  5:17           ` Masaki Kanno
2009-03-30  9:24             ` Andrew Lyon
2009-03-30  9:39               ` Jun Kamada
2009-03-30  9:49                 ` Andrew Lyon
2009-03-30 10:34                   ` Jun Kamada [this message]
2009-03-30 10:35                     ` Andrew Lyon
2009-03-31 15:08                     ` Andrew Lyon
2009-03-31 20:25                       ` James Harper
2009-04-01  8:20                         ` Andrew Lyon
2009-04-01  8:46                           ` James Harper
2009-04-01 23:32                             ` Jun Kamada
2009-04-02  7:13                               ` Andrew Lyon
2009-04-02  7:33                                 ` Masaki Kanno
2009-03-30 10:34                   ` Andrew Lyon

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=20090330192313.0911.EB2C8575@jp.fujitsu.com \
    --to=kama@jp.fujitsu.com \
    --cc=andrew.lyon@gmail.com \
    --cc=james.harper@bendigoit.com.au \
    --cc=kanno.masaki@jp.fujitsu.com \
    --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.