Hello,

I recently installed VMWare Workstation Player 14 on my Linux workstation to run a Windows 10 development machine. The option to install VMware Tools in the Virtual Machine menu was greyed out and inaccessible, despite having already downloaded the Tools ISO's. Thinking this was due to using Player as an unlicensed non-commercial application, I purchased a license to try and remedy this (I need OpenGL support for what I'm working on). After licensing the app, this menu option was still greyed out. Then I realized that I could mount the ISO through the DVD Drive and install the tools this way. Doing so worked, but I would like to know if this required a license in the first place. As a student, $156 isn't chump change and would like to put in a refund/cancellation if a license is not required as I'm not doing any commercial work.

The only reason I could think of this menu option not activating itself is that I installed in a non-default directory, using /usr/local/bin and /usr/local/lib. Any direction on the above topic would be greatly appreciated!

Cheers,

Mike

Hi! I'm trying VMware Workstation for the first time at home and I'm having trouble.

When I try to start up any virtual machine it immediately crashes the host machine without a blue screen (so no crash dump). The crash behavior is either an immediate restart, or it just freezes and locks up.

I'm at a loss here, I'm not sure what could be causing this and without any logs I'm not sure where to start troubleshooting. If you have any suggestions I would greatly appreciate it!

Some basic information of my system:
Windows 7 SP1

Intel i5

8Gb Ram

Samsung SSD 850 EVO

Vmware Workstation 14.1.1 build-7528167

Dear all,

I am on Debian 9 and vmware player 14.

I open a shell and execute the following:

% vmplayer

The following output is displayed:

> [AppLoader] Use shipped Linux kernel AIO access library.

> An up-to-date "libaio" or "libaio1" package from your system is preferred.

A vmware window is also displayed (see attached document)

Does anyone had this problem before? Can someone suggest me smth to solve the problem?

Thanks.

Since I upgraded from Player 12 to Player 14 on my Ubuntu 16.04 host, I was having issues with a Windows 7 Pro guest not shutting down properly some of the time. I would initiate a shutdown from within Windows and this appeared to have the desired effect. However the next time I opened the guest it would seem to sometimes pick up on an incomplete hibernation sequence and then begin shutting down the guest. A further attempt to open the guest would then succeed but only after a recovery from hibernation.

I discovered that the behaviour described above only happened when the notebook was powered from batteries. When connected to mains power the guest operated normally. I eventually solved the problem by setting Windows 7 such that it never commences a shutdown when on batteries. This is easier said than done because Windows 7 does not provide for this option within the gui interface. To achieve this you need to issue the following command from the command prompt:

“powercfg -setdcvalueindex SCHEME_CURRENT SUB_BATTERY BATACTIONCRIT 0”

I hope this might be helpful to anyone encountering the same issue.

Software : VMware Workstation 12 Player (Version 12.5.8 build-7098237)

Host OS : Windows 10 Home Edition (Version 1709, OS Build 16299.125)

Guest OS : Windows 7 x64

Issue : After updating Windows 10 to Version 1709, all host network adapters disappear in bridged network connection setting.

I had tried 3 solutions found on web, but all failed :

1. Remove the network adapter in "Device Manage" of host. Re-boot host.

2. Download VMware-workstation-full-12.5.8-7098237 and install it at another PC. Then, I can get "vmnetcfg.exe".

    Copy "vmnetcfg.exe" to host:\VMware\VMware Player\ and execute it.

    Execute "Restore Defaults" in "vmnetcfg.exe".

3. Uninstall VMware Workstation 12 Player, and then install it.

Does anyone has solutions? Thanks a lot.

(I think re-installing Host OS could solve this issue. This is the final choice. I do not want to do that.)

Hi,

Recently i resumed my VM from suspended mode. However, i encountered colorful lines on the VM window.

When i check the log file, i got the following BSOD lines:

2018-02-01T17:59:00.996+08:00| vcpu-0| I125: CPT: vmstart

2018-02-01T17:59:00.996+08:00| vcpu-1| I125: CPT: vmstart

2018-02-01T17:59:00.999+08:00| vcpu-1| W115: WinBSOD: Synthetic MSR[0x40000100] 0x4e

2018-02-01T17:59:00.999+08:00| vcpu-1| W115:

2018-02-01T17:59:00.999+08:00| vcpu-1| W115: WinBSOD: Synthetic MSR[0x40000101] 0x99

2018-02-01T17:59:00.999+08:00| vcpu-1| W115:

2018-02-01T17:59:00.999+08:00| vcpu-1| W115: WinBSOD: Synthetic MSR[0x40000102] 0x421

2018-02-01T17:59:00.999+08:00| vcpu-1| W115:

2018-02-01T17:59:00.999+08:00| vcpu-1| W115: WinBSOD: Synthetic MSR[0x40000103] 0x2

2018-02-01T17:59:00.999+08:00| vcpu-1| W115:

2018-02-01T17:59:00.999+08:00| vcpu-1| W115: WinBSOD: Synthetic MSR[0x40000104] 0x60001e0001ea82d

Like to check anyone faced the same issue?

My VM Windows is Windows 10.

Linux Ubuntu1710 4.15.1-041501-generic #201802031831 SMP Sat Feb 3 18:32:13 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

