-1

Image imported from AZURE and converted to VMWARE. Booting stop after few seconds. Can't understanding why...

Very long loading "random:" and no loading more. enter image description here

2
  • 1
    Not directly related but you do know you're well past End Of Life for Ubuntu 18 don't you? Sep 11, 2023 at 21:23
  • I know, but this vm have very old and very important project. I'm trying to port it to a newer version of the system, but it's not so easy, because of old package dependencies. Sep 13, 2023 at 12:23

3 Answers 3

1

Here's my 5 cents.

The long loading of random module may indicate general lack of entropy on host machine.

You may even not have rdrand instruction set in your CPU flags, which you may verify with:

grep -m1 rdrand /proc/cpuinfo

If you get no result, you do not have rdrand instruction set in your CPU repertoir.


Where to get entropy = what to try:

$ apt-cache policy rng-tools5 
rng-tools5:
  Installed: 5-4
  Candidate: 5-4
  Version table:
 *** 5-4 500
        500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
        100 /var/lib/dpkg/status

If you find that you do not have rng-tools5 package installed, then install it right away, AFAIK you need to reboot afterward, but that I never tested not doing.

Final check, if the package managed to gather entropy from somewhere, may look like this:

$ sudo rngd -v
[sudo] password for vlastimil:                
Available entropy sources:
    Intel/AMD hardware rng
    DRNG
3
  • Experiments showed that the system boots normally in recovery mode. Sep 13, 2023 at 12:17
  • flags: ...skipped... f16c rdrand hypervisor ...skipped... Sep 13, 2023 at 12:25
  • rngd: read error. Available entropy sources: Intel/AMD hardware rng DRNG Sep 13, 2023 at 12:26
1

Based on the kernel messages (and it's a wild guess), it seems like it might be related to RNG (random number generator) device or virtual device (or lack of them), but the information is insufficient to specify what's the problem.

Since you're on vmware, I'd suggest trying changing the VM configuration or attached virtual hardwares. Starting from the configuration similar to original environment (you can try some tools such as dmidecode, lspci, lsusb to find out what virtual/physical hardware are attached to it, if you still have access to the Azure VM) would be a good starting point.

Also, it's not related to the question but consider migrating to newer LTS version of Ubuntu if you can ;)

1
  • I know, but this vm have very old and very important project. I'm trying to port it to a newer version of the system, but it's not so easy, because of old package dependencies. Sep 13, 2023 at 12:27
0

Take a look at syslog message at boot: uninitialized urandom read.

My guess is that when booting in the Azure environment there was a random number generator that isn't present in your VMware configuration. I would start by checking the kernel command line boot arguments to see if there is any custom reference to an Azure-related module that is no longer relevant in your new situation.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .