Our CI uses a Jammy Ubuntu cloud image, but with quite a large list of extra installed packages. To make sure it's not something specific to that environment, I tried this:
autopkgtest-buildvm-ubuntu-cloud qemu-system-x86_64 -enable-kvm -nographic -m 2048 -device virtio-rng-pci -drive file=autopkgtest-jammy-amd64.img,if=virtio -snapshot Log in as ubuntu:ubuntu, then sudo apt update sudo eatmydata apt install -y virtinst libvirt-daemon-system sudo touch /var/lib/libvirt/empty.iso sudo virt-install --name t1 --os-variant fedora28 --memory 128 --wait -1 --noautoconsole --disk 'size=0.25,format=qcow2' --cdrom /var/lib/libvirt/empty.iso --boot uefi it fails in exactly the same way. So (1) this confirms it's not our Cockpit CI environment, and (2) provides a nice smoke autopkgtest for libvirt. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968131 Title: Starting VM with UEFI firmware fails with swtpm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1968131/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
