* pvscsi broken @ 2009-03-14 12:43 Andrew Lyon 2009-03-14 12:56 ` James Harper 0 siblings, 1 reply; 20+ messages in thread From: Andrew Lyon @ 2009-03-14 12:43 UTC (permalink / raw) To: Xen-devel Hi, On both 3.3.1 and unstable if I try to use pvscsi as per the examples in the config file I get a error when I try to start the domain: xm dry-run xptest.cfg Using config file "./xptest.cfg". /sbin/scsi_id: invalid option -- 's' /sbin/scsi_id comes from udev and I have version 124 installed. This is from xmexample.hvm #----------------------------------------------------------------------------- # Configure PVSCSI devices: # #vscsi=[ 'PDEV, VDEV' ] # # PDEV gives physical SCSI device to be attached to specified guest # domain by one of the following identifier format. # - XX:XX:XX:XX (4-tuples with decimal notation which shows # "host:channel:target:lun") # - /dev/sdxx or sdx # - /dev/stxx or stx # - /dev/sgxx or sgx # - result of 'scsi_id -gu -s'. # ex. # scsi_id -gu -s /block/sdb # 36000b5d0006a0000006a0257004c0000 # # VDEV gives virtual SCSI device by 4-tuples (XX:XX:XX:XX) as # which the specified guest domain recognize. # The command scsi_id -gu -s /block/sdb in the example produces the same error: scsi_id -gu -s /block/sdb scsi_id: invalid option -- 's' I guess the scripts need to be updated for the newer scsi_id & udev. Andy ^ permalink raw reply [flat|nested] 20+ messages in thread
* RE: pvscsi broken 2009-03-14 12:43 pvscsi broken Andrew Lyon @ 2009-03-14 12:56 ` James Harper 2009-03-14 13:15 ` Andrew Lyon 0 siblings, 1 reply; 20+ messages in thread From: James Harper @ 2009-03-14 12:56 UTC (permalink / raw) To: Andrew Lyon, Xen-devel > Hi, > > On both 3.3.1 and unstable if I try to use pvscsi as per the examples > in the config file I get a error when I try to start the domain: > > xm dry-run xptest.cfg > Using config file "./xptest.cfg". > /sbin/scsi_id: invalid option -- 's' > I was sure that I had this working previously, but on my 3.3.1 system it's even worse: xm scsi-attach w2k8test32 /dev/st0 0:0:0:0 sh: /sbin/scsi_id: No such file or directory sh: /sbin/scsi_id: No such file or directory sh: /sbin/scsi_id: No such file or directory sh: /sbin/scsi_id: No such file or directory sh: /sbin/scsi_id: No such file or directory Mine is Debian Lenny, and scsi_id is in /lib/udev, not /sbin, and doesn't seem to support the right options either... James ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: pvscsi broken 2009-03-14 12:56 ` James Harper @ 2009-03-14 13:15 ` Andrew Lyon 2009-03-14 13:19 ` James Harper 0 siblings, 1 reply; 20+ messages in thread From: Andrew Lyon @ 2009-03-14 13:15 UTC (permalink / raw) To: James Harper; +Cc: Xen-devel On Sat, Mar 14, 2009 at 12:56 PM, James Harper <james.harper@bendigoit.com.au> wrote: >> Hi, >> >> On both 3.3.1 and unstable if I try to use pvscsi as per the examples >> in the config file I get a error when I try to start the domain: >> >> xm dry-run xptest.cfg >> Using config file "./xptest.cfg". >> /sbin/scsi_id: invalid option -- 's' >> > > I was sure that I had this working previously, but on my 3.3.1 system > it's even worse: > > xm scsi-attach w2k8test32 /dev/st0 0:0:0:0 > sh: /sbin/scsi_id: No such file or directory > sh: /sbin/scsi_id: No such file or directory > sh: /sbin/scsi_id: No such file or directory > sh: /sbin/scsi_id: No such file or directory > sh: /sbin/scsi_id: No such file or directory > > Mine is Debian Lenny, and scsi_id is in /lib/udev, not /sbin, and > doesn't seem to support the right options either... > > James > scsi_id from udev 114 accepts that syntax but does not output anything at all, I guess its not compatible with the newer udev. ^ permalink raw reply [flat|nested] 20+ messages in thread
* RE: pvscsi broken 2009-03-14 13:15 ` Andrew Lyon @ 2009-03-14 13:19 ` James Harper 2009-03-17 2:00 ` Masaki Kanno 0 siblings, 1 reply; 20+ messages in thread From: James Harper @ 2009-03-14 13:19 UTC (permalink / raw) To: Andrew Lyon; +Cc: Xen-devel > > On Sat, Mar 14, 2009 at 12:56 PM, James Harper > <james.harper@bendigoit.com.au> wrote: > >> Hi, > >> > >> On both 3.3.1 and unstable if I try to use pvscsi as per the examples > >> in the config file I get a error when I try to start the domain: > >> > >> xm dry-run xptest.cfg > >> Using config file "./xptest.cfg". > >> /sbin/scsi_id: invalid option -- 's' > >> > > > > I was sure that I had this working previously, but on my 3.3.1 system > > it's even worse: > > > > xm scsi-attach w2k8test32 /dev/st0 0:0:0:0 > > sh: /sbin/scsi_id: No such file or directory > > sh: /sbin/scsi_id: No such file or directory > > sh: /sbin/scsi_id: No such file or directory > > sh: /sbin/scsi_id: No such file or directory > > sh: /sbin/scsi_id: No such file or directory > > > > Mine is Debian Lenny, and scsi_id is in /lib/udev, not /sbin, and > > doesn't seem to support the right options either... > > > > James > > > > scsi_id from udev 114 accepts that syntax but does not output anything > at all, I guess its not compatible with the newer udev. I can get scsi-attach to work by replacing the call to scsi_id in python/xen/util/vscsi_util.py with: '/lib/udev/scsi_id --whitelisted --replace-whitespace --page=0x80 /dev/' + sg That gives the same output as the previous syntax. Possibly we could omit the --page=0x80 bit, which would instead just give a hex string instead of a vendor_model_serial string. The change is then incompatible with the old version of scsi_id though... James ^ permalink raw reply [flat|nested] 20+ messages in thread
* RE: pvscsi broken 2009-03-14 13:19 ` James Harper @ 2009-03-17 2:00 ` Masaki Kanno 2009-03-23 14:58 ` Andrew Lyon 0 siblings, 1 reply; 20+ messages in thread From: Masaki Kanno @ 2009-03-17 2:00 UTC (permalink / raw) To: James Harper, Andrew Lyon; +Cc: Xen-devel [-- Attachment #1: Mail message body --] [-- Type: text/plain, Size: 1871 bytes --] Hi Andrew and James, I'm not sure about scsi_id and udev. How about these patches? Could you try them? Best regards, Kan Sun, 15 Mar 2009 00:19:18 +1100, "James Harper" wrote: >> >> On Sat, Mar 14, 2009 at 12:56 PM, James Harper >> <james.harper@bendigoit.com.au> wrote: >> >> Hi, >> >> >> >> On both 3.3.1 and unstable if I try to use pvscsi as per the examples >> >> in the config file I get a error when I try to start the domain: >> >> >> >> xm dry-run xptest.cfg >> >> Using config file "./xptest.cfg". >> >> /sbin/scsi_id: invalid option -- 's' >> >> >> > >> > I was sure that I had this working previously, but on my 3.3.1 system >> > it's even worse: >> > >> > xm scsi-attach w2k8test32 /dev/st0 0:0:0:0 >> > sh: /sbin/scsi_id: No such file or directory >> > sh: /sbin/scsi_id: No such file or directory >> > sh: /sbin/scsi_id: No such file or directory >> > sh: /sbin/scsi_id: No such file or directory >> > sh: /sbin/scsi_id: No such file or directory >> > >> > Mine is Debian Lenny, and scsi_id is in /lib/udev, not /sbin, and >> > doesn't seem to support the right options either... >> > >> > James >> > >> >> scsi_id from udev 114 accepts that syntax but does not output anything >> at all, I guess its not compatible with the newer udev. > >I can get scsi-attach to work by replacing the call to scsi_id in python/ >xen/util/vscsi_util.py with: > >'/lib/udev/scsi_id --whitelisted --replace-whitespace --page=0x80 /dev/' + sg > >That gives the same output as the previous syntax. Possibly we could omit >the --page=0x80 bit, which would instead just give a hex string instead of >a vendor_model_serial string. > >The change is then incompatible with the old version of scsi_id though... > >James > >_______________________________________________ >Xen-devel mailing list >Xen-devel@lists.xensource.com >http://lists.xensource.com/xen-devel [-- Attachment #2: scsiid_for_unstable.patch --] [-- Type: application/octet-stream, Size: 1055 bytes --] diff -r 0e1449d6f231 tools/python/xen/util/vscsi_util.py --- a/tools/python/xen/util/vscsi_util.py Fri Mar 13 10:09:25 2009 +0000 +++ b/tools/python/xen/util/vscsi_util.py Tue Mar 17 10:37:07 2009 +0900 @@ -35,6 +35,11 @@ SYSFS_SCSI_DEV_TYPEID_PATH = '/type' SYSFS_SCSI_DEV_TYPEID_PATH = '/type' SYSFS_SCSI_DEV_REVISION_PATH = '/rev' SYSFS_SCSI_DEV_SCSILEVEL_PATH = '/scsi_level' + +SCSI_ID_COMMANDS = [ + "/lib/udev/scsi_id -gu --sg-version 3 -d /dev/%s 2>/dev/null", + "/sbin/scsi_id -gu -s /class/scsi_generic/%s 2>/dev/null" +] def _vscsi_get_devname_by(name, scsi_devices): """A device name is gotten by the HCTL. @@ -79,9 +84,10 @@ def _vscsi_get_hctl_by(phyname, scsi_dev def _vscsi_get_scsiid(sg): - scsi_id = os.popen('/sbin/scsi_id -gu -s /class/scsi_generic/' + sg).read().split() - if len(scsi_id): - return scsi_id[0] + for scsi_id_command in SCSI_ID_COMMANDS: + scsi_id = os.popen(scsi_id_command % sg).read().split() + if len(scsi_id): + return scsi_id[0] return None [-- Attachment #3: scsiid_for_3.3_testing.patch --] [-- Type: application/octet-stream, Size: 1367 bytes --] diff -r 587e81dd3540 tools/python/xen/util/vscsi_util.py --- a/tools/python/xen/util/vscsi_util.py Mon Mar 02 14:19:35 2009 +0000 +++ b/tools/python/xen/util/vscsi_util.py Tue Mar 17 10:51:09 2009 +0900 @@ -26,6 +26,11 @@ import sys import sys import re import string + +SCSI_ID_COMMANDS = [ + "/lib/udev/scsi_id -gu --sg-version 3 -d /dev/%s 2>/dev/null", + "/sbin/scsi_id -gu -s /class/scsi_generic/%s 2>/dev/null" +] def _vscsi_hctl_block(name, scsi_devices): """ block-device name is convert into hctl. (e.g., '/dev/sda', @@ -108,11 +113,12 @@ def vscsi_get_scsidevices(): if re.match('^scsi_generic', f): os.chdir(os.path.join(paths, f)) sg = os.path.basename(os.getcwd()) - lines = os.popen('/sbin/scsi_id -gu -s /class/scsi_generic/' + sg).read().split() - if len(lines) == 0: - scsi_id = '-' - else: - scsi_id = lines[0] + scsi_id = '-' + for scsi_id_command in SCSI_ID_COMMANDS: + lines = os.popen(scsi_id_command % sg).read().split() + if len(lines): + scsi_id = lines[0] + break devices.append([hctl, block, sg, scsi_id]) [-- Attachment #4: Type: text/plain, Size: 138 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: pvscsi broken 2009-03-17 2:00 ` Masaki Kanno @ 2009-03-23 14:58 ` Andrew Lyon 2009-03-25 5:17 ` Masaki Kanno 0 siblings, 1 reply; 20+ messages in thread From: Andrew Lyon @ 2009-03-23 14:58 UTC (permalink / raw) To: Masaki Kanno; +Cc: James Harper, Xen-devel 2009/3/17 Masaki Kanno <kanno.masaki@jp.fujitsu.com>: > Hi Andrew and James, > > I'm not sure about scsi_id and udev. > How about these patches? Could you try them? > > Best regards, > Kan I have tried the patch for unstable and it seems to work, I don't get any errors and xm scsi-list <dom> shows the device is assigned, unfortunately the gplpv driver in windows fails to load but I'm not sure if the problem is the driver or Xen. I will setup a linux domU and try pvscsi with that. Andy ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: pvscsi broken 2009-03-23 14:58 ` Andrew Lyon @ 2009-03-25 5:17 ` Masaki Kanno 2009-03-30 9:24 ` Andrew Lyon 0 siblings, 1 reply; 20+ messages in thread From: Masaki Kanno @ 2009-03-25 5:17 UTC (permalink / raw) To: Andrew Lyon; +Cc: James Harper, Xen-devel Hi Andrew, Thanks for your testing. I'm not sure about the gplpv driver in windows. But I believe that the problem has nothing to do with my patch. Maybe... Best regards, Kan Mon, 23 Mar 2009 14:58:07 +0000, Andrew Lyon wrote: >2009/3/17 Masaki Kanno <kanno.masaki@jp.fujitsu.com>: >> Hi Andrew and James, >> >> I'm not sure about scsi_id and udev. >> How about these patches? Could you try them? >> >> Best regards, >> Kan > > >I have tried the patch for unstable and it seems to work, I don't get >any errors and xm scsi-list <dom> shows the device is assigned, >unfortunately the gplpv driver in windows fails to load but I'm not >sure if the problem is the driver or Xen. > >I will setup a linux domU and try pvscsi with that. > >Andy > >_______________________________________________ >Xen-devel mailing list >Xen-devel@lists.xensource.com >http://lists.xensource.com/xen-devel ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: pvscsi broken 2009-03-25 5:17 ` Masaki Kanno @ 2009-03-30 9:24 ` Andrew Lyon 2009-03-30 9:39 ` Jun Kamada 0 siblings, 1 reply; 20+ messages in thread From: Andrew Lyon @ 2009-03-30 9:24 UTC (permalink / raw) To: Masaki Kanno; +Cc: James Harper, Xen-devel 2009/3/25 Masaki Kanno <kanno.masaki@jp.fujitsu.com>: > Hi Andrew, > > Thanks for your testing. > I'm not sure about the gplpv driver in windows. But I believe that > the problem has nothing to do with my patch. Maybe... > > Best regards, > Kan > > Mon, 23 Mar 2009 14:58:07 +0000, Andrew Lyon wrote: > >>2009/3/17 Masaki Kanno <kanno.masaki@jp.fujitsu.com>: >>> Hi Andrew and James, >>> >>> I'm not sure about scsi_id and udev. >>> How about these patches? (I (BCould you try them? >>> >>> Best regards, >>> (I (BKan >> >> >>I have tried the patch for unstable and it seems to work, I don't get >>any errors and xm scsi-list <dom> shows the device is assigned, >>unfortunately the gplpv driver in windows fails to load but I'm not >>sure if the problem is the driver or Xen. >> >>I will setup a linux domU and try pvscsi with that. >> >>Andy >> >>_______________________________________________ >>Xen-devel mailing list >>Xen-devel@lists.xensource.com >>http://lists.xensource.com/xen-devel > > Hi, I tested pvscsi with a pv domU and had the same problem I did in windows, the scsi device is detected but all tape operations fail and if I run quantum xTalk tape diagnostics it reports a interconnect error: SCSI Interconnect Test Sense: CC: 05 ASC: 20 ASCQ: 00 = "Invalid command operation code The Operation Code in the command was not a valid Operation Code." Andy ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: pvscsi broken 2009-03-30 9:24 ` Andrew Lyon @ 2009-03-30 9:39 ` Jun Kamada 2009-03-30 9:49 ` Andrew Lyon 0 siblings, 1 reply; 20+ messages in thread From: Jun Kamada @ 2009-03-30 9:39 UTC (permalink / raw) To: Andrew Lyon; +Cc: kama, Xen-devel, James Harper, Masaki Kanno 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, On Mon, 30 Mar 2009 10:24:53 +0100 Andrew Lyon <andrew.lyon@gmail.com> wrote: > 2009/3/25 Masaki Kanno <kanno.masaki@jp.fujitsu.com>: > > Hi Andrew, > > > > Thanks for your testing. > > I'm not sure about the gplpv driver in windows. But I believe that > > the problem has nothing to do with my patch. Maybe... > > > > Best regards, > > Kan > > > > Mon, 23 Mar 2009 14:58:07 +0000, Andrew Lyon wrote: > > > >>2009/3/17 Masaki Kanno <kanno.masaki@jp.fujitsu.com>: > >>> Hi Andrew and James, > >>> > >>> I'm not sure about scsi_id and udev. > >>> How about these patches? (I (BCould you try them? > >>> > >>> Best regards, > >>> (I (BKan > >> > >> > >>I have tried the patch for unstable and it seems to work, I don't get > >>any errors and xm scsi-list <dom> shows the device is assigned, > >>unfortunately the gplpv driver in windows fails to load but I'm not > >>sure if the problem is the driver or Xen. > >> > >>I will setup a linux domU and try pvscsi with that. > >> > >>Andy > >> > >>_______________________________________________ > >>Xen-devel mailing list > >>Xen-devel@lists.xensource.com > >>http://lists.xensource.com/xen-devel > > > > > > Hi, > > I tested pvscsi with a pv domU and had the same problem I did in > windows, the scsi device is detected but all tape operations fail and > if I run quantum xTalk tape diagnostics it reports a interconnect > error: > > SCSI Interconnect Test > Sense: CC: 05 ASC: 20 ASCQ: 00 = "Invalid command operation code > The Operation Code in the command was not a valid Operation Code." > > Andy > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel ----- Jun Kamada kama@jp.fujitsu.com ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: pvscsi broken 2009-03-30 9:39 ` Jun Kamada @ 2009-03-30 9:49 ` Andrew Lyon 2009-03-30 10:34 ` Jun Kamada 2009-03-30 10:34 ` Andrew Lyon 0 siblings, 2 replies; 20+ messages in thread From: Andrew Lyon @ 2009-03-30 9:49 UTC (permalink / raw) To: Jun Kamada; +Cc: Xen-devel, James Harper, Masaki Kanno 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? Andy > On Mon, 30 Mar 2009 10:24:53 +0100 > Andrew Lyon <andrew.lyon@gmail.com> wrote: > >> 2009/3/25 Masaki Kanno <kanno.masaki@jp.fujitsu.com>: >> > Hi Andrew, >> > >> > Thanks for your testing. >> > I'm not sure about the gplpv driver in windows. But I believe that >> > the problem has nothing to do with my patch. Maybe... >> > >> > Best regards, >> > Kan >> > >> > Mon, 23 Mar 2009 14:58:07 +0000, Andrew Lyon wrote: >> > >> >>2009/3/17 Masaki Kanno <kanno.masaki@jp.fujitsu.com>: >> >>> Hi Andrew and James, >> >>> >> >>> I'm not sure about scsi_id and udev. >> >>> How about these patches? (I (BCould you try them? >> >>> >> >>> Best regards, >> >>> (I (BKan >> >> >> >> >> >>I have tried the patch for unstable and it seems to work, I don't get >> >>any errors and xm scsi-list <dom> shows the device is assigned, >> >>unfortunately the gplpv driver in windows fails to load but I'm not >> >>sure if the problem is the driver or Xen. >> >> >> >>I will setup a linux domU and try pvscsi with that. >> >> >> >>Andy >> >> >> >>_______________________________________________ >> >>Xen-devel mailing list >> >>Xen-devel@lists.xensource.com >> >>http://lists.xensource.com/xen-devel >> > >> > >> >> Hi, >> >> I tested pvscsi with a pv domU and had the same problem I did in >> windows, the scsi device is detected but all tape operations fail and >> if I run quantum xTalk tape diagnostics it reports a interconnect >> error: >> >> SCSI Interconnect Test >> Sense: CC: 05 ASC: 20 ASCQ: 00 = "Invalid command operation code >> The Operation Code in the command was not a valid Operation Code." >> >> Andy >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel > > > ----- > Jun Kamada > kama@jp.fujitsu.com > > > ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: pvscsi broken 2009-03-30 9:49 ` Andrew Lyon @ 2009-03-30 10:34 ` Jun Kamada 2009-03-30 10:35 ` Andrew Lyon 2009-03-31 15:08 ` Andrew Lyon 2009-03-30 10:34 ` Andrew Lyon 1 sibling, 2 replies; 20+ messages in thread From: Jun Kamada @ 2009-03-30 10:34 UTC (permalink / raw) To: Andrew Lyon; +Cc: kama, Xen-devel, James Harper, Masaki Kanno 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 ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: pvscsi broken 2009-03-30 10:34 ` Jun Kamada @ 2009-03-30 10:35 ` Andrew Lyon 2009-03-31 15:08 ` Andrew Lyon 1 sibling, 0 replies; 20+ messages in thread From: Andrew Lyon @ 2009-03-30 10:35 UTC (permalink / raw) To: Jun Kamada; +Cc: Xen-devel, James Harper, Masaki Kanno On Mon, Mar 30, 2009 at 11:34 AM, Jun Kamada <kama@jp.fujitsu.com> wrote: > 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, I am running unstable, up to date as of 9am GMT today. Andy ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: pvscsi broken 2009-03-30 10:34 ` Jun Kamada 2009-03-30 10:35 ` Andrew Lyon @ 2009-03-31 15:08 ` Andrew Lyon 2009-03-31 20:25 ` James Harper 1 sibling, 1 reply; 20+ messages in thread From: Andrew Lyon @ 2009-03-31 15:08 UTC (permalink / raw) To: Jun Kamada; +Cc: Xen-devel, James Harper, Masaki Kanno On Mon, Mar 30, 2009 at 11:34 AM, Jun Kamada <kama@jp.fujitsu.com> wrote: > 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". 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? Andy > > 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 > > > ^ permalink raw reply [flat|nested] 20+ messages in thread
* RE: pvscsi broken 2009-03-31 15:08 ` Andrew Lyon @ 2009-03-31 20:25 ` James Harper 2009-04-01 8:20 ` Andrew Lyon 0 siblings, 1 reply; 20+ messages in thread From: James Harper @ 2009-03-31 20:25 UTC (permalink / raw) To: Andrew Lyon, Jun Kamada; +Cc: Xen-devel, Masaki Kanno > > 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? > Missing single quote on the end? James ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: pvscsi broken 2009-03-31 20:25 ` James Harper @ 2009-04-01 8:20 ` Andrew Lyon 2009-04-01 8:46 ` James Harper 0 siblings, 1 reply; 20+ messages in thread From: Andrew Lyon @ 2009-04-01 8:20 UTC (permalink / raw) To: James Harper; +Cc: Jun Kamada, Xen-devel, Masaki Kanno On Tue, Mar 31, 2009 at 9:25 PM, James Harper <james.harper@bendigoit.com.au> wrote: >> > 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? >> > > Missing single quote on the end? > > James > Yes but adding a closing quote didnt work either: vscsi=['/dev/st0, host'] Using config file "./xptest.cfg". Error: vscsi syntax error " host" Andy ^ permalink raw reply [flat|nested] 20+ messages in thread
* RE: pvscsi broken 2009-04-01 8:20 ` Andrew Lyon @ 2009-04-01 8:46 ` James Harper 2009-04-01 23:32 ` Jun Kamada 0 siblings, 1 reply; 20+ messages in thread From: James Harper @ 2009-04-01 8:46 UTC (permalink / raw) To: Andrew Lyon; +Cc: Jun Kamada, Xen-devel, Masaki Kanno > > vscsi=['/dev/st0, host'] > > Using config file "./xptest.cfg". > Error: vscsi syntax error " host" > FWIW, same here. James ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: pvscsi broken 2009-04-01 8:46 ` James Harper @ 2009-04-01 23:32 ` Jun Kamada 2009-04-02 7:13 ` Andrew Lyon 0 siblings, 1 reply; 20+ messages in thread From: Jun Kamada @ 2009-04-01 23:32 UTC (permalink / raw) To: James Harper; +Cc: kama, Xen-devel, Andrew Lyon, Masaki Kanno Hi, Please remove space character before keyword "host" like below. vscsi=['/dev/st0,host'] Best regards, On Wed, 1 Apr 2009 19:46:06 +1100 "James Harper" <james.harper@bendigoit.com.au> wrote: > > > > vscsi=['/dev/st0, host'] > > > > Using config file "./xptest.cfg". > > Error: vscsi syntax error " host" > > > > FWIW, same here. > > James ----- Jun Kamada kama@jp.fujitsu.com ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: pvscsi broken 2009-04-01 23:32 ` Jun Kamada @ 2009-04-02 7:13 ` Andrew Lyon 2009-04-02 7:33 ` Masaki Kanno 0 siblings, 1 reply; 20+ messages in thread From: Andrew Lyon @ 2009-04-02 7:13 UTC (permalink / raw) To: Jun Kamada; +Cc: Xen-devel, James Harper, Masaki Kanno On Thu, Apr 2, 2009 at 12:32 AM, Jun Kamada <kama@jp.fujitsu.com> wrote: > Hi, > > Please remove space character before keyword "host" like below. > > vscsi=['/dev/st0,host'] > > Best regards, > That works :), how do I specify multiple devices? i.e. two tape drives. Andy > > On Wed, 1 Apr 2009 19:46:06 +1100 > "James Harper" <james.harper@bendigoit.com.au> wrote: > >> > >> > vscsi=['/dev/st0, host'] >> > >> > Using config file "./xptest.cfg". >> > Error: vscsi syntax error " host" >> > >> >> FWIW, same here. >> >> James > > > ----- > Jun Kamada > kama@jp.fujitsu.com > > > ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: pvscsi broken 2009-04-02 7:13 ` Andrew Lyon @ 2009-04-02 7:33 ` Masaki Kanno 0 siblings, 0 replies; 20+ messages in thread From: Masaki Kanno @ 2009-04-02 7:33 UTC (permalink / raw) To: Andrew Lyon; +Cc: Jun Kamada, James Harper, Xen-devel Hi Andy, It's as follows. vscsi=['/dev/st0,host', '/dev/st1,host'] Best regards, Kan Thu, 2 Apr 2009 08:13:32 +0100, Andrew Lyon wrote: >On Thu, Apr 2, 2009 at 12:32 AM, Jun Kamada <kama@jp.fujitsu.com> wrote: >> Hi, >> >> Please remove space character before keyword "host" like below. >> >> vscsi=['/dev/st0,host'] >> >> Best regards, >> > >That works :), how do I specify multiple devices? i.e. two tape drives. > >Andy > >> >> On Wed, 1 Apr 2009 19:46:06 +1100 >> "James Harper" <james.harper@bendigoit.com.au> wrote: >> >>> > >>> > vscsi=['/dev/st0, host'] >>> > >>> > Using config file "./xptest.cfg". >>> > Error: vscsi syntax error " host" >>> > >>> >>> FWIW, same here. >>> >>> James >> >> >> ----- >> Jun Kamada >> kama@jp.fujitsu.com >> >> >> ^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: pvscsi broken 2009-03-30 9:49 ` Andrew Lyon 2009-03-30 10:34 ` Jun Kamada @ 2009-03-30 10:34 ` Andrew Lyon 1 sibling, 0 replies; 20+ messages in thread From: Andrew Lyon @ 2009-03-30 10:34 UTC (permalink / raw) To: Jun Kamada; +Cc: Xen-devel, James Harper, Masaki Kanno On Mon, Mar 30, 2009 at 10:49 AM, 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? > > Andy Host mode works!, I have tested both a pv linux domain and hvm windows with gplpv drivers loaded, provided I start the domain paused and attach the device before unpausing it and allowing it to boot up, then it seems to work perfectly. :) Andy ^ permalink raw reply [flat|nested] 20+ messages in thread
end of thread, other threads:[~2009-04-02 7:33 UTC | newest] Thread overview: 20+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 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 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
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.