virt-install + Kickstart provisioning keeps dropping to dracut shell

General support questions
Post Reply
sleepee
Posts: 3
Joined: 2017/07/02 13:57:06

virt-install + Kickstart provisioning keeps dropping to dracut shell

Post by sleepee » 2018/09/30 22:33:02

Hello everybody,

So, I've been trying to automate the provisioning of vm's on my KVM host running CentOS7 as much as possible.
So, I created a kickstart file, and a virt-install script that calls the kickstart file.
Almost everything works as expected, but a short while after Kickstart starts doing its thing, I start getting a whole bunch of error messages that look like this:

Code: Select all

[  188.602345] dracut-initqueue[699]: Warning: dracut-initqueue timeout - starting timeout scripts
That line repeats dozens and dozens of times until i finally get this message:

Code: Select all

[  188.602345] dracut-initqueue[699]: Warning: dracut-initqueue timeout - starting timeout scripts
[  188.602654] dracut-initqueue[699]: Warning: Could not boot.
[  188.733354] dracut-initqueue[699]: Warning: /dev/root does not exist
         Starting Dracut Emergency Shell...
Warning: /dev/root does not exist

Generating "/run/initramfs/rdsosreport.txt"


Entering emergency mode. Exit the shell to continue.
Type "journalctl" to view system logs.
You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot
after mounting them and attach it to a bug report.


dracut:/#
Here's a link to the rdsosreport.txt

Now, as you can see, the warning says "/dev/root does not exist", and indeed, from the dracut shell, I can see that /dev/root doesn't exist.

Code: Select all

dracut:/# ls -lh /dev/root
ls: cannot access /dev/root: No such file or directory
But I'm not sure why I get that message though. I got the ks.cfg file from an existing vm that I installed with the virt-manager GUI (although I did add/modify a few things).
And from the rdsosreport log, I can't find anything else that's going wrong.


Here's the virt-install script that creates the vm

And here's the ks.cfg kickstart file that the script calls.

I can spin up vm's with no problems whatsoever when I use the virt-manager GUI. Also, the virt-install script seems to do its job of actually creating the VM and calling the kickstart file.
So, I assume that the problem is within the kickstart file, but I just can't seem to find what I'm doing wrong.

Any help or input would be appreciated.
Thanks in advance.

Post Reply