2 ms·
> If it were, then VMX drivers would not be able to coexist with each other. Most VMX drivers are unable to coexist (in the sense that VirtualBox, HAXM, Hyper-
by mappu 8y ago
> If it were, then VMX drivers would not be able to coexist with each other.
Most VMX drivers are unable to coexist (in the sense that VirtualBox, HAXM, Hyper-V, and VMWare Player are mutually incompatible / can't be used in the same Windows boot session).
- souprock 8y agoI just checked a proprietary VMX driver. It fully disables VMX before turning interrupts back on. If I remember right, it works fine with VMWare running on the same machine, so they must be doing likewise. I think I recall problems with Hyper-V, so you are probably right about that one. It looks like Hyper-V is the uncooperative VMX driver that refuses to play nice with others.