search for: sg0

Greetings, I was wondering what is the proper way to configure a scsi cdrom pass-through so in when the qemu line is generated, host_Cdrom will be used instead of host_device. looking at https://gitlab.com/libvirt/libvirt/-/blob/master/src/qemu/qemu_block.c#L1090, I see that hostcdrom must be true. in order for that to be true, the following must be (see

I have a third party application that I want to run a CentOS4 box that is expecting to access the generic SCSI devices through /dev/sga, /dev/sgb, etc. However, the devices set up by udev are /dev/sg0, /dev/sg1 etc. Does anyone know what syntax I could use to create a udev rule that creates symlinks sga -> sg0 etc. for each sg[0-N] device? Thanks James Pearson

...ied --cdrom, just forgot to include in original post; While searching google, I saw a post where --block --short included cdrom output. [root at darkness ~]# ls -al /dev/sr* ls: cannot access /dev/sr*: No such file or directory [root at darkness ~]# ls /dev/s* /dev/sda /dev/sda3 /dev/sdb1 /dev/sg0 /dev/stderr /dev/sda1 /dev/sda4 /dev/sdb2 /dev/sg1 /dev/stdin /dev/sda2 /dev/sdb /dev/sdb3 /dev/snapshot /dev/stdout [root at darkness ~]# hwinfo --cdrom [root at darkness ~]# thanks ~d

...doesn't show it? usb-storage: device found at 5 usb-storage: waiting for device to settle before scanning Vendor: Model: Rev: Type: Direct-Access ANSI SCSI revision: 02 sd 7:0:0:0: Attached scsi disk sda sd 7:0:0:0: Attached scsi generic sg0 type 0 usb-storage: device scan complete usb 1-4: USB disconnect, address 5 usb 1-4: new high speed USB device using ehci_hcd and address 6 usb 1-4: configuration #1 chosen from 1 choice scsi8 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 6 usb-storage: waiting for devi...

...e the 'host_device' protocol backend. The main difference is that for the emulation interface (<disk>) we use the block interface for the cdrom (/dev/sr0 for example). For hostdev we open the SCSI-generic interface which is a character device and is used to pass generic commads (/dev/sg0) I've originally attempted to change the way we open /dev/sg0 as you might know since you were CC'd on that thread, but testing actually proved that the above approach is correct, for scsi passthrough we don't need to treat the cdrom differently.

...nd my CD drive and can read the CD. However, when I try to make any kind of image (iso, bin/cue, etc) it freezes at a 0% loading screen. These are the only two lines sent to the terminal: Code: fixme:win:LockWindowUpdate ((nil)), partial stub! err:aspi:SCSI_OpenDevice Failed to open device /dev/sg0: Permission denied What's wrong? The AppDB indicates that it should work.

...as a LUN larger than currently supported. Driver ''sd'' needs updating - please use bus_type methods Driver ''sr'' needs updating - please use bus_type methods sd 0:0:0:0: [sda] 1953103872 512-byte hardware sectors: (999 GB/931 GiB) sd 0:0:0:0: Attached scsi generic sg0 type 0 (XEN) PCI add device 00:1f.1 sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Write cache: enabled, read cache: disabled, doesn''t support DPO or FUA sda: unknown partition table ---> Full log here: http://p.linode.com/2609 And from 2.6.18 (working): 3ware 9000 Sto...

...-device scsi-generic,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-hostdev0,id=hostdev0 \ > > [...] > > > the bad one: > > /usr/bin/qemu-system-x86_64 \ > > [...] > > > -blockdev '{"driver":"host_device","filename":"/dev/sg0","node-name":"libvirt-hostdev0-backend","read-only":true}' \ > > -device scsi-generic,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=libvirt-hostdev0-backend,id=hostdev0 \ > > This doesn't corelate with the version numbers you've mentioned, be...

...Lun: 00 Vendor: HP Model: Ultrium 5-SCSI Rev: Z58Z Type: Sequential-Access ANSI SCSI revision: 06 Host: scsi0 Channel: 00 Id: 00 Lun: 01 Vendor: QUANTUM Model: Scalar i40-i80 Rev: 135G Type: Medium Changer ANSI SCSI revision: 03 # mtx -f /dev/sg0 inquiry mtx: Request Sense: Long Report=yes mtx: Request Sense: Valid Residual=no mtx: Request Sense: Error Code=70 (Current) mtx: Request Sense: Sense Key=Illegal Request mtx: Request Sense: FileMark=no mtx: Request Sense: EOM=no mtx: Request Sense: ILI=no mtx: Request Sense: Additional Sense Code...

...ootindex=1 \ -netdev tap,fd=28,id=hostnet0 \ -device e1000e,netdev=hostnet0,id=net0,mac=52:54:00:5a:4c:8c,bus=pci.3,addr=0x0 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0 \ -blockdev '{"driver":"host_device","filename":"/dev/sg0","node-name":"libvirt-hostdev0-backend","read-only":true}' \ -device scsi-generic,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=libvirt-hostdev0-backend,id=hostdev0 \ -device vfio-pci,host=0000:00:02.0,id=hostdev1,bus=pci.7,addr=0x0,romfile=/home/streamer/gpu-80...

...m1 kernel: scsi host13: uas Mar 11 15:52:47 kvm1 kernel: scsi 13:0:0:0: Direct-Access Lexar WorkflowCR1 0 PQ: 0 ANSI: 6 Mar 11 15:52:47 kvm1 kernel: sd 13:0:0:0: [sda] 30198988 512-byte logical blocks: (15.4 GB/14.3 GiB) Mar 11 15:52:47 kvm1 kernel: sd 13:0:0:0: Attached scsi generic sg0 type 0 Mar 11 15:52:47 kvm1 kernel: sd 13:0:0:0: [sda] Write Protect is off Mar 11 15:52:47 kvm1 kernel: sd 13:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA Mar 11 15:52:47 kvm1 kernel: sda: sda1 sda2 Mar 11 15:52:47 kvm1 kernel: sd 13:0:0:0: [sda] Attached...