more  /tmp/vmware-root/vmware-22734.log

2018-02-06T18:04:22.376+01:00| vthread-1| I125: Log for VMware Workstation pid=22734 version=14.0.0 build=build-6661328 option=Release

2018-02-06T18:04:22.376+01:00| vthread-1| I125: The process is 64-bit.

2018-02-06T18:04:22.376+01:00| vthread-1| I125: Host codepage=UTF-8 encoding=UTF-8

2018-02-06T18:04:22.376+01:00| vthread-1| I125: Host is Linux 4.15.1-041501-generic Ubuntu 17.10

2018-02-06T18:04:22.376+01:00| vthread-1| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No existe el archivo o el directorio.

2018-02-06T18:04:22.376+01:00| vthread-1| I125: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": No existe el archivo o el directorio.

2018-02-06T18:04:22.376+01:00| vthread-1| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.

2018-02-06T18:04:22.376+01:00| vthread-1| I125: DictionaryLoad: Cannot open file "/home/jesus/.vmware/config": No existe el archivo o el directorio.

2018-02-06T18:04:22.376+01:00| vthread-1| I125: [msg.dictionary.load.openFailed] Cannot open file "/home/jesus/.vmware/config": No existe el archivo o el directorio.

2018-02-06T18:04:22.376+01:00| vthread-1| I125: PREF Optional preferences file not found at /home/jesus/.vmware/config. Using default values.

2018-02-06T18:04:22.422+01:00| vthread-1| W115: Logging to /tmp/vmware-root/vmware-22734.log

2018-02-06T18:04:22.430+01:00| vthread-1| I125: Obtaining info using the running kernel.

2018-02-06T18:04:22.430+01:00| vthread-1| I125: Created new pathsHash.

2018-02-06T18:04:22.430+01:00| vthread-1| I125: Setting header path for 4.15.1-041501-generic to "/lib/modules/4.15.1-041501-generic/build/include".

2018-02-06T18:04:22.430+01:00| vthread-1| I125: Validating path "/lib/modules/4.15.1-041501-generic/build/include" for kernel release "4.15.1-041501-generic".

2018-02-06T18:04:22.430+01:00| vthread-1| I125: Failed to find /lib/modules/4.15.1-041501-generic/build/include/linux/version.h

2018-02-06T18:04:22.430+01:00| vthread-1| I125: /lib/modules/4.15.1-041501-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2018-02-06T18:04:22.430+01:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check

2018-02-06T18:04:22.435+01:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.15.1-041501-generic".

2018-02-06T18:04:22.435+01:00| vthread-1| I125: The header path "/lib/modules/4.15.1-041501-generic/build/include" for the kernel "4.15.1-041501-generic" is valid.  Whoohoo!

2018-02-06T18:04:22.572+01:00| vthread-1| I125: found symbol version file /lib/modules/4.15.1-041501-generic/build/Module.symvers

2018-02-06T18:04:22.572+01:00| vthread-1| I125: Reading symbol versions from /lib/modules/4.15.1-041501-generic/build/Module.symvers.

2018-02-06T18:04:22.590+01:00| vthread-1| I125: Read 22351 symbol versions

2018-02-06T18:04:22.590+01:00| vthread-1| I125: Reading in info for the vmmon module.

2018-02-06T18:04:22.590+01:00| vthread-1| I125: Reading in info for the vmnet module.

2018-02-06T18:04:22.590+01:00| vthread-1| I125: Reading in info for the vmblock module.

2018-02-06T18:04:22.590+01:00| vthread-1| I125: Reading in info for the vmci module.

2018-02-06T18:04:22.590+01:00| vthread-1| I125: Reading in info for the vsock module.

2018-02-06T18:04:22.590+01:00| vthread-1| I125: Setting vsock to depend on vmci.

2018-02-06T18:04:22.590+01:00| vthread-1| I125: Invoking modinfo on "vmmon".

2018-02-06T18:04:22.592+01:00| vthread-1| I125: "/sbin/modinfo" exited with status 256.

2018-02-06T18:04:22.592+01:00| vthread-1| I125: Invoking modinfo on "vmnet".

2018-02-06T18:04:22.593+01:00| vthread-1| I125: "/sbin/modinfo" exited with status 0.

2018-02-06T18:04:22.593+01:00| vthread-1| I125: Invoking modinfo on "vmblock".

2018-02-06T18:04:22.595+01:00| vthread-1| I125: "/sbin/modinfo" exited with status 256.

2018-02-06T18:04:22.595+01:00| vthread-1| I125: Invoking modinfo on "vmci".

2018-02-06T18:04:22.596+01:00| vthread-1| I125: "/sbin/modinfo" exited with status 256.

2018-02-06T18:04:22.596+01:00| vthread-1| I125: Invoking modinfo on "vsock".

2018-02-06T18:04:22.597+01:00| vthread-1| I125: "/sbin/modinfo" exited with status 0.

2018-02-06T18:04:22.609+01:00| vthread-1| I125: to be installed: vmmon status: 0

2018-02-06T18:04:22.626+01:00| vthread-1| I125: Obtaining info using the running kernel.

2018-02-06T18:04:22.626+01:00| vthread-1| I125: Setting header path for 4.15.1-041501-generic to "/lib/modules/4.15.1-041501-generic/build/include".

