[Bug 1872941] Comment bridged from LTC Bugzilla

[bugproxy]

------- Comment From cborntra at de.ibm.com 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.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to debian-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1872941

Title:
  [Ubuntu 20.04] virt-install fails to detect path after images folder
  name has changed

Status in Ubuntu CD Images:
  Opinion
Status in Ubuntu on IBM z Systems:
  Fix Released
Status in debian-installer package in Ubuntu:
  Won't Fix
Status in virt-manager package in Ubuntu:
  Fix Released

Bug description:
  
  For 20.04.0 d-i is changing from /images/ to /legacy-images/ in it's directory structure.

  For 20.04.1+ it will not exist at all.

  For all Ubuntu releases virt-install should learn how to use cloud-
  images from https://cloud-images.ubuntu.com/ which are preinstalled
  cloud-init enabled qcow2 images, with unpacked kernels. Allowing to
  change kernel cmdline parameters and boot in-place. Which is the best
  & default Ubuntu experience on VMs.

  ---

  Installer version: Latest
  https://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x

  Description/Reproduction:
  Start virt-install with the following options:

  virt-install \
  --name ubuntu20-guest1 \
  --memory 4096 \
  --vcpus 4 \
  --disk "size=4" \
  --location http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x \
  --network "network=default"

  Error:
  ERROR    Error validating install location: Could not find an installable distribution at 'http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x'

  The location must be the root directory of an install tree.
  See virt-install man page for various distro examples.

  Looking at previous releases I would guess it expects an "images"
  directory instead of the new "legacy-images" directory. I'm aware of
  the workaround to specify kernel/initramfs directly but that shouldn't
  be a solution.

  == Comment: #2 - Andre Wild1 <Andre.Wild1 at ibm.com> - 2020-04-15 03:51:21 ==
  (In reply to comment #0)
  > Installer version: Latest
  > https://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x
  >

  Sorry I've copied the wrong link. This is the link I've used successfully in the past:
  http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1872941/+subscriptions