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?
Rich.
(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)
On 25/09/2019 17:46, Richard W.M. Jones wrote:
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?
Rich.
Hi Richard,
Can you share some of the machine specs ? so VM details like memory etc ? (in our initial tests, we found that it wasn't able to explode the initramfs and install.img for stage2 on VM with low memory specs)
FWIW, this is the kickstart that was used for our own QA/validation tests for CentOS 8 :
https://github.com/CentOS/sig-core-QA_harness_ansible/blob/master/templates/...
And here is the virt-install command that ansible generates when deploying the VM :
https://github.com/CentOS/sig-core-QA_harness_ansible/blob/master/templates/...
On Wed, Sep 25, 2019 at 06:40:43PM +0200, Fabian Arrotin wrote:
Can you share some of the machine specs ? so VM details like memory etc ? (in our initial tests, we found that it wasn't able to explode the initramfs and install.img for stage2 on VM with low memory specs)
In the original email: https://lists.centos.org/pipermail/centos-devel/2019-September/017813.html
but I've given the guest 2GB of RAM. Do you think that's not enough? I'll try more (but tomorrow, it's really late here).
FWIW, this is the kickstart that was used for our own QA/validation tests for CentOS 8 :
https://github.com/CentOS/sig-core-QA_harness_ansible/blob/master/templates/...
And here is the virt-install command that ansible generates when deploying the VM :
https://github.com/CentOS/sig-core-QA_harness_ansible/blob/master/templates/...
Thanks, that's interesting, I'll compare them to mine and see if I can see a difference.
Rich.
On Wed, Sep 25, 2019 at 22:35 Richard W.M. Jones wrote:
On Wed, Sep 25, 2019 at 06:40:43PM +0200, Fabian Arrotin wrote:
Can you share some of the machine specs ? so VM details like memory etc ? (in our initial tests, we found that it wasn't able to explode the initramfs and install.img for stage2 on VM with low memory specs)
In the original email: https://lists.centos.org/pipermail/centos-devel/2019-September/017813.html
but I've given the guest 2GB of RAM. Do you think that's not enough? I'll try more (but tomorrow, it's really late here).
FWIW I wasn't able to complete a regular install using the dvd with 2GB of ram, the interface froze before completion. Bumping to 4GB fixed the issue.
-Tristan
On 9/26/19 3:48 AM, Tristan Cacqueray wrote:
FWIW I wasn't able to complete a regular install using the dvd with 2GB of ram, the interface froze before completion. Bumping to 4GB fixed the issue.
I believe that if you add "text" to the kernel boot parameters, you'll get a text based version of the Anaconda installer. Or at least that used to be the case.
I've included that parameter with my kickstart installs, and I get a text installer (which might be because they're automated installs), but I haven't tried supplying the option manually with this release yet. I've also built VMs this way, for a variety of platforms, with only 2gb of RAM, although I used the smaller boot CD, and a network repo to do it.
L~
On 9/27/19 7:22 AM, Ladar Levison via CentOS-devel wrote:
On 9/26/19 3:48 AM, Tristan Cacqueray wrote:
FWIW I wasn't able to complete a regular install using the dvd with 2GB of ram, the interface froze before completion. Bumping to 4GB fixed the issue.
I believe that if you add "text" to the kernel boot parameters, you'll get a text based version of the Anaconda installer. Or at least that used to be the case.
I've included that parameter with my kickstart installs, and I get a text installer (which might be because they're automated installs), but I haven't tried supplying the option manually with this release yet. I've also built VMs this way, for a variety of platforms, with only 2gb of RAM, although I used the smaller boot CD, and a network repo to do it.
The text installer hasn't had a usable UI for partitioning since before CentOS 7 / Fedora 19 so this is unlikely to work well unless you are completely suppressing all questions from appearing.
On Thu, Sep 26, 2019 at 07:18:25AM +0900, Tristan Cacqueray wrote:
On Wed, Sep 25, 2019 at 22:35 Richard W.M. Jones wrote:
On Wed, Sep 25, 2019 at 06:40:43PM +0200, Fabian Arrotin wrote:
Can you share some of the machine specs ? so VM details like memory etc ? (in our initial tests, we found that it wasn't able to explode the initramfs and install.img for stage2 on VM with low memory specs)
In the original email: https://lists.centos.org/pipermail/centos-devel/2019-September/017813.html
but I've given the guest 2GB of RAM. Do you think that's not enough? I'll try more (but tomorrow, it's really late here).
FWIW I wasn't able to complete a regular install using the dvd with 2GB of ram, the interface froze before completion. Bumping to 4GB fixed the issue.
I got around to trying with 4GB today but it did not fix the original problem, but also I've still not had time to look into this properly to see if I can work out what's going wrong.
Rich.
On Wed, Sep 25, 2019 at 04:46:40PM +0100, Richard W.M. Jones wrote:
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?
My colleague worked out what is going on and it does appear to be an actual bug in CentOS 8.
The problem is fixed by adding one line to the kickstart:
# Kickstart file for centos-8.0 # Generated by libguestfs.git/builder/templates/make-template.ml
install text reboot lang en_US.UTF-8 keyboard us network --bootproto dhcp rootpw builder firewall --enabled --ssh timezone --utc America/New_York selinux --enforcing
bootloader --location=mbr --append="console=tty0 console=ttyS0,115200 rd_NO_PLYMOUTH"
url --url="http://mirror.centos.org/centos-8/8/BaseOS/x86_64/os"
zerombr clearpart --all --initlabel --disklabel=gpt autopart --type=plain
# Halt the system once configuration has finished. poweroff
%packages @core %end
But in previous versions of CentOS, and indeed in RHEL 8, this line is not necessary, it is somehow inferred (from the kernel command line? I'm not sure from where).
Rich.
On 10/2/19 9:33 AM, Richard W.M. Jones wrote:
On Wed, Sep 25, 2019 at 04:46:40PM +0100, Richard W.M. Jones wrote:
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?
My colleague worked out what is going on and it does appear to be an actual bug in CentOS 8.
The problem is fixed by adding one line to the kickstart:
# Kickstart file for centos-8.0 # Generated by libguestfs.git/builder/templates/make-template.ml
install text reboot lang en_US.UTF-8 keyboard us network --bootproto dhcp rootpw builder firewall --enabled --ssh timezone --utc America/New_York selinux --enforcing
bootloader --location=mbr --append="console=tty0 console=ttyS0,115200 rd_NO_PLYMOUTH"
url --url="http://mirror.centos.org/centos-8/8/BaseOS/x86_64/os"
zerombr clearpart --all --initlabel --disklabel=gpt autopart --type=plain
# Halt the system once configuration has finished. poweroff
%packages @core %end
But in previous versions of CentOS, and indeed in RHEL 8, this line is not necessary, it is somehow inferred (from the kernel command line? I'm not sure from where).
Rich.
Interesting that that ever worked. However, https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/htm...
does note:
To actually run the installation, one of cdrom, harddrive, hmc, nfs, liveimg, or url must be specified.
-
Dominique Martinet -
Fabian Arrotin -
Kevin Stange -
Ladar Levison -
Orion Poplawski -
Richard W.M. Jones -
Tristan Cacqueray