I''m not sure if this is a debian thing or if debian is using an older version, but I see this in xend debug log when I try to use vscsi: cat: /sys/bus/scsi/devices/host6/vendor: No such file or directory cat: /sys/bus/scsi/devices/host6/model: No such file or directory cat: /sys/bus/scsi/devices/host6/type: No such file or directory cat: /sys/bus/scsi/devices/host6/rev: No such file or directory cat: /sys/bus/scsi/devices/host6/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/target6:0:3/vendor: No such file or directory cat: /sys/bus/scsi/devices/target6:0:3/model: No such file or directory cat: /sys/bus/scsi/devices/target6:0:3/type: No such file or directory cat: /sys/bus/scsi/devices/target6:0:3/rev: No such file or directory cat: /sys/bus/scsi/devices/target6:0:3/scsi_level: No such file or directory In my case the files it is looking for are actually in /sys/bus/scsi/devices/target6:0:3/0:6:0:3/... Is anyone maintaining vscsi anymore? Thanks James
> > I''m not sure if this is a debian thing or if debian is using an older version, but I > see this in xend debug log when I try to use vscsi: > > cat: /sys/bus/scsi/devices/host6/vendor: No such file or directory > cat: /sys/bus/scsi/devices/host6/model: No such file or directory > cat: /sys/bus/scsi/devices/host6/type: No such file or directory > cat: /sys/bus/scsi/devices/host6/rev: No such file or directory > cat: /sys/bus/scsi/devices/host6/scsi_level: No such file or directory > cat: /sys/bus/scsi/devices/target6:0:3/vendor: No such file or directory > cat: /sys/bus/scsi/devices/target6:0:3/model: No such file or directory > cat: /sys/bus/scsi/devices/target6:0:3/type: No such file or directory > cat: /sys/bus/scsi/devices/target6:0:3/rev: No such file or directory > cat: /sys/bus/scsi/devices/target6:0:3/scsi_level: No such file or directory > > In my case the files it is looking for are actually in > /sys/bus/scsi/devices/target6:0:3/0:6:0:3/... >It seems that this was fixed by installing lsscsi... james
On Fri, Aug 03, 2012 at 05:47:46AM +0000, James Harper wrote:> I''m not sure if this is a debian thing or if debian is using an older version, but I see this in xend debug log when I try to use vscsi: > > cat: /sys/bus/scsi/devices/host6/vendor: No such file or directory > cat: /sys/bus/scsi/devices/host6/model: No such file or directory > cat: /sys/bus/scsi/devices/host6/type: No such file or directory > cat: /sys/bus/scsi/devices/host6/rev: No such file or directory > cat: /sys/bus/scsi/devices/host6/scsi_level: No such file or directory > cat: /sys/bus/scsi/devices/target6:0:3/vendor: No such file or directory > cat: /sys/bus/scsi/devices/target6:0:3/model: No such file or directory > cat: /sys/bus/scsi/devices/target6:0:3/type: No such file or directory > cat: /sys/bus/scsi/devices/target6:0:3/rev: No such file or directory > cat: /sys/bus/scsi/devices/target6:0:3/scsi_level: No such file or directory > > In my case the files it is looking for are actually in /sys/bus/scsi/devices/target6:0:3/0:6:0:3/... > > Is anyone maintaining vscsi anymore? >Konrad put the Xen pvscsi Linux kernel patches to his git tree, but other than that I don''t think anyone is really maintaining pvscsi. Do you want become pvscsi maintainer? :) Someone should upstream the drivers to upstream Linux.. -- Pasi
> > Is anyone maintaining vscsi anymore? > > > > Konrad put the Xen pvscsi Linux kernel patches to his git tree, but other than > that I don''t think anyone is really maintaining pvscsi. > > Do you want become pvscsi maintainer? :) Someone should upstream the > drivers to upstream Linux.. >While I have a need for it I can have a go. One thing I just noticed, /etc/xen/scripts/vscsi is #!/bin/sh when it should be #!/bin/bash (sh != bash under Debian by default). I guess the main thing is that afaik the vscsi stuff isn''t in xl... can anyone estimate the work required to port it? (if it hasn''t been done already) Thanks James
On Sat, 2012-08-04 at 07:35 +0100, James Harper wrote:> I guess the main thing is that afaik the vscsi stuff isn''t in xl... > can anyone estimate the work required to port it? (if it hasn''t been > done already)I''ve not heard of anyone doing it. You''d need to reverse engineer the actual xm/xend syntax and figure out how this translates into xenstore (I suspect this will actually be the hardest bit). Then it''s just a case of writing a parser in xl or libxlu and defining/implementing libxl_device_scsi in libxl. The libxl side is fairly standard and any of the existing devices should provide a reasonable template to follow. Ian.