Comment 35 for bug 1902179

------- Comment From <email address hidden> 2021-01-22 10:02 EDT-------
Hi Frank,

we've now internally confirmed that setting the "nvme-core.multipath=0" Kernel
parameter as a workaround makes "chreipl node" succeed with NVMes that otherwise break the current chreipl due to its lack of multipath support.

Do you think it would be possible to set this Kernel parameter for the installer?
As far as I understand this option doesn't necessarily have to be set for the installed system since the IPL information is stored in firmware as FID
and namespace so only a manual "chreipl node /dev/nvmeXYZ" from
the installed system would risk breaking the IPL information and there
the user should get a crash and can instead use "chreipl nvme -i <fid> -s <nsid>". Normal "zipl" as done by a kernel update should not be a problem, in fact I've got an Ubuntu 20.04 installed on an NVMe (via KVM ;-) /dev/vda on an NVMe) here and kernel updates worked fine.

Alternatively there is also the config option CONFIG_NVME_MULTIPATH if
we would set that to "n" for Z that should also work.

Either way we'll of course work on a proper fix for chreipl.