From: Olaf Hering <olaf@aepfle.de>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH 1 of 3] xend/pvscsi: fix passing of SCSI control LUNs
Date: Fri, 24 Aug 2012 13:17:52 +0200 [thread overview]
Message-ID: <20120824111752.GA14745@aepfle.de> (raw)
In-Reply-To: <1345799722.12501.176.camel@zakaz.uk.xensource.com>
On Fri, Aug 24, Ian Campbell wrote:
> On Thu, 2012-08-23 at 19:24 +0100, Olaf Hering wrote:
> > # HG changeset patch
> > # User Olaf Hering <olaf@aepfle.de>
> > # Date 1345743306 -7200
> > # Node ID 52f3d52bacdecb2c8d7f8aa26e2600febc03b6dd
> > # Parent e6ca45ca03c2e08af3a74b404166527b68fd1218
> > xend/pvscsi: fix passing of SCSI control LUNs
> >
> > Currently pvscsi can not pass SCSI devices that have just a scsi_generic node.
> > In the following example sg3 is a control LUN for the disk sdd.
> > But vscsi=['4:0:2:0,0:0:0:0'] does not work because the internal 'devname'
> > variable remains None. Later writing p-devname to xenstore fails because None
> > is not a valid string variable.
>
> Just out of interest, would you not need to pass through 4:0:2:1 too?
Yes, this is just an example how to pass the control LUN at all.
Olaf
next prev parent reply other threads:[~2012-08-24 11:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 18:24 [PATCH 0 of 3] xend pvscsi fixes Olaf Hering
2012-08-23 18:24 ` [PATCH 1 of 3] xend/pvscsi: fix passing of SCSI control LUNs Olaf Hering
2012-08-24 9:15 ` Ian Campbell
2012-08-24 11:17 ` Olaf Hering [this message]
2012-08-23 18:24 ` [PATCH 2 of 3] xend/pvscsi: fix usage of persistant device names for SCSI devices Olaf Hering
2012-08-24 9:20 ` Ian Campbell
2012-08-23 18:24 ` [PATCH 3 of 3] xend/pvscsi: update sysfs parser for Linux 3.0 Olaf Hering
2012-08-24 9:24 ` Ian Campbell
2012-08-24 11:20 ` Olaf Hering
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=20120824111752.GA14745@aepfle.de \
--to=olaf@aepfle.de \
--cc=Ian.Campbell@citrix.com \
--cc=xen-devel@lists.xen.org \
/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.