Virtual machine monitor failed linux

Arch Linux

You are not logged in.

#1 2017-12-11 12:59:47

[SOLVED]VMware Failed to start — vmmon failed — monitor machine failed

Hello
At first if anything about this topic is wrong please accept my apologize

I installed Arch linux and it is updated with last kernel and everything

I want to install vmware but I’m failed with this app
I install all requirements and and one note : I don’t have dkms installed.

At first this is my Kernel :

This is my GCC

I have installed vmware by

After install this is my /etc/init.d

And here is /etc/rc.d/

In the Arch wiki for vmware said you can use vmware-patch or another patcher
But I create 3 system.service in /etc/systemd/system/

3 files in the end and their content is exactly same in vmware page in Arch wiki

When I want to modprobe : vmmon — vmnet — vmci
I get these errors :

Those 2 error and its tell that modules not build yet so I command this like said in Arch wiki in vmware page :

But I will get these :

So it is saying there is no successful taks.

After this I start vmware by command vmware and after a second a windows appear saying it wants to install modules and when i click install it is going to be failed show monitor machine not start and I think its because of modules not install completely.
After say see log in /tmp/vmware-root/vmware-3375.log

So guys sorry for its long but I think its better to be complete.
If anyone know this issue
Help to make this FIX and help Arch Linux to be better.

I did whatever Arch Wili said but no luck.

Last edited by jarvisai (2017-12-14 08:33:24)

$> whoami — Jarvis Mercer | My GitHub — My email address — Telegram-ID — Discord = #0839 — ArchLinux+AsusN552VW-A+MacbookPro2017(TB)

#2 2017-12-11 13:12:33

Re: [SOLVED]VMware Failed to start — vmmon failed — monitor machine failed

Why aren’t you installing using the vmware-workstation package in the AUR?

No, it didn’t «fix» anything. It just shifted the brokeness one space to the right. — jasonwryan
Closing — for deletion; Banning — for muppetry. — jasonwryan

#3 2017-12-11 13:20:47

Re: [SOLVED]VMware Failed to start — vmmon failed — monitor machine failed

I try that and no luck in that way of installing vmware i dont get any link in /etc/init.d and i got error from vmci and vmnet but vmmon is ok.
hmm sorry for bad eng my native is japanese.

so thanks man i think the best way of installing vmware is sh package that what Arch wiki said.
in this way we get symlink in /etc/init.d and we cant get status, start, restart and stop with /etc/init.d/vmware start|stop|restart|status

$> whoami — Jarvis Mercer | My GitHub — My email address — Telegram-ID — Discord = #0839 — ArchLinux+AsusN552VW-A+MacbookPro2017(TB)

#4 2017-12-14 08:31:52

Re: [SOLVED]VMware Failed to start — vmmon failed — monitor machine failed

So after some try about 23 time try installing VMware , finally success
At first I don’t know this is important in success but I install dkms package.
After that I read that log and found that the gcc version is compatiable with these vmware package to compile so i downgrade the gcc to 6
and Try to install but failed again
Then found that there is no need for gcc to compile that vmmon or vmci or others
Compile them by dkms and match the kernel after that success yeah
I finally get vmware on my arch in asus.

But i delete it, hehe
I want to try the AUR package pre mafe for vmware and i install it
Druting installation i found out that this one compile vmware tools by dkms
like me but manually
So i delete it again and install it manually again to keep DIY safe.

Thanks for reading my post
Also Im writing the cheat sheet for installing Arch on Asus laptops , the most trouble laptop for having Arch on them + help of with friend.

Any way thanks
I changed the topic[SOLVED]

$> whoami — Jarvis Mercer | My GitHub — My email address — Telegram-ID — Discord = #0839 — ArchLinux+AsusN552VW-A+MacbookPro2017(TB)

Источник

Virtual machine monitor failed linux

• VMware Technology Network
• :
• Desktop Hypervisor
• :
• VMware Workstation
• :
• VMware Workstation Player Discussions
• :
• Virtual machine monitor failed. Ubuntu 16.04.1 x86.

• Subscribe to RSS Feed
• Mark Topic as New
• Mark Topic as Read
• Float this Topic for Current User
• Bookmark
• Subscribe
• Mute
• Printer Friendly Page

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Email to a Friend
• Report Inappropriate Content

