I would wait until the fix is in, commonly, in a virtual terminal, you should have the ability to install any kernel module needed from an additional device (commonly a mounted additional USB disk) which should be done before the main thread looks for disks.but if denied that then vitrtualizing FreePBX over another layer of virtualization is probably not going to be optimal.
I would also suggest that LXD/LXC would also be a more ‘metal based’ solution’ if you can’t wait. Or use one of the many recipes to install in the WIKI that bypasses the “Distro”
noMachine does not use any server…you have to do a port forwarding to access it from outside. I dont know how safe it is. I have been using it for two years now on 5 Linux Mint NUC PCs with freePBX VMs. No issues yet…
It is not widely used (which is good) and it’s free. Teamviewer is not free anymore, VNC is very old…so I think it is a good alternative.
What do you mean by “but if denied that then vitrtualizing FreePBX over another layer of virtualization is probably not going to be optimal.”
If he installs an OS, which properly recognizes his hardware (e.g. Linux Mint), there are no two layers of virtualization. It is just Virtualbox…and Virtualbox sometimes runs operating systems faster and better than some hardware systems…except for the graphics…but you dont need much graphic power for freePBX
Windows 10/11 as host for a VM is not a good choice, because it updates like hell…and doesnt even ask.
Sorry for the repetition…Linux Mint + Virtualbox.
An Ubuntu-based Linux distro like Linux Mint is stable, asks before it runs updates and runs on most HW.
NoMachine has been around a long time, another advantage of it is that it works quite well over low bandwidth connections - though who needs that these days?!
Though was barely useable over Iridium satellite connections at about 9600 baud the last time I was doing that years ago. I think the high latency of the satellite connection was the main source of the slowness…