2018-02-06T18:04:22.626+01:00| vthread-1| I125: Validating path "/lib/modules/4.15.1-041501-generic/build/include" for kernel release "4.15.1-041501-generic".

2018-02-06T18:04:22.626+01:00| vthread-1| I125: Failed to find /lib/modules/4.15.1-041501-generic/build/include/linux/version.h

2018-02-06T18:04:22.626+01:00| vthread-1| I125: /lib/modules/4.15.1-041501-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2018-02-06T18:04:22.626+01:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check

2018-02-06T18:04:22.631+01:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.15.1-041501-generic".

2018-02-06T18:04:22.631+01:00| vthread-1| I125: The header path "/lib/modules/4.15.1-041501-generic/build/include" for the kernel "4.15.1-041501-generic" is valid.  Whoohoo!

2018-02-06T18:04:22.769+01:00| vthread-1| I125: found symbol version file /lib/modules/4.15.1-041501-generic/build/Module.symvers

2018-02-06T18:04:22.769+01:00| vthread-1| I125: Reading symbol versions from /lib/modules/4.15.1-041501-generic/build/Module.symvers.

2018-02-06T18:04:22.787+01:00| vthread-1| I125: Read 22351 symbol versions

2018-02-06T18:04:22.787+01:00| vthread-1| I125: Kernel header path retrieved from FileEntry: /lib/modules/4.15.1-041501-generic/build/include

2018-02-06T18:04:22.787+01:00| vthread-1| I125: Update kernel header path to /lib/modules/4.15.1-041501-generic/build/include

2018-02-06T18:04:22.787+01:00| vthread-1| I125: Validating path "/lib/modules/4.15.1-041501-generic/build/include" for kernel release "4.15.1-041501-generic".

2018-02-06T18:04:22.787+01:00| vthread-1| I125: Failed to find /lib/modules/4.15.1-041501-generic/build/include/linux/version.h

2018-02-06T18:04:22.787+01:00| vthread-1| I125: /lib/modules/4.15.1-041501-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2018-02-06T18:04:22.787+01:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check

2018-02-06T18:04:22.793+01:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.15.1-041501-generic".

2018-02-06T18:04:22.793+01:00| vthread-1| I125: The header path "/lib/modules/4.15.1-041501-generic/build/include" for the kernel "4.15.1-041501-generic" is valid.  Whoohoo!

2018-02-06T18:04:22.794+01:00| vthread-1| I125: Found compiler at "/usr/bin/gcc"

2018-02-06T18:04:22.796+01:00| vthread-1| I125: Got gcc version "7".

2018-02-06T18:04:22.796+01:00| vthread-1| I125: The GCC version matches the kernel GCC minor version like a glove.

2018-02-06T18:04:22.798+01:00| vthread-1| I125: Got gcc version "7".

2018-02-06T18:04:22.798+01:00| vthread-1| I125: The GCC version matches the kernel GCC minor version like a glove.

2018-02-06T18:04:22.799+01:00| vthread-1| I125: Trying to find a suitable PBM set for kernel "4.15.1-041501-generic".

2018-02-06T18:04:22.799+01:00| vthread-1| I125: No matching PBM set was found for kernel "4.15.1-041501-generic".

2018-02-06T18:04:22.799+01:00| vthread-1| I125: The GCC version matches the kernel GCC minor version like a glove.

2018-02-06T18:04:22.799+01:00| vthread-1| I125: Validating path "/lib/modules/4.15.1-041501-generic/build/include" for kernel release "4.15.1-041501-generic".

2018-02-06T18:04:22.799+01:00| vthread-1| I125: Failed to find /lib/modules/4.15.1-041501-generic/build/include/linux/version.h

2018-02-06T18:04:22.799+01:00| vthread-1| I125: /lib/modules/4.15.1-041501-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2018-02-06T18:04:22.799+01:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check

2018-02-06T18:04:22.805+01:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.15.1-041501-generic".

2018-02-06T18:04:22.805+01:00| vthread-1| I125: The header path "/lib/modules/4.15.1-041501-generic/build/include" for the kernel "4.15.1-041501-generic" is valid.  Whoohoo!

2018-02-06T18:04:22.806+01:00| vthread-1| I125: The GCC version matches the kernel GCC minor version like a glove.

2018-02-06T18:04:22.806+01:00| vthread-1| I125: Validating path "/lib/modules/4.15.1-041501-generic/build/include" for kernel release "4.15.1-041501-generic".

2018-02-06T18:04:22.806+01:00| vthread-1| I125: Failed to find /lib/modules/4.15.1-041501-generic/build/include/linux/version.h

2018-02-06T18:04:22.806+01:00| vthread-1| I125: /lib/modules/4.15.1-041501-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2018-02-06T18:04:22.806+01:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check

2018-02-06T18:04:22.812+01:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.15.1-041501-generic".

2018-02-06T18:04:22.812+01:00| vthread-1| I125: The header path "/lib/modules/4.15.1-041501-generic/build/include" for the kernel "4.15.1-041501-generic" is valid.  Whoohoo!

2018-02-06T18:04:22.812+01:00| vthread-1| I125: Using temp dir "/tmp".

