Sounds like a bug in the guest driver (vmwgfx) in that case. Although some quick googling for:
"vmwgfx seems to be running on an unsupported hypervisor"
reveals it can be storage related too. I guess because the hypervisor uses similar mechanisms for sharing storage as it does for communicating graphics? One could potentially break the other.
Sounds like a bug in the guest driver (vmwgfx) in that case. Although some quick googling for:
"vmwgfx seems to be running on an unsupported hypervisor"
reveals it can be storage related too. I guess because the hypervisor uses similar mechanisms for sharing storage as it does for communicating graphics? One could potentially break the other.