The .hd1 and .is1 extensions cover cases where a driver does not support SCSI-2 but only SCSI-1-CCS. This is usually sufficient, but there is a special case when the extension-based approach does not work: In case the device is attached without a medium, i.e. with an empty image filename. In such a scenario, when later inserting a medium the SCSI level will still be the default one, i.e. SCSI-2 for these device types. (The SCSI level must not change once it has been set.)
In order to support SCSI-1-CCS for removable media drives without a medium inserted at creation a new property "scsi-level" and a new s2p command line option "--scsi-level" shall be supported.
s2pctl shall support attaching a new SCSI-1-CCS device
The protobuf interface shall be extended in a backwards compatible way, so that the SCSI level is available for remote clients that know how to deal with this information.
The .hd1 and .is1 extensions cover cases where a driver does not support SCSI-2 but only SCSI-1-CCS. This is usually sufficient, but there is a special case when the extension-based approach does not work: In case the device is attached without a medium, i.e. with an empty image filename. In such a scenario, when later inserting a medium the SCSI level will still be the default one, i.e. SCSI-2 for these device types. (The SCSI level must not change once it has been set.) In order to support SCSI-1-CCS for removable media drives without a medium inserted at creation a new property "scsi-level" and a new s2p command line option "--scsi-level" shall be supported. s2pctl shall support attaching a new SCSI-1-CCS device
The protobuf interface shall be extended in a backwards compatible way, so that the SCSI level is available for remote clients that know how to deal with this information.