If your host CPU supports that RDRAND instruction, you won’t experience the problem. That’s why it only hit some people. If the CPU doesn’t, the instruction is emulated in bhyve and if the host runs out of entropy the virtual CPU might be paused for a couple of milliseconds. Linux as a guest doesn’t like that and locks up.
That’s how I understood the problem, I might not have got all the details correct but I should have got the essential mechanism - host pausing to collect entropy, guest CPU pausing in turn.
That’s why we need someone of the original crowd who can reproduce the issue.
The solution is to hack the middleware to add -s 28,virtio-rnd to the bhyve command line and I think that’s really all.
I did not understand the code to be able to correctly add another device. Any takers?
For a quick test - if we find a volunteer, I would hack the VNC configuration section in the middleware to just add the parameter mentioned above in front of the ones for VNC.