Fedora 25 image is not bootable (virtio hard disk drivers missing)

[martinpitt]

I'm using mkosi as packaged in Fedora 25 (version 1.fc25):

sudo mkosi -d fedora -r 25 -b -t raw_gpt --password root  -o /srv/nspawn/f25.img

Booting this in QEMU (with -bios /usr/share/edk2/ovmf/OVMF_CODE.fd times out waiting for dev-gpt\x2dauto\x2droot.device

Screenshot

/dev/disk/ only has a symlink for sr0 (the CD drive), there are no /sys/block/* devices other than sr0. It seems the generated initramfs is lacking the drivers for the QEMU virtio hard disks?

[martinpitt]

Indeed booting the image without a virtio hard disk works fine.

[martinpitt]

In an anaconda VM install of F25 I see virtio_{blk,net,scsi} in lsinitrd, while in mkosi's image these are missing. I tried to work around this with

$ cat /etc/dracut.conf.d/virtio.conf 
add_drivers+="virtio_blk virtio_scsi virtio_net"

This is because dracut normally auto-detects required drivers, but this doesn't work when being called in that chroot construction mode of mkosi.

Even with this the image still doesn't boot with virtio, it seems EFI does not even get to the point of starting sd-boot (a bit hard to tell as sd-boot is really quiet).

[fsateler]

in the debian path we enable the "fat" dracut that installs all modules (although for a different reason)
https://github.com/systemd/mkosi/blob/master/mkosi#L780

[poettering]

hmm, so we use "no-hostonly" mode in dracut which would mean the included kernel modules cover all kinds of hw, not just the one used locally on the host. I am pretty sure this should also include virtio stuff, and if it does not I'd assume that's a bug in dracut. @haraldh any idea?

[poettering]

filed a bug about that now in dracut github:

dracutdevs/dracut#205

[poettering]

A work-around fix is now waiting in #180. But I think this should be fixed in dracut anyway.