2018-02-06T18:04:22.813+01:00| vthread-1| I125: Obtaining info using the running kernel.

2018-02-06T18:04:22.813+01:00| vthread-1| I125: Setting header path for 4.15.1-041501-generic to "/lib/modules/4.15.1-041501-generic/build/include".

2018-02-06T18:04:22.813+01:00| vthread-1| I125: Validating path "/lib/modules/4.15.1-041501-generic/build/include" for kernel release "4.15.1-041501-generic".

2018-02-06T18:04:22.813+01:00| vthread-1| I125: Failed to find /lib/modules/4.15.1-041501-generic/build/include/linux/version.h

2018-02-06T18:04:22.813+01:00| vthread-1| I125: /lib/modules/4.15.1-041501-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2018-02-06T18:04:22.813+01:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check

2018-02-06T18:04:22.819+01:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.15.1-041501-generic".

2018-02-06T18:04:22.819+01:00| vthread-1| I125: The header path "/lib/modules/4.15.1-041501-generic/build/include" for the kernel "4.15.1-041501-generic" is valid.  Whoohoo!

2018-02-06T18:04:22.956+01:00| vthread-1| I125: found symbol version file /lib/modules/4.15.1-041501-generic/build/Module.symvers

2018-02-06T18:04:22.956+01:00| vthread-1| I125: Reading symbol versions from /lib/modules/4.15.1-041501-generic/build/Module.symvers.

2018-02-06T18:04:22.974+01:00| vthread-1| I125: Read 22351 symbol versions

2018-02-06T18:04:22.974+01:00| vthread-1| I125: Invoking modinfo on "vmmon".

2018-02-06T18:04:22.976+01:00| vthread-1| I125: "/sbin/modinfo" exited with status 256.

2018-02-06T18:04:23.654+01:00| vthread-1| I125: Setting destination path for vmmon to "/lib/modules/4.15.1-041501-generic/misc/vmmon.ko".

2018-02-06T18:04:23.654+01:00| vthread-1| I125: Extracting the vmmon source from "/usr/lib/vmware/modules/source/vmmon.tar".

2018-02-06T18:04:23.662+01:00| vthread-1| I125: Successfully extracted the vmmon source.

2018-02-06T18:04:23.662+01:00| vthread-1| I125: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-DYA5SO/vmmon-only auto-build HEADER_DIR=/lib/modules/4.15.1-041501-generic/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2018-02-06T18:04:25.064+01:00| vthread-1| W115: Failed to build vmmon.  Failed to execute the build command.

In Windows 10 64 bits Professional as host, I have installed VMware Workstation Player and Windows XP Pro.
With Internet Explorer I can open normal pages (wttp://) but not secure pages (wttps://). And, perhaps for this reason, I cannot activate Windows (I have only 25 days left).
I have tried Bridged Networking and NAT.

Can anybody help me? Thanks in advance.

I have a shortcut that automatically opens WMware Workstation 14 Player and Windows XP Pro:

"C:\Program Files (x86)\VMware\VMware Player\vmplayer.exe" "d:\Documents\Virtual Machines\Windows XP Professional\Windows XP Professional.vmx"

Is there a way to edit this shortcut (or to modify the Settings) in order clicking on the shortcut the virtual machine opens always automatically in Unity Mode?

Thanks in advance for your help.

Hello! I used vmware workstation player 12 with no problem, but after the kernel update i had to install the new version. I use Linux Mint 18.3 Cinnamon x64. The problem is: when i try to create a virtual machine or to open an existing one, the list on the left side remains empty. So i can't edit that virtual machine. And the only way to open it is to manually navigate to the folder where it is created and double click on it( which opens it drectly, so, again, i can't edit it). Have anyone found a solution yet?

Hello,

I'm using:

VMware Player 12.5.9 build 7535481

VMware Tools 10.1.6 build-5214329.

Guest OS is Windows 10 Pro version 1709 build 16299.192

Acording to this https://kb.vmware.com/s/article/1008360 under Resolution topic, step 3:

3. Check that VMware Tools is installed in the virtual machine and running the correct version. The version listed in the toolbox application must match the version of the product hosting the virtual machine. To access the toolbox, double-click the VMware icon in the notification area on the task bar, or run vmware-toolbox in Linux. Some VMware products indicate when the version does not match by displaying a message below the console view. For more information on installing VMware Tools, see Overview of VMware Tools (340).

I tried to update VMware Tools using top bar > Player > Help > Software Updates but get "No pending updates" message.

After that, I tried top bar > Player > Manage > Reinstall VMware Tools then removed VMware Tools and reinstalled it but version/build remains the same.

It seems there's no new VMware Tools version to match VMware Player version as stated in step 3 above.

These version numbers matching is the first thing I'm checking, since I'm having slowness problems (VM extremely slow at startup ).

Thanks for any help.

Attached is a log.

Was on and off before with it now wont do it at all.

I have the latest version.

I did a P2V with vCenter Converter of a Windows 10 Pro laptop to run it as virtual machine.

I booted this new vm in VMware Player 14 but the keyboard is not working while the mouse is ok. I could use the On-Screen keyboard to login but obviously I cannot work only with the On-Screen keyboard. 

Does someone know of a fix to this problem?

Thanks,

