(Giving a bit back since I asked a question :p)
Richard W.M. Jones wrote on Wed, Sep 25, 2019 at 04:46:40PM +0100:
I'm trying to boot CentOS 8 in a VM using my usual kickstart and virt-install recipes. Dracut fails in a way that indicates it cannot find the install disk:
[ 4.984555] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready [ 4.985509] 8021q: adding VLAN 0 to HW filter on device enp1s0 [ 5.599558] IPv6: ADDRCONF(NETDEV_CHANGE): enp1s0: link becomes ready [ 7.058879] dracut-initqueue[926]: RTNETLINK answers: File exists [ 134.439929] dracut-initqueue[926]: Warning: dracut-initqueue timeout - starting timeout scripts [ 134.969517] dracut-initqueue[926]: Warning: dracut-initqueue timeout - starting timeout scripts [ 135.488283] dracut-initqueue[926]: Warning: dracut-initqueue timeout - starting timeout scripts (repeated endlessly until it drops into the emergency shell)
The kernel sees the virtio-blk device, the kmod is loaded, and /dev/vda exists ...
So I don't really know. Can anyone see my mistake?
Network failed to initialize somehow? I had a similar lack of messages when I failed my qemu network params and no interface existed.
Once you have an emergency shell 'journalctl' might have more useful informations; I noticed I had no network right away in my case... I could install a centos 8 earlier today with the following command and manually answering questions (this is before kickstart, so your kickstart will probably work anyway) :
qemu-system-x86_64 -machine type=pc,accel=kvm -cpu host -hda c8.img -m 30G -netdev user,id=n1 -device virtio-net,netdev=n1 -device virtio-rng-pci -nographic -serial mon:stdio -kernel vmlinuz -initrd initrd.img -append 'console=ttyS0,115200 ksdevice=bootif text inst.repo=<link to some mirror>/8/BaseOS/x86_64/os'
where the vmlinuz and initrd.img came from BaseOS/x86_64/os/images/pxeboot/
(I'm not using any libvirt tool, so no idea what they might have done wrong -- the network setup should be basic enough to not fail nor should it pick an incorrect kernel/initrd so it's odd)