random: wait-for-root: uninitialized urandom read (16 bytes read)

Description

After having performed an APT-upgrade [I kept the existing version of GRUB when prompted] all of my VMs won’t start anymore, halting instead their boot on:

random: wait-for-root: uninitialized urandom read (16 bytes read)

They’re all Ubuntu 18 KVM [downloaded from the marketplace] running on an Ubuntu 16 host machine and one v 5.4.13.

To Reproduce

Do what I did above.

Expected behavior

They should boot.

Details

• Affected Component: core
• Hypervisor: KVM
• Version: 5.4.13

Additional context

None that I can think of.

Thanks in advance for your help.

Progress Status

• Branch created
• Code committed to development branch
• Testing - QA
• Documentation
• Release notes - resolved issues, compatibility, known issues
• Code committed to upstream release/hotfix branches
• Documentation committed to upstream release/hotfix branches

[vholer]

Download latest Ubuntu images from the Marketplace, they are already fixed.

Problem is a caused by Grub configuration overrides in /etc/default/grub.d, which brings back the configuration for the serial console on Grub refresh (mostly caused by kernel upgrade) and next reboot. As a workaround, delete directory /etc/default/grub.d from all your running Ubuntu instances and trigger update-grub.

To fix a VM which doesn’t boot, you have to power-off the VM and add serial console device via raw parameters for the libvirt. Steps:

• power off VM
• click on “Conf” -> “Update Configuration”
• click on “Other”
• place into “Data” box:

<devices><serial type='pty'><target port='0'/></serial><console type='pty'><target type='serial' port='0'/></console></devices>

• power on VM

[frootmig]

@vholer

Download latest Ubuntu images from the Marketplace, they are already fixed.

It seems to work for 16.04. I had no machine running with the template, deleted it and re-downloaded. The template seems to work now. I was not able to update the 18.04 template because there are two VMs attached. So I added the template with a new name. This survived the apt upgrade, too.

It is a bit confusing, that the marketplace apps do not show an updated date. And I’m still not sure if it’s possible to update the image used for the existing VMs or if I should recreate them.

To get the VMs with the old template up and running again just for clarification: you mean placing the XML snipped in

• “Conf” -> “Update Configuration”
• Click “Tags”
• Under “RAW data” with type “kvm” in the data Box

Another option is using the advanved tab and add to the template RAW = [ DATA = "<devices><serial type='pty'><target port='0'/></serial><console type='pty'><target type='serial' port='0'/></console></devices>", TYPE = "kvm" ]