Category Archives: Workstation

VMware, Workstation

VMware Workstation 14: "Error: Not enough physical memory is available to power on this virtual machine with its configured settings."

4 Comments

Problem

When starting a virtual machine on VMware Workstation 14 and Fedora 27 (Kernel 4.13), the following error is displayed, and the virtual machines cannot be started.  However, there is plenty of free memory on the system.

Not enough physical memory is available to power on this virtual machine with its configured settings.

Solution

“vmmon” is the virtual machine monitor kernel module. You need to modify the source file “hostif.c,” and rebuild the kernel module by running:

sudo su
cd /tmp
cp -p /usr/lib/vmware/modules/source/vmmon.tar /usr/lib/vmware/modules/source/vmmon.tar~backup
cp /usr/lib/vmware/modules/source/vmmon.tar .
tar xf vmmon.tar
rm vmmon.tar
wget https://raw.githubusercontent.com/mkubecek/vmware-host-modules/fadedd9c8a4dd23f74da2b448572df95666dfe12/vmmon-only/linux/hostif.c
mv -f hostif.c vmmon-only/linux/hostif.c
tar cf vmmon.tar vmmon-only
rm -rf vmmon-only
mv -f vmmon.tar /usr/lib/vmware/modules/source/vmmon.tar
vmware-modconfig --console --install-all

VMware Workstation should now work and the virtual machine should now start the next time you start it.

My System Configuration

  • VMware Workstation 14 Pro; 14.0.0 build-6661328
  • Fedora 27 x86 64-bit with Kernel 4.13.16-300.fc27.x86_64

References

VMware, Workstation, Workstation 10

VMware Workstation 10: "Error: Could not open /dev/vmmon: No such file or directory. Please make sure that the kernel module vmmon is loaded."

9 Comments

Problem

When starting VMware Workstation, the following error is displayed:

Could not open /dev/vmmon: No such file or directory.
Please make sure that the kernel module `vmmon' is loaded.

Also, virtual machines cannot be started.

Solution

“vmmon” is the virtual machine monitor kernel module. You can rebuid it by running:

sudo vmware-modconfig --console --install-all

Sample output:

Stopping VMware services:
   VMware Authentication Daemon                            [  OK  ]
   VM communication interface socket family                [  OK  ]
   Virtual machine communication interface                 [  OK  ]
   Virtual machine monitor                                 [  OK  ]
   Blocking file system                                    [  OK  ]
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-lea0x8/vmmon-only'
/usr/bin/make -C /lib/modules/2.6.32-504.1.3.el6.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/kernels/2.6.32-504.1.3.el6.x86_64'
  CC [M]  /tmp/modconfig-lea0x8/vmmon-only/linux/driver.o
  CC [M]  /tmp/modconfig-lea0x8/vmmon-only/linux/driverLog.o
  CC [M]  /tmp/modconfig-lea0x8/vmmon-only/linux/hostif.o
  CC [M]  /tmp/modconfig-lea0x8/vmmon-only/common/apic.o
  CC [M]  /tmp/modconfig-lea0x8/vmmon-only/common/comport.o
  CC [M]  /tmp/modconfig-lea0x8/vmmon-only/common/cpuid.o
  CC [M]  /tmp/modconfig-lea0x8/vmmon-only/common/hashFunc.o
  CC [M]  /tmp/modconfig-lea0x8/vmmon-only/common/memtrack.o
  CC [M]  /tmp/modconfig-lea0x8/vmmon-only/common/phystrack.o
  CC [M]  /tmp/modconfig-lea0x8/vmmon-only/common/task.o
  CC [M]  /tmp/modconfig-lea0x8/vmmon-only/common/vmx86.o
  CC [M]  /tmp/modconfig-lea0x8/vmmon-only/vmcore/moduleloop.o
  LD [M]  /tmp/modconfig-lea0x8/vmmon-only/vmmon.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/modconfig-lea0x8/vmmon-only/vmmon.mod.o
  LD [M]  /tmp/modconfig-lea0x8/vmmon-only/vmmon.ko.unsigned
  NO SIGN [M] /tmp/modconfig-lea0x8/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.32-504.1.3.el6.x86_64'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-lea0x8/vmmon-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-lea0x8/vmmon-only'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/modconfig-lea0x8/vmmon-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-lea0x8/vmnet-only'
/usr/bin/make -C /lib/modules/2.6.32-504.1.3.el6.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/kernels/2.6.32-504.1.3.el6.x86_64'
  CC [M]  /tmp/modconfig-lea0x8/vmnet-only/driver.o
  CC [M]  /tmp/modconfig-lea0x8/vmnet-only/hub.o
  CC [M]  /tmp/modconfig-lea0x8/vmnet-only/userif.o
  CC [M]  /tmp/modconfig-lea0x8/vmnet-only/netif.o
  CC [M]  /tmp/modconfig-lea0x8/vmnet-only/bridge.o
  CC [M]  /tmp/modconfig-lea0x8/vmnet-only/procfs.o
  CC [M]  /tmp/modconfig-lea0x8/vmnet-only/smac_compat.o
  CC [M]  /tmp/modconfig-lea0x8/vmnet-only/smac.o
  CC [M]  /tmp/modconfig-lea0x8/vmnet-only/vnetEvent.o
  CC [M]  /tmp/modconfig-lea0x8/vmnet-only/vnetUserListener.o
  LD [M]  /tmp/modconfig-lea0x8/vmnet-only/vmnet.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/modconfig-lea0x8/vmnet-only/vmnet.mod.o
  LD [M]  /tmp/modconfig-lea0x8/vmnet-only/vmnet.ko.unsigned
  NO SIGN [M] /tmp/modconfig-lea0x8/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.32-504.1.3.el6.x86_64'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-lea0x8/vmnet-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-lea0x8/vmnet-only'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/modconfig-lea0x8/vmnet-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-lea0x8/vmblock-only'
/usr/bin/make -C /lib/modules/2.6.32-504.1.3.el6.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/kernels/2.6.32-504.1.3.el6.x86_64'
  CC [M]  /tmp/modconfig-lea0x8/vmblock-only/linux/block.o
  CC [M]  /tmp/modconfig-lea0x8/vmblock-only/linux/control.o
  CC [M]  /tmp/modconfig-lea0x8/vmblock-only/linux/dentry.o
  CC [M]  /tmp/modconfig-lea0x8/vmblock-only/linux/file.o
  CC [M]  /tmp/modconfig-lea0x8/vmblock-only/linux/filesystem.o
  CC [M]  /tmp/modconfig-lea0x8/vmblock-only/linux/inode.o
  CC [M]  /tmp/modconfig-lea0x8/vmblock-only/linux/module.o
  CC [M]  /tmp/modconfig-lea0x8/vmblock-only/linux/stubs.o
/tmp/modconfig-lea0x8/vmblock-only/linux/control.c: In function âExecuteBlockOpâ:
/tmp/modconfig-lea0x8/vmblock-only/linux/control.c:285: warning: assignment from incompatible pointer type
/tmp/modconfig-lea0x8/vmblock-only/linux/control.c:296: warning: passing argument 1 of âputnameâ from incompatible pointer type
include/linux/fs.h:2185: note: expected âstruct filename *â but argument is of type âchar *â
  CC [M]  /tmp/modconfig-lea0x8/vmblock-only/linux/super.o
  LD [M]  /tmp/modconfig-lea0x8/vmblock-only/vmblock.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/modconfig-lea0x8/vmblock-only/vmblock.mod.o
  LD [M]  /tmp/modconfig-lea0x8/vmblock-only/vmblock.ko.unsigned
  NO SIGN [M] /tmp/modconfig-lea0x8/vmblock-only/vmblock.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.32-504.1.3.el6.x86_64'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-lea0x8/vmblock-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-lea0x8/vmblock-only'
cp -f vmblock.ko ./../vmblock.o
make: Leaving directory `/tmp/modconfig-lea0x8/vmblock-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-lea0x8/vmci-only'
/usr/bin/make -C /lib/modules/2.6.32-504.1.3.el6.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/kernels/2.6.32-504.1.3.el6.x86_64'
  CC [M]  /tmp/modconfig-lea0x8/vmci-only/linux/driver.o
  CC [M]  /tmp/modconfig-lea0x8/vmci-only/linux/vmciKernelIf.o
  CC [M]  /tmp/modconfig-lea0x8/vmci-only/common/vmciContext.o
  CC [M]  /tmp/modconfig-lea0x8/vmci-only/common/vmciDatagram.o
  CC [M]  /tmp/modconfig-lea0x8/vmci-only/common/vmciDoorbell.o
  CC [M]  /tmp/modconfig-lea0x8/vmci-only/common/vmciDriver.o
  CC [M]  /tmp/modconfig-lea0x8/vmci-only/common/vmciEvent.o
  CC [M]  /tmp/modconfig-lea0x8/vmci-only/common/vmciHashtable.o
  CC [M]  /tmp/modconfig-lea0x8/vmci-only/common/vmciQPair.o
  CC [M]  /tmp/modconfig-lea0x8/vmci-only/common/vmciQueuePair.o
  CC [M]  /tmp/modconfig-lea0x8/vmci-only/common/vmciResource.o
  CC [M]  /tmp/modconfig-lea0x8/vmci-only/common/vmciRoute.o
  CC [M]  /tmp/modconfig-lea0x8/vmci-only/driverLog.o
  LD [M]  /tmp/modconfig-lea0x8/vmci-only/vmci.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/modconfig-lea0x8/vmci-only/vmci.mod.o
  LD [M]  /tmp/modconfig-lea0x8/vmci-only/vmci.ko.unsigned
  NO SIGN [M] /tmp/modconfig-lea0x8/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.32-504.1.3.el6.x86_64'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-lea0x8/vmci-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-lea0x8/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/modconfig-lea0x8/vmci-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-lea0x8/vsock-only'