Hi all.
I am a new VM user. First installation and problems ((
Ubuntu 16.04.1 LTS x86_64 4.4.0-31-generic new installation on HP Envy laptop.
New WM player 12.1.1 added via «sudo ./VMware-Player-12.1.1-3770994.x86_64.bundle»
With few errors:

(vmware-installer.py:32115): Gtk-WARNING **: Unable to locate theme engine in module_path: «murrine»,

(vmware-installer.py:32115): Gtk-WARNING **: Unable to locate theme engine in module_path: «murrine»,

(vmware-installer.py:32115): Gtk-WARNING **: Unable to locate theme engine in module_path: «murrine»,

(vmware-installer.py:32115): Gtk-WARNING **: Unable to locate theme engine in module_path: «murrine»,

Gtk-Message: Failed to load module «canberra-gtk-module»: libcanberra-gtk-module.so: cannot open shared object file: No such file or directory

The «vmware-installer» log is attached.

Then adds first VW (with winXP from ISO located at

/Desktop) and when trying to enable it I have got:

Could not open /dev/vmmon: No such file or directory.

Please make sure that the kernel module `vmmon’ is loaded.

Found in Google and tried:

Virtual machine monitor failed

Virtual machine communication interface done

VM communication interface socket family done

Blocking file system done

Virtual ethernet failed

VMware Authentication Daemon done

The full log in attachment.

Will provide all necessary info.
Thank you in advance.

Источник

Virtual machine monitor failed linux

• VMware Technology Network
• :
• Desktop Hypervisor
• :
• VMware Workstation
• :
• VMware Workstation Pro Discussions
• :
• Virtual Machine monitor FAIL, vmware player and .

• Subscribe to RSS Feed
• Mark Topic as New
• Mark Topic as Read
• Float this Topic for Current User
• Bookmark
• Subscribe
• Mute
• Printer Friendly Page

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Email to a Friend
• Report Inappropriate Content

I have been running VMware workstation on my Redhat 64 LINUX workstaation for a long time,

(2.6.32-131.6.1.el6.x86_64 #1 SMP x86_64 x86_64 x86_64 GNU/Linux)

Suddenly last week it stopped working with message » Too many virtual machines are running. The maximum number of running mmachines is 64″

I am not aware of any system change.

when I perform a start of vmware services by «/etc/init.d/vmware start»

I get the status :

Virtual machine monitor [FAILED]

I tried VMplayer, if it fail whth the same issue

I tried to reconfigure VMware by

# vmware-modconfig —console —install-all

all configuration run ok and all services start except

«Virtual machine monitor [FAILED]»

Then I tried to start KVM virtual machine, it use to run but now it fails

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Email to a Friend
• Report Inappropriate Content

I decided to reinstall Linux, rather than using long time to debug the issue,

VMware is running fine agin om my RHEL X86_64 laptop.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Email to a Friend
• Report Inappropriate Content

Some people have suggested disabling Secure Boot.

This didn’t help for me, but might help other people out there facing the same issue.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Email to a Friend
• Report Inappropriate Content

Could you describe your problem with more info, such as workstation version, host OS version, and the steps to reproduce your problem, etc?

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Email to a Friend
• Report Inappropriate Content

I recently had to reinstall my system Debian unstable/sid (Kernel 5.2.9-2) and has been unable to get VMware up and running again.

When starting the application, I’m prompted with a message saying: «Before you can run VMware, several modules must be compiled and loaded into the running kernel.»

I click Install and it just keeps failing on «Virtual Machine Monitor».

I’m then prompted with an error message «Unable to start services. See log file /tmp/vmware-root/vmware-23066.log for details.»

With the command «$ cat vmware-23066.log | grep Failed» (to keep it short), I get these error messages:

2019-09-20T21:44:23.179+02:00| host-23066| I125: [msg.dictionary.load.openFailed] Cannot open file «/usr/lib/vmware/settings»: No such file or directory.

2019-09-20T21:44:23.179+02:00| host-23066| I125: [msg.dictionary.load.openFailed] Cannot open file «/home/chiya/.vmware/config»: No such file or directory.

2019-09-20T21:44:23.179+02:00| host-23066| I125: [msg.dictionary.load.openFailed] Cannot open file «/home/chiya/.vmware/preferences»: No such file or directory.

2019-09-20T21:44:23.365+02:00| host-23066| I125: Failed to find /lib/modules/5.2.0-2-amd64/build/include/linux/version.h

2019-09-20T21:44:23.611+02:00| host-23066| I125: Failed to find /lib/modules/5.2.0-2-amd64/build/include/linux/version.h

2019-09-20T21:44:23.799+02:00| host-23066| I125: Failed to find /lib/modules/5.2.0-2-amd64/build/include/linux/version.h

2019-09-20T21:44:23.818+02:00| host-23066| I125: Failed to find /lib/modules/5.2.0-2-amd64/build/include/linux/version.h

2019-09-20T21:44:23.824+02:00| host-23066| I125: Failed to find /lib/modules/5.2.0-2-amd64/build/include/linux/version.h

2019-09-20T21:44:23.837+02:00| host-23066| I125: Failed to find /lib/modules/5.2.0-2-amd64/build/include/linux/version.h

2019-09-20T21:44:25.853+02:00| host-23066| W115: Failed to build vmmon. Failed to execute the build command.

2019-09-20T21:44:27.685+02:00| host-23066| W115: Failed to build vmnet. Failed to execute the build command.

I have tried disabling secure boot, switching between EFI and legacy, running this command «sudo vmware-modconfig —console —install-all» which also failed.

I also tried 3 different VMware versions.

I’m using «VMware Player 15.0.3 build-12422535»

Источник

VMware/Install Arch Linux as a guest

This article is about installing Arch Linux in a VMware product, such as Player (Plus), Fusion or Workstation.

Contents

In-kernel drivers

• vmw_balloon — The physical memory management driver. It acts like a «balloon» that can be inflated to reclaim physical pages by reserving them in the guest and invalidating them in the monitor, freeing up the underlying machine pages so they can be allocated to other guests. It can also be deflated to allow the guest to use more physical memory. Deallocated Virtual Machine memory can be reused in the host without terminating the guest.
• vmw_pvscsi — For VMware’s Paravirtual SCSI (PVSCSI) HBA.
• vmw_vmci — The Virtual Machine Communication Interface. It enables high-speed communication between host and guest in a virtual environment via the VMCI virtual device.
• vmwgfx — For 3D acceleration. This is a KMS enabled DRM driver for the VMware SVGA2 virtual hardware.
• vmxnet3 — For VMware’s vmxnet3 virtual ethernet NIC.
• a fuse-based hgfs implementation has been added to open-vm-tools 10.0+ and is supported from kernel version 4.0+.

The following drivers are only needed if you are running Arch Linux on a hypervisor like VMware vSphere Hypervisor. Client-server applications can write to the VMCI Sock (vsock) interface to make use of the VMCI virtual device, when communicating between virtual machines.

• vsock — The Virtual Socket Protocol. It is similar to the TCP/IP socket protocol, allowing communication between Virtual Machines and hypervisor or host.
• vmw_vsock_vmci_transport — Implements a VMCI transport for Virtual Sockets.

Some modules, such as the legacy vmhgfs shared folder module, will require additional work to manually compile and systemd enable in order to function properly.

VMware Tools versus Open-VM-Tools

In 2007, VMware released large partitions of the VMware Tools under the LGPL as Open-VM-Tools. The official Tools are not available separately for Arch Linux.

Originally, VMware Tools provided the best drivers for network and storage, combined with the functionality for other features such as time synchronization. However, now the drivers for the network/SCSI adapter are part of the Linux kernel.

The official VMware Tools also had the advantage of being able to use the Unity mode feature, but as of VMWare Workstation 12, Unity mode for Linux guests has been removed due to lack of use and developer difficulties in maintaining the feature. See this thread.

Open-VM-Tools

Utilities

The open-vm-tools package comes with the following utilities:

• vmtoolsd — Service responsible for the Virtual Machine status report.
• vmware-checkvm — Tool to check whether a program is running in the guest.
• vmware-toolbox-cmd — Tool to obtain Virtual Machine information of the host.
• vmware-user — Tool to enable clipboard sharing (copy/paste) between host and guest.
• vmware-vmblock-fuse — Filesystem utility. Enables drag & drop functionality between host and guest through FUSE (Filesystem in Userspace).
• vmware-xferlogs — Dumps logging/debugging information to the Virtual Machine logfile.
• vmhgfs-fuse — Utility for mounting vmhgfs shared folders.

Modules

• vmhgfs — Legacy filesystem driver. Enables legacy sharing implementation between host and guest.
• vmxnet — for the old VMXNET network adapter.

Installation

Install open-vm-tools . If the legacy vmhgfs shared folder module is desired, the open-vm-tools-dkms AUR [broken link: package not found] package must be installed (the new vmhgfs-fuse driver is included in open-vm-tools ). Start and/or enable vmtoolsd.service and vmware-vmblock-fuse.service .

Try to install gtkmm3 manually if it does not work properly. To enable copy and paste between host and guest gtkmm3 is required.

Official VMware Tools

Modules

• vmblock — Filesystem driver. Enables drag & drop functionality between host and guest (superseded by the vmware-vmblock-fuse utility).
• vmci — High performance communication interface between host and guest.
• vmmon — Virtual Machine Monitor.
• vmnet — Networking driver.
• vsock — VMCI sockets.

Installation (from guest)

Install the dependencies: base-devel (for building), net-tools (for ifconfig , used by the installer) and linux-headers (for kernel headers). A make dependency for checking out open-vm-tools is asp .

Then, create bogus init directories for the installer:

The installer can then be mounted:

Extracted (e.g. to /root ):

The following build failures can safely be ignored:

• VMNEXT 3 virtual network card
• «Warning: This script could not find mkinitrd or update-initramfs and cannot remake the initrd file!»
• Fuse components not found on the system.

Enable vmware-vmblock-fuse systemd services (make sure the dependencies are manually installed, or that the -s flag) used. The open-vm-tools source code should be checked out using the Arch Build System.

Reboot the Virtual Machine:

Log in and start the VMware Tools:

Additionally, to auto start vmware-tools on boot, create a new file /etc/systemd/system/vmwaretools.service :

And enable the new systemd service:

Xorg configuration

These packages should be all that are required to get started with booting into a graphical target : . /etc/xdg/autostart/vmware-user.desktop will get started which will set up most of what is needed to work with the Virtual Machine.

However, if booting into multi-user.target or using an uncommon setup (e.g. multiple monitors), then vmtoolsd.service needs to be enabled. In addition to this, edit:

to give permission for loading drivers.

Tips and tricks

Shared Folders with vmhgfs-fuse utility

Share a folder by selecting Edit virtual machine settings > Options > Shared Folders > Always enabled, and creating a new share.

The shared folders should be visible with:

Now the folder can be mounted:

If the error message fusermount: option allow_other only allowed if ‘user_allow_other’ is set in /etc/fuse.conf is displayed, uncomment the following line in /etc/fuse.conf :

Other vmhgfs-fuse mount options can be viewed by using the -h input flag:

fstab

Add a rule for each share:

Create and mount the Shared Folders (if not done so already):

Systemd

Create the following .service :

Ensure the folder exists on the system. If this folder does not exist then it must be created, as the systemd service depends on it:

Enable the — .service mount target.

If all shared folders should be mounted automatically then omit .

Legacy Shared Folders with vmhgfs module

Share a folder by selecting Edit virtual machine settings > Options > Shared Folders > Always enabled, and creating a new share.

Ensure the vmhgfs driver is loaded:

The shared folders should be viewable with:

Now the folder can be mounted:

Enable at boot

Edit mkinitcpio.conf thusly:

fstab

Add a rule for each share:

Create and mount the Shared Folders:

Systemd

For shared folders to work the vmhgfs driver must be loaded. Create the following .service s:

Ensure the folder exists on the system. If this folder does not exist then it must be created, as the systemd scripts depend on it:

Enable the mnt-hgfs.automount mount target.

If all shared folders should be mounted automatically then omit .

Prune mlocate DB

When using mlocate, it is pointless to index the shared directories in the locate DB . Therefore, add the directories to PRUNEPATHS in /etc/updatedb .

3D Acceleration

If not selected at guest creation time, 3D Acceleration can be enabled in: Edit virtual machine settings > Hardware > Display > Accelerate 3D graphics.

OpenGL and GLSL support

It is possible to update OpenGL and GLSL with new kernel modules, overriding Arch-controlled versions.

Currently, OpenGL 3.3 and GLSL 3.30 can be supported. See https://bbs.archlinux.org/viewtopic.php?id=202713 for more details.

Time synchronization

Configuring time synchronization in a Virtual Machine is important; fluctuations are bound to occur more easily in a guest VM. This is mostly due to the CPU being shared by more than one guest.

There are 2 options to set up time synchronization: the host or an external source.

Host machine as time source

To use the host as a time source, ensure vmtoolsd.service is started. Then enable the time synchronization:

To synchronize the guest after suspending the host:

External server as time source

Troubleshooting

Network slow on guest

Arch Linux, as well as other Linux guests, may have slow network speeds while using NAT. To resolve this, switch the network type to Bridged mode in the guest settings on the host, changing the configuration file for the network on the guest where necessary. For more information on configuration, see Network configuration. If on a Windows host and it is not connecting properly despite correct guest configuration, open the Virtual Network Editor on the host as Administrator and press the Restore defaults button at the bottom left.

File share problems with legacy vmhgfs module and newer kernels

As the open-vm-tools-dkms AUR [broken link: package not found] package is no longer being updated, newer kernels are not patched correctly using it to be compatible with a host-guest file share. The Github repository has some patch files that can be manually applied to restore functionality.

It is also recommended that the AUR comment section be checked for this package.

Sound problems

If unacceptably loud or annoying sounds occur, then it may be related to the PC speaker. The issue may be resolved by disabling the PC speaker within the guest image:

Mouse problems

The following problems may occur with the mouse:

• The automatic grab/ungrab feature does not automatically grab input when the cursor enters the window
• Missing buttons
• Input lag
• Clicks are not registered in some applications
• Mouse cursor jumps when entering/leaving virtual machine
• Mouse position jumps to where it left the guest VM

These may be fixed by uninstalling the xf86-input-vmmouse package. xf86-input-vmmouse and xf86-input-libinput should be sufficient for handling mouse and keyboard inputs.

Adding settings to the .vmx configuration file may help (Mouse position jumps to where it left the guest VM):

VMware also attempts to automatically optimize the mouse for gaming. If problems are experienced, disabling the optimization is recommended: Edit > Preferences > Input > Optimize mouse for games: Never

Alternatively, attempting to disable the catchall event in 60-libinput.conf may be required:

Boot problems

Slow boot time

The following errors may be displayed if VMWare’s memory hot-add feature is enabled:

• add_memory failed
• acpi_memory_enable_device() error

Disable the memory hot-add feature by setting mem.hotadd = «FALSE» to the .vmx .

Shutdown/Reboot hangs

Adjust the timeout for the vmtoolsd service (defaults to 90 seconds).

Window resolution autofit problems

«Autofit» means that when the VMWare window’s size is adjusted in the host, ArchLinux in the guest should automatically follow and readjust its resolution to fit the new size of the host window.

Potential solution 1

Ensure autofit is enabled. For VMware Workstation the setting can be found in: View -> Autosize -> Autofit Guest

Potential solution 2

For some reason, autofit requires the packages gtkmm and gtk2, so ensure they are installed. If X windows is not installed or a non–GTK-based desktop environment (such as KDE) is being used, the might have to be installed independently.

Potential solution 3

The relevant modules may have to be added to mkinitcpio.conf:

Potential solution 4

If this does not work, ensure the vmtoolsd.service is restarted.

Potential solution 5

Drag and drop, copy/paste

The drag-and-drop (copy/paste) feature requires both open-vm-tools and gtkmm3 packages to be installed.

Make the command vmware-user run after X11 by either:

• Ensuring etc/xdg/autostart/vmware-user.desktop exists, and if not, running:

Problems when running as a shared VM on Workstation 11

Workstation 11 has a bug where vmware-hostd crashes if an Arch guest is running as a shared VM and vmtoolsd is running in the guest. A patch to open-vm-tools to work around the bug is here.

Shared folder not mounted after system upgrade

Most likely, this should only happen to open-vm-tools . Since the vmhgfs module belongs to open-vm-tools-dkms AUR [broken link: package not found] , the legacy filesystem driver would not be upgraded by using the command pacman -Syu . Therefore, open-vm-tools-dkms AUR [broken link: package not found] should be manually upgraded before the official repositories.

If a shared folder is not mounted after a system upgrade, then remove the shared filesystem automount, upgrade open-vm-tools-dkms AUR [broken link: package not found] , run pacman -Syu , and finally regenerate the initramfs. Do not forget to restore the filesystem automount.

Источник