> These images should likewise be bootable under libvirt with, at most, a boot performance penalty because of the second boot.
Well, yes, it does boot on the second boot. Not trying to be contrarian here, but isn't a moot point that booting on the first boot is the de facto way things should work? I.e., a panic/reboot shouldn't be considered the "normal" way to boot on libvirt, or anywhere, for that matter. Furthermore, the panic/reboot breaks the virt-install cloud-init workflow, which expects the first boot to succeed. I mean, that's a solid expectation, right? :) What is the cloudimg designed to boot with, if not libvirt? I think virtio-scsi is being used. Here's the virt-install line, if it helps, virt-install \ -n myvm \ --description '' \ --os-type Linux \ --os-variant ubuntu16.04 \ --disk path=/var/lib/libvirt/images/focal-server-cloudimg-amd64.img,bus=scsi,discard=unmap \ --controller type=scsi,model=virtio-scsi \ --cdrom /var/lib/libvirt/images/nocloud.iso \ --virt-type kvm \ --graphics none \ --ram 1024 \ --vcpus 1 \ --network bridge:guestbr,model=virtio,virtualport_type=openvswitch,target=myvm \ --boot hd Once I do (eventually) get the image to boot through arcane ways, then I can confirm it is loading virtio-scsi: $ lsmod | grep virt virtio_net 53248 0 virtio_scsi 24576 2 Virtio-scsi seems like it needs to be compiled into the kernel for this to make sense. Am I missing something here? :) Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870189 Title: initramfs does not get loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1870189/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
