virt-install kickstart hangs and drops to dracut shell

Issues related to applications and software problems
Post Reply
vinceskahan
Posts: 8
Joined: 2015/02/25 18:15:33

virt-install kickstart hangs and drops to dracut shell

Post by vinceskahan » 2015/02/25 18:46:40

I'm trying to do a kickstart of a minimum possible centos7 using virt-install on a centos7 host system. What I'm seeing is that there is a big pause after 'Reached target Basic System' then it drops me to a dracut emergency shell after perhaps 3 minutes or so. I just ^D at the dracut prompt, doing nothing else, and the system proceeds through a hands-off kickstart just fine. Any idea what's going on ? Can somebody provide me with a known-good minimal ks.cfg that will not kick me into questions interactively ?

Command I'm running is:

Code: Select all

virt-install  --network bridge:br0  --ram=1024  --vcpus=1  --disk path=/var/lib/libvirt/images/vm8.img,size=10  --graphics none  --initrd-inject=/var/www/html/ks.cfg  --extra-args="console=tty0 console=ttyS0,115200 ks=file:/ks.cfg"  --location=/iso/CentOS-7.0-1406-x86_64-DVD/CentOS-7.0-1406-x86_64-DVD.iso  --name vm8
ks.cfg is:

Code: Select all

version=RHEL7
reboot
eula --agreed
cdrom
text
firstboot --disable
ignoredisk --only-use=vda
keyboard --vckeymap=us --xlayouts='us'
lang en_US.UTF-8
network  --bootproto=dhcp --device=eth0 --onboot=off --ipv6=auto
network  --bootproto=dhcp --hostname=localhost.localdomain
rootpw --plaintext root
skipx
timezone America/Los_Angeles --isUtc
bootloader --location=mbr --boot-drive=vda
autopart --type=lvm
clearpart --all --initlabel --drives=vda
%packages
@base
@core
%end
Here's a transcript:

Code: Select all

  OK  ] Reached target System Initialization.
         Starting Show Plymouth Boot Screen...
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Reached target Paths.
[  OK  ] Reached target Basic System.
dracut-initqueue[556]: mount: /dev/sr0 is write-protected, mounting read-only
[   66.510259] loop: module loaded
[   66.547253] bio: create slab <bio-1> at 1
[   66.556828] bio: create slab <bio-2> at 2
dracut-initqueue[556]: Warning: Could not boot.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Reached target Paths.
[  OK  ] Reached target Basic System.
dracut-initqueue[556]: mount: /dev/sr0 is write-protected, mounting read-only
dracut-initqueue[556]: Warning: Could not boot.
         Starting Dracut Emergency Shell...

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:/#

User avatar
TrevorH
Forum Moderator
Posts: 30355
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: virt-install kickstart hangs and drops to dracut shell

Post by TrevorH » 2015/02/25 21:14:02

You didn't pass any information to the VM about its networking and it needs it.
CentOS 6 died in November 2020 - migrate to a new version!
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 is dead, do not use it.
Full time Geek, part time moderator. Use the FAQ Luke

vinceskahan
Posts: 8
Joined: 2015/02/25 18:15:33

Re: virt-install kickstart hangs and drops to dracut shell

Post by vinceskahan » 2015/02/25 22:44:08

TrevorH wrote:You didn't pass any information to the VM about its networking and it needs it.
Isn't that what "network --bootproto=dhcp --device=eth0 --onboot=off --ipv6=auto" in ks.cfg is doing ?

What do you suggest I add, and in which piece (ks.cfg or the virt-install command) ?

More info - commenting that out unblocks the installation and it runs fine. Changing it to a static address also results in a working virt-install, although there is a noticeable pause at the same place in the sequence, but then it proceeds.

vinceskahan
Posts: 8
Joined: 2015/02/25 18:15:33

Re: virt-install kickstart hangs and drops to dracut shell

Post by vinceskahan » 2015/02/26 04:30:56

last update - solved

The problem was that I had messed up networking in my br0 and eno1 configuration due to misreading the Dell doc at http://linux.dell.com/files/whitepapers ... e_Easy.pdf

added 'BRIDGE=br0' to ifcfg-en01 (wired nic)

created a ifcfg-br0 containing:
DEVICE="br0"
BOOTPROTO="dhcp"
IPV6INIT="yes"
IPV6_AUTOCONF="yes"
ONBOOT="yes"
TYPE="Bridge"
DELAY="0"

restarted NetworkManager

result was the ip address for the LAN showed up on br0 , eno1 was up with no address, virbr0 was created with the private subnet 192.168.122.1 address, and life was good.

Post Reply

Return to “CentOS 7 - Software Support”