Comment 7 for bug 1650300

------- Comment From <email address hidden> 2017-01-12 07:23 EDT-------
Unfortunately, the term dasd is overloaded as it describes a) a disk device type in terms of access method (more comparable with SCSI or IDE) and b) the format of the disk in a misleading manner (instead of dasd it should rather be called eckd).
This becomes quite obvious by looking at KVM: here the device typein the guest is virtio_blk, whereas the data format is determined by the device type in the host, which can be an ECKD DASD. BIODASDINFO won't work in this case because it needs the dasd driver.
The way I'd suggest to attack this would be in partman-base rather than in partman-partitioning, because the former package determines the label type to be written. I.e. one could check whether the disk is of type dasd_fba and in this case not request a dasd label.
Alternatively, one could consider changing parted, but this might be more complex/error prone.