I'm not able to start vmplayer on debian 9 testing.

Please help me

I tried:

root@debian:/home/rafal# apt-cache search linux-headers-$(uname -r)

linux-headers-4.14.0-3-amd64 - Header files for Linux 4.14.0-3-amd64

root@debian:/home/rafal# apt-get install linux-headers-$(uname -r)

and now I see:

I replaced the original HD of my Windows 10 64bit PC to a new SSD disk.

VMs I create from scratch on my new SSD drive perform better.

VMs originally created on HD disks and moved to the SSD drive still perform slowly compared to new VMs directrly created on the SSD disk.

What can I to to make my old VMs take advantage from the new SSD drive?

Regards

marius

Hello,

I recently installed VMware Workstation 14 Player on my Linux device. I downloaded the .bundle file and ran the installer without problems. However, when I ran VMware, the kernel module updater appeared (which I assume always happens on the first run). All the modules were shown as installed with the green check mark, but the Virtual Machine Communication Interface alone was not installed. To clarify, all the modules were successfully installed except vmci.

I'm running a distro of Linux called GalliumOS (which is basically just Ubuntu 16.04 with a different UI).

Any help would be greatly appreciated. Thanks!

Here's the log file, if it helps:

2018-02-12T16:41:18.493-05:00| vthread-1| I125: Log for VMware Workstation pid=1733 version=14.0.0 build=build-6661328 option=Release

2018-02-12T16:41:18.493-05:00| vthread-1| I125: The process is 64-bit.

2018-02-12T16:41:18.493-05:00| vthread-1| I125: Host codepage=UTF-8 encoding=UTF-8

2018-02-12T16:41:18.493-05:00| vthread-1| I125: Host is Linux 4.8.17-galliumos GalliumOS 2.1

2018-02-12T16:41:18.492-05:00| vthread-1| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory.

2018-02-12T16:41:18.492-05:00| vthread-1| I125: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": No such file or directory.

2018-02-12T16:41:18.492-05:00| vthread-1| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.

2018-02-12T16:41:18.492-05:00| vthread-1| I125: DictionaryLoad: Cannot open file "/home/chrx/.vmware/config": No such file or directory.

2018-02-12T16:41:18.492-05:00| vthread-1| I125: [msg.dictionary.load.openFailed] Cannot open file "/home/chrx/.vmware/config": No such file or directory.

2018-02-12T16:41:18.492-05:00| vthread-1| I125: PREF Optional preferences file not found at /home/chrx/.vmware/config. Using default values.

2018-02-12T16:41:18.492-05:00| vthread-1| I125: DictionaryLoad: Cannot open file "/home/chrx/.vmware/preferences": No such file or directory.

2018-02-12T16:41:18.492-05:00| vthread-1| I125: [msg.dictionary.load.openFailed] Cannot open file "/home/chrx/.vmware/preferences": No such file or directory.

2018-02-12T16:41:18.492-05:00| vthread-1| I125: PREF Optional preferences file not found at /home/chrx/.vmware/preferences. Using default values.

2018-02-12T16:41:18.624-05:00| vthread-1| W115: Logging to /tmp/vmware-root/vmware-1733.log

2018-02-12T16:41:18.745-05:00| vthread-1| I125: Obtaining info using the running kernel.

2018-02-12T16:41:18.745-05:00| vthread-1| I125: Created new pathsHash.

2018-02-12T16:41:18.745-05:00| vthread-1| I125: Setting header path for 4.8.17-galliumos to "/lib/modules/4.8.17-galliumos/build/include".

2018-02-12T16:41:18.745-05:00| vthread-1| I125: Validating path "/lib/modules/4.8.17-galliumos/build/include" for kernel release "4.8.17-galliumos".

2018-02-12T16:41:18.745-05:00| vthread-1| I125: Failed to find /lib/modules/4.8.17-galliumos/build/include/linux/version.h

2018-02-12T16:41:18.745-05:00| vthread-1| I125: /lib/modules/4.8.17-galliumos/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2018-02-12T16:41:18.745-05:00| vthread-1| I125: using /usr/bin/gcc-5 for preprocess check

2018-02-12T16:41:18.762-05:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.8.17-galliumos".

2018-02-12T16:41:18.762-05:00| vthread-1| I125: The header path "/lib/modules/4.8.17-galliumos/build/include" for the kernel "4.8.17-galliumos" is valid.  Whoohoo!

2018-02-12T16:41:19.073-05:00| vthread-1| I125: found symbol version file /lib/modules/4.8.17-galliumos/build/Module.symvers

2018-02-12T16:41:19.073-05:00| vthread-1| I125: Reading symbol versions from /lib/modules/4.8.17-galliumos/build/Module.symvers.

2018-02-12T16:41:19.116-05:00| vthread-1| I125: Read 14334 symbol versions

2018-02-12T16:41:19.116-05:00| vthread-1| I125: Reading in info for the vmmon module.

2018-02-12T16:41:19.116-05:00| vthread-1| I125: Reading in info for the vmnet module.

2018-02-12T16:41:19.116-05:00| vthread-1| I125: Reading in info for the vmblock module.

2018-02-12T16:41:19.116-05:00| vthread-1| I125: Reading in info for the vmci module.

