Could not open /dev/vmmon

[kamuycikap]

Hi all.

I installed Vmware player 15 on MX Linux 18.
it's complete.
install is no problem.

but I have a problem that run OS image.
i maked OS Image on VMware player 15.

this is the my VMware Player 15 on MX Linux 18.
-> VMware® Workstation 15 Player
-> 15.0.2 build-10952284

I maked VMware Machine Image.
and run VMware Machine also.
so after, there is error message on display.

---------------------
Could not open /dev/vmmon:????????????.
Please make sure that the kernel module 'vmmon' is loaded.
---------------------

I want to run VMware Player 15 machine image on MX Linux 18.

A person who knows the solution method.
Please teach me the solution by all means.

[kamuycikap]

Hi all.

I tried several methods and proceeded to where I started up the machine image.

But I do not know if this is the best solution.

The command I tried is as follows.

---------------
$> sudo vmware-modconfig --console --build-mod vmmon
$> sudo vmware-modconfig --console --build-mod vmnet
$> sudo vmware-modconfig --console --build-mod vmci
$> sudo modprobe vmmon
$> sudo modprobe vmnet
$> sudo service vmware restart
---------------

In addition, I opened the BIOS of my PC and activated Virtualization Technology (VT - X).

In this way, the virtual machine starts up, but the

$ > sudo service vmware restart

command is required every time the PC is restarted.
On MX Linux 18, VMWare Player 15 does not seem to work easily.

[dolphin_oracle]

Try

update-rcd.d vmware enable


To get the service to start at boot. This assumes the vmware startup script contins the necessary sysvinit information.

[kamuycikap]

Hi averyone.

I could not solve the problem.
I uninstall VMWare once.
I tried installing again.

As a result, VMware worked without any problem.

I thought about the possibility that something failed when I installed it.
I will write my point of thought.

No. 1 Enable Virtualization Technology (VT - X).
No. 2 Install the OS to create the virtual machine.
No. 3 Install VMWare Tools.
No 4. Run the installer as root.

Anyway, I was able to solve the problem by uninstalling VMware once and installing it again.

[kamuycikap]

Hi all.

I wrote that in the last writing I completely solved the problem.
But now, I have learned that it was wrong.

Shutting down the PC will cause the problem to recur.

$ > sudo service vmware restart

This command is required.
Every time I restart it I need it every time.

The command mr dolphin_oracle taught can not be executed.
It is displayed that there is no such command.

$ > update-rcd.d vmware enable

MX Linux 18 seems to be difficult to operate VMWare without problems.

[dolphin_oracle]

you will need to be sudo sorry.

Code: Select all

sudo update-rc.d vmware enable

[kamuycikap]

thanks a lot dolphin_oracle.

I tryed your command.
it is run that no probrem.

but....

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.
---------------------

Is there anyone other than me who install VMWare Workstation Player 15 on MX Linux 18?
Are they able to start virtual machines without problems?

I am very mysterious.

[meremortal]

The following advice from jurgen69 worked perfectly for me with MX18...

Jurgen69 solved this for me...it works perfectly and survives reboot;

"that is the fix -> vmware-modconfig --console --install-all
if you open rc.local what is in ect/ rc.local is not a map (its a file) open it and just add this string above exit and it wil work.

you can do that in the terminal or you open it with sudo nautilus and do it manual (that is what i do) "
Top

[ludolph]

May I ask, what is the current status of the "Could not open /dev/vmmon" problem on MX 18.1?

Is the command:

Code: Select all

vmware-modconfig --console --install-all

really sufficient to solve this problem and survive next reboot? I am afraid that only so far known solution is run this command again and again after each reboot ... so this is not solution which I am looking for.

[Thomas T]

There is the same problem in Mx 19.
Has anyone solved the problem with VMware ?