Stuck at "Configuring alsa-sof-firmware.noarch" installing with f38-netboot ISO

I am trying to compare the outcome of standard F38 ISO with Server38-netboot ISO (choosing Workstation) .

With Silverblue 38 as host, using virt-manager to do GUI based installation.

With netboot ISO, Anaconda installation stuck at “Configuring alsa-sof-firmware.noarch”

As it is a KVM guest, I can let it run and waiting for your input on how to troubleshoot this issue.

Plesea give me hints / pointers on what should be collected, how to finish the installation, etc.

I do have in virt-manager under Sound (Speaker Icon) three options to set. Just check if you can switch to an other one.

Here a list of what hardware they emulate:

Check for hardware virtualization support:

sudo virt-host-validate

Also make sure the VM has at least 2 GB of RAM.

I always use either 4GB or 8GB RAM and at least 2 CPUs for each VM. Is yours adequately provisioned?

I am using virt-manager defaut for Fedora - 2vCpu + 2GB ram + 20GB disk

$ sudo virt-host-validate

  QEMU: Checking for hardware virtualization                                 : PASS
  QEMU: Checking if device /dev/kvm exists                                   : PASS
  QEMU: Checking if device /dev/kvm is accessible                            : PASS
  QEMU: Checking if device /dev/vhost-net exists                             : PASS
  QEMU: Checking if device /dev/net/tun exists                               : PASS
  QEMU: Checking for cgroup 'cpu' controller support                         : PASS
  QEMU: Checking for cgroup 'cpuacct' controller support                     : PASS
  QEMU: Checking for cgroup 'cpuset' controller support                      : PASS
  QEMU: Checking for cgroup 'memory' controller support                      : PASS
  QEMU: Checking for cgroup 'devices' controller support                     : PASS
  QEMU: Checking for cgroup 'blkio' controller support                       : PASS
  QEMU: Checking for device assignment IOMMU support                         : PASS
  QEMU: Checking if IOMMU is enabled by kernel                               : PASS
  QEMU: Checking for secure guest support                                    : WARN (Unknown if this platform has Secure Guest support)
   LXC: Checking for Linux >= 2.6.26                                         : PASS
   LXC: Checking for namespace ipc                                           : PASS
   LXC: Checking for namespace mnt                                           : PASS
   LXC: Checking for namespace pid                                           : PASS
   LXC: Checking for namespace uts                                           : PASS
   LXC: Checking for namespace net                                           : PASS
   LXC: Checking for namespace user                                          : PASS
   LXC: Checking for cgroup 'cpu' controller support                         : PASS
   LXC: Checking for cgroup 'cpuacct' controller support                     : PASS
   LXC: Checking for cgroup 'cpuset' controller support                      : PASS
   LXC: Checking for cgroup 'memory' controller support                      : PASS
   LXC: Checking for cgroup 'devices' controller support                     : PASS
   LXC: Checking for cgroup 'freezer' controller support                     : FAIL (Enable 'freezer' in kernel Kconfig file or mount/enable cgroup controller in your system)
   LXC: Checking for cgroup 'blkio' controller support                       : PASS
   LXC: Checking if device /sys/fs/fuse/connections exists                   : PASS

I am using virt-manager default “HDA(ICH9)”

For comparison, Everything-netinst and Workstation both installed OK. Only Server-netboot stuck at that task.

1 Like

What ISO are you referring to with “standard F38 ISO”? Would that be the Everything netinstall ISO?

That would hint at more differences under the hood between Everything and Server netinst ISO.

Elsewhere I proposed to merge these to, since they appear to achieve the same thing provided one selects the proper partitioning scheme:

But if this turns out to be a Server media issue, it would need to be addressed as well.

Can you get to the logs in /tmp ?
I believe you can access a terminal with Ctrl + Alt + F (1 - 6) during the install.

1 Like

anaconda.log
https://paste.centos.org/view/480e843d
program.log
https://paste.centos.org/view/688d71f1
storage.log
https://paste.centos.org/view/f7e88454
packaging.log
https://paste.centos.org/view/9df22cb7

syslog is too large to upload.