2018-02-12T16:41:19.116-05:00| vthread-1| I125: Reading in info for the vsock module.

2018-02-12T16:41:19.116-05:00| vthread-1| I125: Setting vsock to depend on vmci.

2018-02-12T16:41:19.116-05:00| vthread-1| I125: Invoking modinfo on "vmmon".

2018-02-12T16:41:19.121-05:00| vthread-1| I125: "/sbin/modinfo" exited with status 256.

2018-02-12T16:41:19.121-05:00| vthread-1| I125: Invoking modinfo on "vmnet".

2018-02-12T16:41:19.125-05:00| vthread-1| I125: "/sbin/modinfo" exited with status 256.

2018-02-12T16:41:19.126-05:00| vthread-1| I125: Invoking modinfo on "vmblock".

2018-02-12T16:41:19.131-05:00| vthread-1| I125: "/sbin/modinfo" exited with status 256.

2018-02-12T16:41:19.131-05:00| vthread-1| I125: Invoking modinfo on "vmci".

2018-02-12T16:41:19.136-05:00| vthread-1| I125: "/sbin/modinfo" exited with status 256.

2018-02-12T16:41:19.136-05:00| vthread-1| I125: Invoking modinfo on "vsock".

2018-02-12T16:41:19.142-05:00| vthread-1| I125: "/sbin/modinfo" exited with status 0.

2018-02-12T16:41:19.162-05:00| vthread-1| I125: to be installed: vmmon status: 0

2018-02-12T16:41:19.162-05:00| vthread-1| I125: to be installed: vmnet status: 0

2018-02-12T16:41:19.162-05:00| vthread-1| I125: to be installed: vmci status: 0

2018-02-12T16:41:19.202-05:00| vthread-1| I125: Obtaining info using the running kernel.

2018-02-12T16:41:19.202-05:00| vthread-1| I125: Setting header path for 4.8.17-galliumos to "/lib/modules/4.8.17-galliumos/build/include".

2018-02-12T16:41:19.202-05:00| vthread-1| I125: Validating path "/lib/modules/4.8.17-galliumos/build/include" for kernel release "4.8.17-galliumos".

2018-02-12T16:41:19.202-05:00| vthread-1| I125: Failed to find /lib/modules/4.8.17-galliumos/build/include/linux/version.h

2018-02-12T16:41:19.202-05:00| vthread-1| I125: /lib/modules/4.8.17-galliumos/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2018-02-12T16:41:19.202-05:00| vthread-1| I125: using /usr/bin/gcc-5 for preprocess check

2018-02-12T16:41:19.214-05:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.8.17-galliumos".

2018-02-12T16:41:19.215-05:00| vthread-1| I125: The header path "/lib/modules/4.8.17-galliumos/build/include" for the kernel "4.8.17-galliumos" is valid.  Whoohoo!

2018-02-12T16:41:19.526-05:00| vthread-1| I125: found symbol version file /lib/modules/4.8.17-galliumos/build/Module.symvers

2018-02-12T16:41:19.526-05:00| vthread-1| I125: Reading symbol versions from /lib/modules/4.8.17-galliumos/build/Module.symvers.

2018-02-12T16:41:19.566-05:00| vthread-1| I125: Read 14334 symbol versions

2018-02-12T16:41:19.567-05:00| vthread-1| I125: Kernel header path retrieved from FileEntry: /lib/modules/4.8.17-galliumos/build/include

2018-02-12T16:41:19.567-05:00| vthread-1| I125: Update kernel header path to /lib/modules/4.8.17-galliumos/build/include

2018-02-12T16:41:19.567-05:00| vthread-1| I125: Validating path "/lib/modules/4.8.17-galliumos/build/include" for kernel release "4.8.17-galliumos".

2018-02-12T16:41:19.567-05:00| vthread-1| I125: Failed to find /lib/modules/4.8.17-galliumos/build/include/linux/version.h

2018-02-12T16:41:19.567-05:00| vthread-1| I125: /lib/modules/4.8.17-galliumos/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2018-02-12T16:41:19.567-05:00| vthread-1| I125: using /usr/bin/gcc-5 for preprocess check

2018-02-12T16:41:19.580-05:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.8.17-galliumos".

2018-02-12T16:41:19.580-05:00| vthread-1| I125: The header path "/lib/modules/4.8.17-galliumos/build/include" for the kernel "4.8.17-galliumos" is valid.  Whoohoo!

2018-02-12T16:41:19.584-05:00| vthread-1| I125: Found compiler at "/usr/bin/gcc"

2018-02-12T16:41:19.592-05:00| vthread-1| I125: Got gcc version "5.4.0".

2018-02-12T16:41:19.592-05:00| vthread-1| I125: The GCC version matches the kernel GCC minor version like a glove.

2018-02-12T16:41:19.598-05:00| vthread-1| I125: Got gcc version "5.4.0".

2018-02-12T16:41:19.598-05:00| vthread-1| I125: The GCC version matches the kernel GCC minor version like a glove.

2018-02-12T16:41:19.603-05:00| vthread-1| I125: Trying to find a suitable PBM set for kernel "4.8.17-galliumos".

2018-02-12T16:41:19.603-05:00| vthread-1| I125: No matching PBM set was found for kernel "4.8.17-galliumos".

