Comment 36 for bug 1872941

------- Comment From <email address hidden> 2020-04-30 02:30 EDT-------
(In reply to comment #43)
> I am working on implementing network config & network .iso discovery
>
> On s390x, when using virt-install, do you really want to configure
> networking at all or do you want it to simply dhcp, self-find the right iso,
> download that and attempt booting that?

I think in a lot of places s390x guest still do have assigned IP addresses, so maybe asking for autoconfig or manual network config is the right thing?
>
> Or do you still want interactive experience to ask for any chzdev devices to
> activate, dhcp or static, ip address, gateway (? or just always use
> default), dns (? or just always use gateway), vlan id, http_proxy, url to
> iso?

Fortunately under KVM all virtio devices are auto activated. And for everything else just do that depending on the first decision.

If you want to have full headleass installation, the user should use kickstart, autoyast, preseed or your new way.

> Because it feels like the best experience is no questions asked, just works.
> Which might be the case with DPM autoconfigured networking devices & qemu
> autoconfigured devices.
>
> Also virt-install can download & import boot off .iso. Have you tried to
> point virt-install just at the live-server.iso? On s390x, I expect it to be
> downloaded, added as a SCSI disk, and el-torito boot to be performed. And if
> kernel params are needed, virt-install knows how to extract kernels from
> iso, and it can then do direct kernel boot with kernel params, which iso
> attached.

Yes that works, but it requires root as the parameter things mounts the ISO.