Comment 6 for bug 1921468

Hi,
I have tested this with:
$ virt-install --name testinst1 --memory 2048 --disk path=/dev/disk/by-path/ccw-0.0.151e --cdrom /var/lib/libvirt/images/ubuntu-18.04.5-server-s390x.iso

But while the issue itself and the fix is clear, this did not trigger the issue.
In my case the reboot after install worked just fine even without the fix.
Might I ask:
- which "xxxxxx.iso" it is in your example that has issues with this?
- which disk setup did you select on install (that is then put onto the dasd by the installer)
- what should I expect in the error case, I expected a fail or hang on reboot but got:

```
The system is going down NOW!
Sent SIGTERM to all processes
Sent SIGKILL to all processes
Requesting system reboot

Domain creation completed.ts; <Enter> activates buttons
Restarting guest.
Connected to domain testinst1
Escape character is ^]

Booting entry #0
[ 0.450525] Linux version 4.15.0-140-generic (buildd@bos02-s390x-010) (gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)) #144-Ubuntu SMP Fri Mar 19 14:11:29 UTC 2021 (Ubuntu 4.15.0-140.144-
generic 4.15.18)
```

```
The config (in regard to boot) that virtinst left (and that worked) was:
  <os>
    <type arch='s390x' machine='s390-ccw-virtio-focal'>hvm</type>
    <boot dev='hd'/>
  </os>
...
    <disk type='block' device='disk'>
      <driver name='qemu' type='raw' cache='none' io='native'/>
      <source dev='/dev/disk/by-path/ccw-0.0.151e' index='2'/>
      <backingStore/>
      <target dev='vda' bus='virtio'/>
      <alias name='virtio-disk0'/>
      <address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0000'/>
    </disk>
```

I agree to the fix, but need a reasonable testcase that works (also to explain to the SRU team why this is a realistic issue someone would hit).