2018-02-12T16:41:19.603-05:00| vthread-1| I125: The GCC version matches the kernel GCC minor version like a glove.

2018-02-12T16:41:19.603-05:00| vthread-1| I125: Validating path "/lib/modules/4.8.17-galliumos/build/include" for kernel release "4.8.17-galliumos".

2018-02-12T16:41:19.603-05:00| vthread-1| I125: Failed to find /lib/modules/4.8.17-galliumos/build/include/linux/version.h

2018-02-12T16:41:19.603-05:00| vthread-1| I125: /lib/modules/4.8.17-galliumos/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2018-02-12T16:41:19.603-05:00| vthread-1| I125: using /usr/bin/gcc-5 for preprocess check

2018-02-12T16:41:19.617-05:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.8.17-galliumos".

2018-02-12T16:41:19.617-05:00| vthread-1| I125: The header path "/lib/modules/4.8.17-galliumos/build/include" for the kernel "4.8.17-galliumos" is valid.  Whoohoo!

2018-02-12T16:41:19.620-05:00| vthread-1| I125: The GCC version matches the kernel GCC minor version like a glove.

2018-02-12T16:41:19.621-05:00| vthread-1| I125: Validating path "/lib/modules/4.8.17-galliumos/build/include" for kernel release "4.8.17-galliumos".

2018-02-12T16:41:19.621-05:00| vthread-1| I125: Failed to find /lib/modules/4.8.17-galliumos/build/include/linux/version.h

2018-02-12T16:41:19.621-05:00| vthread-1| I125: /lib/modules/4.8.17-galliumos/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2018-02-12T16:41:19.621-05:00| vthread-1| I125: using /usr/bin/gcc-5 for preprocess check

2018-02-12T16:41:19.635-05:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.8.17-galliumos".

2018-02-12T16:41:19.635-05:00| vthread-1| I125: The header path "/lib/modules/4.8.17-galliumos/build/include" for the kernel "4.8.17-galliumos" is valid.  Whoohoo!

2018-02-12T16:41:19.635-05:00| vthread-1| I125: Using temp dir "/tmp".

2018-02-12T16:41:19.641-05:00| vthread-1| I125: Obtaining info using the running kernel.

2018-02-12T16:41:19.641-05:00| vthread-1| I125: Setting header path for 4.8.17-galliumos to "/lib/modules/4.8.17-galliumos/build/include".

2018-02-12T16:41:19.641-05:00| vthread-1| I125: Validating path "/lib/modules/4.8.17-galliumos/build/include" for kernel release "4.8.17-galliumos".

2018-02-12T16:41:19.641-05:00| vthread-1| I125: Failed to find /lib/modules/4.8.17-galliumos/build/include/linux/version.h

2018-02-12T16:41:19.641-05:00| vthread-1| I125: /lib/modules/4.8.17-galliumos/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2018-02-12T16:41:19.641-05:00| vthread-1| I125: using /usr/bin/gcc-5 for preprocess check

2018-02-12T16:41:19.658-05:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.8.17-galliumos".

2018-02-12T16:41:19.658-05:00| vthread-1| I125: The header path "/lib/modules/4.8.17-galliumos/build/include" for the kernel "4.8.17-galliumos" is valid.  Whoohoo!

2018-02-12T16:41:19.967-05:00| vthread-1| I125: found symbol version file /lib/modules/4.8.17-galliumos/build/Module.symvers

2018-02-12T16:41:19.968-05:00| vthread-1| I125: Reading symbol versions from /lib/modules/4.8.17-galliumos/build/Module.symvers.

2018-02-12T16:41:20.008-05:00| vthread-1| I125: Read 14334 symbol versions

2018-02-12T16:41:20.008-05:00| vthread-1| I125: Invoking modinfo on "vmmon".

2018-02-12T16:41:20.013-05:00| vthread-1| I125: "/sbin/modinfo" exited with status 256.

2018-02-12T16:41:20.013-05:00| vthread-1| I125: Invoking modinfo on "vmnet".

2018-02-12T16:41:20.018-05:00| vthread-1| I125: "/sbin/modinfo" exited with status 256.

2018-02-12T16:41:20.018-05:00| vthread-1| I125: Invoking modinfo on "vmci".

2018-02-12T16:41:20.023-05:00| vthread-1| I125: "/sbin/modinfo" exited with status 256.

2018-02-12T16:41:20.505-05:00| vthread-1| I125: Setting destination path for vmmon to "/lib/modules/4.8.17-galliumos/misc/vmmon.ko".

2018-02-12T16:41:20.505-05:00| vthread-1| I125: Extracting the vmmon source from "/usr/lib/vmware/modules/source/vmmon.tar".

2018-02-12T16:41:20.547-05:00| vthread-1| I125: Successfully extracted the vmmon source.

2018-02-12T16:41:20.547-05:00| vthread-1| I125: Building module with command "/usr/bin/make -j2 -C /tmp/modconfig-EgD6A9/vmmon-only auto-build HEADER_DIR=/lib/modules/4.8.17-galliumos/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2018-02-12T16:41:26.959-05:00| vthread-1| I125: Successfully built vmmon.  Module is currently at "/tmp/modconfig-EgD6A9/vmmon.o".