/usr/bin/make -C /lib/modules/2.6.32-504.1.3.el6.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/kernels/2.6.32-504.1.3.el6.x86_64'
  CC [M]  /tmp/modconfig-lea0x8/vsock-only/linux/af_vsock.o
  CC [M]  /tmp/modconfig-lea0x8/vsock-only/linux/notify.o
  CC [M]  /tmp/modconfig-lea0x8/vsock-only/linux/notifyQState.o
  CC [M]  /tmp/modconfig-lea0x8/vsock-only/linux/stats.o
  CC [M]  /tmp/modconfig-lea0x8/vsock-only/linux/util.o
  CC [M]  /tmp/modconfig-lea0x8/vsock-only/linux/vsockAddr.o
  CC [M]  /tmp/modconfig-lea0x8/vsock-only/driverLog.o
  LD [M]  /tmp/modconfig-lea0x8/vsock-only/vsock.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/modconfig-lea0x8/vsock-only/vsock.mod.o
  LD [M]  /tmp/modconfig-lea0x8/vsock-only/vsock.ko.unsigned
  NO SIGN [M] /tmp/modconfig-lea0x8/vsock-only/vsock.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.32-504.1.3.el6.x86_64'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-lea0x8/vsock-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-lea0x8/vsock-only'
cp -f vsock.ko ./../vsock.o
make: Leaving directory `/tmp/modconfig-lea0x8/vsock-only'
Starting VMware services:
   Virtual machine monitor                                 [  OK  ]
   Virtual machine communication interface                 [  OK  ]
   VM communication interface socket family                [  OK  ]
   Blocking file system                                    [  OK  ]
   Virtual ethernet                                        [  OK  ]
   VMware Authentication Daemon                            [  OK  ]
   Shared Memory Available                                 [  OK  ]

VMware Workstation should now work the next time you start it.

My System Configuration

  • VMware Workstation 10.0.4
  • CentOS 6.6 x86 64-bit

References

CentOS, CentOS 6, iTunes, Linux, VMware, Windows, Windows 7, Workstation, Workstation 10

VMware Workstation 10 on CentOS 6 Host with Windows 7 Guest Running iTunes

1 Comment

After installing iTunes on a Windows 7 guest, I would then plug my iPhone into a USB port on my CentOS 6 host. Inside of VMware Workstation 10, I selected the appropriate VM, then from the menu bar I selected VM > Removable Devices > Apple iPhone > Connect (Disconnect from host). This causes VMware to attach this USB device to the Windows guest instead of the CentOS host.
After doing this, I get the following message from VMware: “The Device “Apple iPhone” was not able to connect to its ideal host controller. An attempt will be made to connect this device to the best available host controller. This might result in undefined behavior for this device.”

Go to Start > Devices and Printers. You should see two new devices under the Unspecified section called “Apple Mobile Device USB Driver” and “Apple iPhone”.

Also, if you open up Explorer and go to Computer, you should see your iPhone listed as a Portable Device.

After browsing files on the iPhone within Explorer (using the iPhone as an internal storage device), I get a Windows blue screen including the message “BUGCODE_USB_DRIVER”. The guest machine crashes while the host remains stable.

Alternatively, if I opened iTunes while the iPhone is attached to the Windows guest, iTunes would display the error “iTunes could not connect to the iPhone because an invalid response was received from the device.”

Ultimately, I resolved the majority of my issues by powering off the Windows guest VM, going to VM > Settings > USB Controller >
Change USB Compatibility from USB 1.1 to USB 2.0. Save and restart the VM.
Every once in a while iTunes does not recognize the iPhone. Usually this can be resolved, by removing and re-adding the iPhone or closing and re-opening iTunes. Sometimes by adding the iPhone prior to starting iTunes.
In order for Sync over Wi-Fi to work, the guest Windows VM running iTunes should to have an IP on the same physical network as your iPhone. Power off the guest VM, go to VM > Settings > Network Adapter >
Select “Bridged” instead of “NAT”.

My System Configuration

  • VMware Workstation 10.1
  • Host: CentOS 6.5 x86 64-bit
  • Guest: Windows 7 Professional SP1
  • iTunes 11.1.3.8

References

CentOS, CentOS 6, Linux, VMware, VMware Tools, Windows, Windows 7, Workstation, Workstation 10

CentOS Host OS Crashes When Installing VMware Tools on a Guest OS Within VMware Workstation 10

6 Comments

Installing VMware Tools on a Windows 7 Guest OS in VMware Workstation 10.1 running on a CentOS 6 host always resulted in the host OS crashing.
This appears to be due to a combination of VMware Workstation 10.1 running on CentOS 6 .5 with kernel 2.6.32-431.1.2.0.1.el6.x86_64 #1 SMP x86_64 GNU/Linux. I see these two interesting items on the screen output followed by a call trace.

BUG: scheduling while atomic: vmware/6035/0x000002000
Pid: 6035, comm: vmware Tainted: G D --------- 2.6.32-431.1.2.0.1.el6.x86_64 #1

2013-12-28_vmware-host-crash
To resolve this issue:

# service vmware-workstation-server stop
# service vmware stop
# mv -v /usr/lib/vmware/modules/binary /usr/lib/vmware/modules/binary~orig
# rm /lib/modules/$(uname -r)/misc/v*.ko
# depmod -a
# yum install make gcc keneral-headers-$(uname -r) kernel-devel
# /usr/bin/vmware-modconfig --console --install-all
# service vmware start
# service vmware-workstation-server start

I could now attempt to install VMware Tools on a Windows 7 Guest OS without the host crashing. However, I now ran into another complication. The VMware Tools install would hang around the point of installing the ThinPrint module. Basically, the VMware Tools install hangs due to cruft left over from previous install attempts. Follow VMware KB Article 1001354 to remove cruft left over from previous VMware Tools installs. Then try reinstalling again.
You do not need to repeat this procedure since the offending modules are being removed in the steps above. During subsequent kernel upgrades, modules will be recompiled automatically.
VMware claims that “this issue should be fixed with the next update (10.0.2), and we will publish a kb article.”
UPDATE: The VMware community appears to agree that this issue is resolved in the Workstation 10.0.2 release.

My System Configuration

  • VMware Workstation 10.1
  • Host: CentOS 6.5 x86 64-bit
  • Guest: Windows 7 Professional SP1

References