I've got a vm that when it starts goes to dracut-initqueue timeout and i'm a bit fuzzy on the technical side of this on what to do to resolve this issue. If anyone can help me resolve this i'd greatly appreciate it. Our vendor that provided the OVA file only supports us if we are using vSphere (previously ESXi). Install is pretty simple under the old ESXi (shows you how long it's been since we had to set up a box). Background - box is a standalone server once the VM is running for a building automation system that basically turns this box into a large controller. We are just having a few small issues as we move over to proxmox on getting the first one going. We have a dozen more to move over to proxmox once we resolve this issue. All installs are identical so if we can resolve this it becomes a cookie-cutter setup going forward. Thank you so much for any help you can give me.
dracut-initqueue timeout please help
- Thread starter andrewvodonnell
- Start date
I had a similar issue migrating a vm from vSphere to proxmox, in my case it was a problem with the virtio drivers, as the disk was configured as SCSI using the virtio scsi single controller.
Have you tried editing the disk and see if it boots as ide/sata?
If you have access to a ESXi host or vSphere environment you can also boot the server there, and then verify if the virtio drivers are included in the kernel and in the boot temporary filesystem (I found this link helpful https://www.tencentcloud.com/document/product/213/9929 ) and also possibly add the drivers using dracut
dracut --add-drivers "virtio_balloon virtio_ring virtio_input virtio_pci virtio virtio_blk virtio_net virtio_scsi" --force
In case you cannot login on the server, playing around with the controller/disk might help in getting the server to boot, but performances might suffer, in which case it might be a good idea to ask the vendor to possibly include virtio drivers/KVM support, as you will possibly not be the only customer considering a migration from vSphere to Proxmox
Have you tried editing the disk and see if it boots as ide/sata?
If you have access to a ESXi host or vSphere environment you can also boot the server there, and then verify if the virtio drivers are included in the kernel and in the boot temporary filesystem (I found this link helpful https://www.tencentcloud.com/document/product/213/9929 ) and also possibly add the drivers using dracut
dracut --add-drivers "virtio_balloon virtio_ring virtio_input virtio_pci virtio virtio_blk virtio_net virtio_scsi" --force
In case you cannot login on the server, playing around with the controller/disk might help in getting the server to boot, but performances might suffer, in which case it might be a good idea to ask the vendor to possibly include virtio drivers/KVM support, as you will possibly not be the only customer considering a migration from vSphere to Proxmox
I just wanted to thank you as I was dealing with this as well and figured it was a missing driver in the initramfs, but wasn't sure what to include. I ssh'd into the host, mounted and chroot'd into the VM's drives, and performed the dracut I had already built, including the --add-drivers above and it solved this for me. I have two more VMs to import from VirtualBox and I imagine I'll be doing this twice more.
Note for those who read this and think this is the solution for them, because the nature of chroot don't forget to bind mount /sys, /run, /proc, and /dev, then chroot, and when using the dracut command you will likely need to include the path to the initramfs image file and then the kernel version after.
This was my command, for a real world example (note it has my file includes that I was using for troubleshooting):
Bash:
dracut --add-drivers "virtio_balloon virtio_ring virtio_input virtio_pci virtio virtio_blk virtio_net virtio_scsi" --include /usr/bin/find /usr/bin/find --include /usr/bin/lsblk /usr/bin/lsblk --force /boot/initramfs-5.14.0-503.22.1.el9_5.x86_64.img 5.14.0-503.22.1.el9_5.x86_64Again, thanks for saving me from further headache.