2018-02-12T16:41:26.959-05:00| vthread-1| I125: Found the vmmon symvers file at "/tmp/modconfig-EgD6A9/vmmon-only/Module.symvers".

2018-02-12T16:41:26.959-05:00| vthread-1| I125: Installing vmmon from /tmp/modconfig-EgD6A9/vmmon.o to /lib/modules/4.8.17-galliumos/misc/vmmon.ko.

2018-02-12T16:41:26.960-05:00| vthread-1| I125: Registering file "/lib/modules/4.8.17-galliumos/misc/vmmon.ko".

2018-02-12T16:41:27.710-05:00| vthread-1| I125: "/usr/lib/vmware-installer/2.1.0/vmware-installer" exited with status 0.

2018-02-12T16:41:27.711-05:00| vthread-1| I125: Registering file "/usr/lib/vmware/symvers/vmmon-4.8.17-galliumos".

2018-02-12T16:41:28.369-05:00| vthread-1| I125: "/usr/lib/vmware-installer/2.1.0/vmware-installer" exited with status 0.

2018-02-12T16:41:28.374-05:00| vthread-1| I125: Setting destination path for vmnet to "/lib/modules/4.8.17-galliumos/misc/vmnet.ko".

2018-02-12T16:41:28.374-05:00| vthread-1| I125: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar".

2018-02-12T16:41:28.393-05:00| vthread-1| I125: Successfully extracted the vmnet source.

2018-02-12T16:41:28.393-05:00| vthread-1| I125: Building module with command "/usr/bin/make -j2 -C /tmp/modconfig-EgD6A9/vmnet-only auto-build HEADER_DIR=/lib/modules/4.8.17-galliumos/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2018-02-12T16:41:36.671-05:00| vthread-1| I125: Successfully built vmnet.  Module is currently at "/tmp/modconfig-EgD6A9/vmnet.o".

2018-02-12T16:41:36.671-05:00| vthread-1| I125: Found the vmnet symvers file at "/tmp/modconfig-EgD6A9/vmnet-only/Module.symvers".

2018-02-12T16:41:36.671-05:00| vthread-1| I125: Installing vmnet from /tmp/modconfig-EgD6A9/vmnet.o to /lib/modules/4.8.17-galliumos/misc/vmnet.ko.

2018-02-12T16:41:36.672-05:00| vthread-1| I125: Registering file "/lib/modules/4.8.17-galliumos/misc/vmnet.ko".

2018-02-12T16:41:37.344-05:00| vthread-1| I125: "/usr/lib/vmware-installer/2.1.0/vmware-installer" exited with status 0.

2018-02-12T16:41:37.344-05:00| vthread-1| I125: Registering file "/usr/lib/vmware/symvers/vmnet-4.8.17-galliumos".

2018-02-12T16:41:38.011-05:00| vthread-1| I125: "/usr/lib/vmware-installer/2.1.0/vmware-installer" exited with status 0.

2018-02-12T16:41:38.017-05:00| vthread-1| I125: Setting destination path for vmci to "/lib/modules/4.8.17-galliumos/misc/vmci.ko".

2018-02-12T16:41:38.018-05:00| vthread-1| I125: Extracting the vmci source from "/usr/lib/vmware/modules/source/vmci.tar".

2018-02-12T16:41:38.043-05:00| vthread-1| I125: Successfully extracted the vmci source.

2018-02-12T16:41:38.043-05:00| vthread-1| I125: Building module with command "/usr/bin/make -j2 -C /tmp/modconfig-EgD6A9/vmci-only auto-build HEADER_DIR=/lib/modules/4.8.17-galliumos/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2018-02-12T16:41:40.148-05:00| vthread-1| W115: Failed to build vmci.  Failed to execute the build command.

I have been looking online for this and haven't had a lot of luck finding the same thing. I have VMWare Workstation 12 player installed. When I bring up a VM, and then set the resolution to be smaller than that of the host's, it basically centers the screen and there are black borders all around. I was hoping there could be a way to make vmware change the host's resolution to match the guest's resolution whenever the guest's resolution changes so that it feels more seamless. I don't see anything like this in the basic configuration GUI, but a lot of times there are options that need to be added to the preferences file. Can anyone point me to something like this?

Thanks!

I mainly used VirtualBox for my VMs. But these days they do not work that good any more, the sound is broken and at the moment without repair. I learned that I can move over to VMWare by exporting the vdi file of an Virtualbox VM by "Exporting Appliance" to OVA format. This should be importable in VMWare Workstation Player (14 in my case). But so far it did *not* work whatever differrent export parameters I tried. The best attempt died while booting (a Windows 10 Pro 64 bit machine)

What is the correct way to convert a vdi file to a OVA/vdmk file for VMWare Workstation Player 14?

I am running VMware Workstation 12 Player (12.5.9 build-7535481) on a Windows 10 machine. Before zipping the image to distribute to students who will try to find and fix security vulnerabilities, I see that I have a number of .vmdk files Is there a way to reduce the number/size (27.2 GB) of these files?

I used VMwareToolboxCmd.exe disk shrink utility on the guest image and received the message "disk shrinking complete." My compressed file size, using 7zip, is still a rather impressive 14.6 GB.