VM runtime doesn't catch all VM issues upon start of provider

[cryptobench]

With the launch of the facelifted stats page we introduced a table that shows the providers list of reputation tasks and their status. Some of these providers reached out to us because they had the error Failed to deploy activity listed. So I sat down and investigated this and got the provider to try out the healthcheck feature of the stats page itself, and that healthcheck task came back with the exact same Failed to deploy activity error message.

Upon further research we found out that the providers who are facing these issues are running the provider in a VM, and it appears that the VM runtime (kvm) is not working properly within that VM.

This essentially means that the initial healtcheck the provider is doing upon start where it checks the VM runtime is not covering all of these problems. One example VM software a person was using was Virtualbox.