I have a Sony lib-162 tape library hooked up to an adaptec 39160 scsi controller. I''m running OpenSolaris / Indiana snv_98 with the CADP160 driver installed from a SXCE dvd (snv_99). When I boot without xvm, I can run "mt config" and see the configuration information for the first drive in the library. Under xvm, some scsi operations still work - I can access the changer, move tapes, etc. Howerver, I am unable to see the tape drives. When I run devfsadm -v -i st, I get devfsadm: driver failed to attach: st exit status = 1 modinfo | grep '' st '' show 210 fffffffff86b6000 206e8 129 1 st (SCSI tape Driver) so the module is loaded. Are there any known issues with using tape drives under xvm (from the dom0)? -- This message posted from opensolaris.org
Brian Banister wrote:> I have a Sony lib-162 tape library hooked up to an adaptec 39160 scsi controller. > I''m running OpenSolaris / Indiana snv_98 with the CADP160 driver installed from > a SXCE dvd (snv_99). When I boot without xvm, I can run "mt config" and see the > configuration information for the first drive in the library. Under xvm, some scsi > operations still work - I can access the changer, move tapes, etc. Howerver, I am > unable to see the tape drives. > > When I run devfsadm -v -i st, I get > devfsadm: driver failed to attach: st > exit status = 1 > > modinfo | grep '' st '' show > 210 fffffffff86b6000 206e8 129 1 st (SCSI tape Driver) > so the module is loaded. > > Are there any known issues with using tape drives under xvm (from the dom0)?No, but I believe that driver is installed under i86pc so it''s not loaded in i86xpv. You can cp the capd* drivers and conf file (if there is one) from /platform/i86pc/kernel/drv/[amd64/] to /platform/i86xpv/kernel/drv/[amd64/], do a bootadm update-archive, devfsadm -i <driver-name>, and I believe it will work fine. The is a bug to move this driver to /kernel/drv, but unfortunately, due to the gate that it''s in, it''s not trivial. MRJ
Brian Banister wrote:> On Sun, Nov 02, 2008 at 10:24:31AM -0500, Mark Johnson wrote: > Mark, > > Your advice solved the problem. Now I''m hoping you can give a bit of > insight into why it did. I had already copied the amd64/cadp160 driver > over to the i86xpv side, but had not copied the 32-bit driver (not > needed) or the cadp160.conf file. In the absence of the .conf file, > the scsi system still came up and partially worked (I could talk to > the scsi changer and see hard drives), so I _assumed_ that it must be > finding the .conf from the i86pc side./kernel is the common directory between i86pc and i86xpv. the /platform/i86pc directory will not be looked at when booting into i86xpv. > Can you suggest why st didn''t work but other things did? It the conf file, but not exactly sure why.. You could try removing these one at a time and see which property it is if your interested.. I would guess tape="sctp". flow_control="dmult" queue="qsort" disk="scdk" tape="sctp" MRJ