...ously installed open-vm-tools via yum. I then umounted it, and in vsphere deleted the vdisk and dmesg immediately shows... [155820.730477] vmw_pvscsi: msg type: 0x1 - MSG RING: 2/1 (5) [155820.730481] vmw_pvscsi: msg: device removed at scsi0:1:0 [155820.754176] sd 0:0:0:0: Attached scsi generic sg0 type 0 [155820.754247] sr 2:0:0:0: Attached scsi generic sg1 type 5 I also did much the same with a CentOS 6.7 VM, also using a 'paravirtual SCSI' vm on the same esxi host, when I added the vdisk, it immediately shows... # dmesg ..... vmw_pvscsi: msg type: 0x0 - MSG RING: 1/0 (5) vmw_p...

When I try to burn anything to cd, I get a message to insert a CD large enough for my file (normally an ISO image). Doesn't matter if the iso image is a 600Mb Centos ISO or a 48Mb DSL ISO. Same warning. My CD-Rs are Memorex 700MB/80min 52x disks that work just fine on XP systems. So what am I missing configuration-wise?

...s, offset 8) scsi target0:0:6: Domain Validation skipping write tests scsi target0:0:6: Ending Domain Validation scsi 0:0:6:1: tag#63 Disabling Tag Command Queuing st: Version 20160209, fixed bufsize 32768, s/g segs 256 sd 0:0:6:0: Power-on or device reset occurred sd 0:0:6:0: Attached scsi generic sg0 type 0 LASI 82596 driver - Revision: 1.30 Found i82596 at 0xf0107000, IRQ 17 eth0: 82596 at 0xf0107000, 08:00:09:c2:9e:60 IRQ 17. sd 0:0:6:0: [sda] 6281856 512-byte logical blocks: (3.22 GB/3.00 GiB) sd 0:0:6:0: [sda] Write Protect is off Christoph, you may add a Tested-by: Helge Deller <deller...

...raw,id=drive-hostdev0,readonly=on \ > -device scsi-generic,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-hostdev0,id=hostdev0 \ [...] > the bad one: > /usr/bin/qemu-system-x86_64 \ [...] > -blockdev '{"driver":"host_device","filename":"/dev/sg0","node-name":"libvirt-hostdev0-backend","read-only":true}' \ > -device scsi-generic,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=libvirt-hostdev0-backend,id=hostdev0 \ This doesn't corelate with the version numbers you've mentioned, because the &quo...

...si-id=0,lun=0,drive=drive-hostdev0,id=hostdev0 \ > > > > [...] > > > > > the bad one: > > > /usr/bin/qemu-system-x86_64 \ > > > > [...] > > > > > -blockdev '{"driver":"host_device","filename":"/dev/sg0","node-name":"libvirt-hostdev0-backend","read-only":true}' \ > > > -device scsi-generic,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=libvirt-hostdev0-backend,id=hostdev0 \ > > > > This doesn't corelate with the version numbers you'v...

More googling, and then something I wouldn't have thought of: smartctl doesn't work on this HBA against /dev/sd*. HOWEVER, it's happy as a clam against /dev/sgx, and there's my RAID, /dev/sg0 and /dev/sg1 (which lshw also was able to show me), but now, at least, I can run smartctl tests on the drives, and hopefully one will say, "Bad! Bad!". mark

...e with 4 SSD SATA disks. i installed oVirt node (= CentOS 7) on the first two disks configured as SW RAID 1 (in the oVirt node/CentOS installer). when i look at the device names in the running OS i get # lsscsi --scsi_id -g [0:0:0:0] disk ATA SAMSUNG MZ7LM480 204Q /dev/sda - /dev/sg0 [0:0:1:0] disk ATA SAMSUNG MZ7LM480 204Q /dev/sdb - /dev/sg1 [0:0:2:0] disk ATA SAMSUNG MZ7LM480 204Q /dev/sdc SAMSUNG_MZ7LM480HMHQ-00005_S2UJNX0J102216 /dev/sg2 [0:0:3:0] disk ATA SAMSUNG MZ7LM480 204Q /dev/sdd SAMSUNG_MZ7LM480HMHQ-00005_S2UJNX0J102214 /d...

> > [root at darkness ~]# ls -al /dev/sr* > ls: cannot access /dev/sr*: No such file or directory > [root at darkness ~]# ls /dev/s* > /dev/sda /dev/sda3 /dev/sdb1 /dev/sg0 /dev/stderr > /dev/sda1 /dev/sda4 /dev/sdb2 /dev/sg1 /dev/stdin > /dev/sda2 /dev/sdb /dev/sdb3 /dev/snapshot /dev/stdout > [root at darkness ~]# hwinfo --cdrom > [root at darkness ~]# > Presumably it is a SATA CD/DVD - if so you need to go through the output of...

...t;InstallPath"="C:\\Program Files\\Diablo II" "Program"="C:\\Program Files\\Diablo II\\Diablo II.exe" "Save Path"="C:\\Program Files\\Diablo II\\save\\" "SmallInstall"=dword:00000001 so are my rights on the cdrom cd /dev ls -l cdrom sg0 scd0 lrwxrwxrwx 1 root cdrom 3 Aug 17 2000 cdrom -> sr0 brw-rw---- 1 root cdrom 11, 0 Sep 25 2000 scd0 lrwxrwxrwx 1 root root 4 Sep 25 2000 sr0 -> scd0 groups michael cdrom floppy audio users Can somebody help me, please? Thanks, Michael