Comment # 22 on bug 1170863 from Michael Friesenegger

(In reply to Marcus Schaefer from comment #21)
> > This image booted.
> 
> yay :) as soon as my open questions are clarified with Raymund we are going
> to merge the open PR.
> 
> Something different but related:
> 
> Do you know if somebody is working on the kpartx issue when 4k devices are
> used ? See the log here:
> 
>     osc buildlog -M PhysicalBSZ_4096 images s390x
> 
> in the Virtualization:Appliances:Images:Testing_s390:sle15/test-image-disk
> project:
> 
> [  104s] [ DEBUG   ]: 14:49:27 | Initialize DASD disk with new VTOC table
> [  104s] [ DEBUG   ]: 14:49:27 | EXEC: [bash -c cat /tmp/tmp9oupc5fm | fdasd
> -f /dev/loop0]
> [  105s] [ INFO    ]: 14:49:28 | --> creating boot partition
> [  105s] [ DEBUG   ]: 14:49:28 | p.lxboot: fdasd: n p cur_position +300M w q
> [  105s] [ DEBUG   ]: 14:49:28 | EXEC: [bash -c cat /tmp/tmp8qsbzkxf | fdasd
> -f /dev/loop0]
> [  106s] [ INFO    ]: 14:49:29 | --> creating LVM root partition
> [  106s] [ DEBUG   ]: 14:49:29 | p.lxlvm: fdasd: n p cur_position +all_freeM
> w q
> [  106s] [ DEBUG   ]: 14:49:29 | EXEC: [bash -c cat /tmp/tmpj_j_dmhq | fdasd
> -f /dev/loop0]
> [  108s] [ DEBUG   ]: 14:49:31 | EXEC: [kpartx -s -a /dev/loop0]
> [  108s] [ ERROR   ]: 14:49:31 | KiwiMappedDeviceError: Device
> /dev/mapper/loop0p1 does not exist
> [  108s] [ INFO    ]: 14:49:31 | Cleaning up Disk instance
> 
> 
> This one prevents us from creating images that could run on s390
> disks using 4k block size.
> 
> Thanks for anything that you can do to make people aware of it

You will happy to know that kpartx-0.8.2+18.9ff73e7-2.1.s390x included in
SLES15 SP2 has the 4096 blocksize support.  The kpartx changelog is below which
I learned from Mark Post.

* Thu Aug 29 2019 mwilck@suse.com
- Update to version 0.8.2+17+suse.21ac578:
  * kpartx: recognize DASD on loop devices again (bsc#1139775)

I am successfully building oem dasd images for SLES15 SP2 and SLES12 SP5 using
kiwi on SLES15 SP2.  Like the KVM image discussed above, the oem dasd image
does not boot after being built by kiwi.  I have a script that makes the oem
dasd image bootable.  Should I open a new bug so you can work on making oem
dasd bootable?