Virtualbox, real trouble

[Dirk Broer]

Without any further comment: Schermafbeelding 2021-11-27 155605.JPG (click for bigger picture)
To add injury to insult: one of these is now uploaded, without any credits received...

[vaughan]

This Virtual Box thingy is terrible. Over on Cosmology I set to accept Legacy tasks only to avoid all the problems with Virtual Machines. That 500+MB d/l of Docker was a waste of electrons.

[Dirk Broer]

I have one machine, the Ryzen 3 3100 running Ubuntu, that runs the Cosmology VMs very well (3.5-4.5 min/wu for hours now), but trashes the Rosetta ones under the same settings.
Under Linux there is no need for a 500 MB download, I just selected a few docker files in Synaptic to get a Docker infrastructure and let Synaptic figure out the dependencies.
The AM1 and other lesser systems became saturated with VMs, but the Linux ones had another message (Communication with VM Hypervisor failed) than the Windows ones (VM job unmanageable).

[Dirk Broer]

Just 'revived' a Ryzen Windows box, virtual box-wise, as both LHC@Home and LHCathome-dev reported that the CPU 'did not support hardware virtualization'.
Utter bollocks! The CPU in question is a Ryzen 5 3400G, on an Asrock Fatal1ty X370 Gaming-ITX/ac.

Now, to get virtualization running for LHC one has to jump no less than four hurdles in this case, and that is after installing Virtual Box.

1. Enable AMD-v: In the BIOS, go to Advanced/CPU Configuration -> SVM Mode and set SVM Mode to 'enabled'.
2. Enable AMD-vi: In the BIOS, go to Advanced/North Bridge Configuration -> IOMMU and set to 'enabled'.
3. Enable Single-root input/output virtualization: In the BIOS, go to Advanced/North Bridge Configuration ->SR-IOV and set to 'enabled'.
4. Go to the Jungle that is called LHC@Home Forum and try to find what else these paranoids have thought of to prevent you from running LHC and/or LHCathome-dev

On the bright side: Rosetta and Ralph might be far less picky.