Hey All,
Is it possible, or has anyone done any work, to get the Dual-Boot labs working as OVAs? My IT department is hesitant to allow dual-booting, but they would allow VMs using something like VirtualBox on local machines. Is this possible or allowed? If so, would it be possible to have the OVAs hosted via FTP downloads?
(For REL8 labs)
I have created Foundation0 in VMware WS, Virtualbox and KVM/QEMU. VMware WS version uses open-vm-tools package. Virtualbox version have own driver but this needs kernel-header, kernel-devel, gcc and libelf-devel packages for building driver.
KVM/QEMU version works without any changes. It is also fast with virtio-drivers.
OK...so I will ask this about the installation we've been discussing.
On workstation, what is the rngd (RNG entropy gatherer daemon) used for and why is it consistently chewing up ~43-49% of the processor time?
utility, servera, and serverb are running it, too (but not bastion and classroom).
Not surprisingly, workstation (for example) runs a lot better without it. Question: can this be (safely) shut down and masked?
{UPDATE} The environment has now been up for almost 3 hours and the rngd service is still running and taking up even more CPU time: ~58 - 70
More information about the rngd daemon...
A couple of more notes:
OK, more notes, especially for @ralii:
Due to an unfortunate set of circumstances, I ended up deleting an RH134 environment that was working under VMware (for those who are unaware, there are issues using the Windows Subsystem for Linux 2 if you are also using VMware Workstation).
https://tcpip.me/2020/11/14/vmware-workstation-nested-virtualization-and-wsl2-disaster/
Anway. I've been trying to get my RH134 environment reinstalled, and I'm running into the same problem as before... rht-f0finish is trying the resolve bastion*.example.com, as seen in a later screen shot.
So far, it seems like a dice roll where you have a 1-in-6 (or worse) chance of getting it to install "properly" -- without it having it try and resolve a bunch of bastion*.example.com FQDNs.
Now, what makes this odd is:
standalone rh134 was used...
the system confirms that it is in standalone mode...
yet, here it is trying to resolve bastion*.example.com
I've tried this a few times this morning, each time starting fresh. Some notes:
other notes:
And, for those who are curious, the script I'm using (I'm always fully aware that there are probably better was to write scripts).
I create it as /home/kiosk/bin/start and make it executable. Then, when opening a terminal on foundation0, just type start
Red Hat
Learning Community
A collaborative learning environment, enabling open source skill development.