Page 2 of 2
Re: Could not open /dev/vmmon
Posted: Wed Nov 06, 2019 3:56 am
by JayM
As VMware's website says the supported Linux distros for their Workstation Player commercial product are
Host Operating Systems (64-bit)
Ubuntu 14.04 and above
Red Hat Enterprise Linux 6 & above
CentOS 6.0 and above
Oracle Linux 6.0 and above
openSUSE Leap 42.2 and above
SUSE Linux 12 and above
I suggest you guys contact them and ask when a version for Debian Stable 10 (Buster) will be available, because as of now VMware Player isn't compatable with Debian, only with the distros listed above. Presumably you paid for VMware Player as it's not a Free/Open Source application so your requests for a Debian Buster version should have some weight.
Reference:
https://www.vmware.com/products/workstation-player.html
Re: Could not open /dev/vmmon
Posted: Wed Nov 06, 2019 4:03 am
by ludolph
Thomas T wrote: Wed Nov 06, 2019 3:33 am
There is the same problem in Mx 19.
Has anyone solved the problem with VMware ?
Yes, the problem still persist ... :(
This is the one of reason why I go back to Ubuntu based distros (like Linux Mint 19.x), because VMware is the only virtualization tool which has no problem with full support of Windows 10 (3D acceleration, printer sharing, etc, etc.). VirtualBox has terrible problems with Windows 10.
Re: Could not open /dev/vmmon
Posted: Wed Nov 06, 2019 4:28 am
by BitJam
kamuycikap wrote: Thu Mar 07, 2019 5:27 am
there is a error message after vertual machine power on.
---------------------
Could not open /dev/vmmon:????????????.
Please make sure that the kernel module 'vmmon' is loaded.
---------------------
Since you got it to work once, this shouldn't be too difficult. From the command line try running:
Code: Select all
sudo modprobe vmmon
sudo service vmware restart
If this works and lets you use vmware then edit the file /etc/rc.local as root and add these two lines:
Code: Select all
modprobe vmmon
service vmware restart
This will run those two commands as root when the computer boots.
Re: Could not open /dev/vmmon
Posted: Wed Nov 06, 2019 4:47 am
by JayM
@BitJam: I think I should just stop replying to topics like this. You devs are so cool about figuring out ways and means to get things to work on MX that were never intended to.
