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?
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? 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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872941 Title: [Ubuntu 20.04] virt-install fails to detect path after images folder name has changed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1872941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
