VMware Workstation 11 installation directory

Greetings,

I recently downloaded vmware workstation 11 64-bit path and installed on Windows 8.1, he moved to the path ' C:\program files (x 86)-"I don't know if its installation correct directory or not, but it is the default path. I ask this because especially the 64-bit application will move into "C:\program files", my computer works fine, but I uninstalled the thought of vmware workstation to choose the 64-bit version and enabled VT in BIOS and tried to reinstall, but sitill that it points to x 86 path. My laptop uses the Intel i7 with 16 GB of RAM.

With respect,

Guillet.

Hi smgopinath,

Behavior you saw (WS installed under "C:\program files (x 86) \") is as expected. Workstation UI is a 32-bit application and is installed by default in "C:\program files (x 86) \".

So just, do not hesitate to use the workstation under the default path.

Tags: VMware

Similar Questions

VMware Workstation 9 installation failed

Signed in as an administrator and run the installation "as Administrator".
Downloaded twice in case file has been corrupted.
How to get:
The MSI 'c:\users\administrator\AppData\Local\temp\\vmware_1350226415\vmwareworkstation_x86.msi' failed.
Service "VMware Workstation Server" (VMwareHostd) could not be installed. Make sure you have sufficient privileges to install system services.
This file has all the rights

Is the following: "ALEX ~ 1.SYS ' really your admin account?

Don t have a normal account with a name like "admin" or something? -I expect it works with such a name.

The restore script failed - Please check if the permissions of the registry for HKLM\Software\VMware Inc. are always ok

VMWare Workstation 9 - installation in silent mode

Hello!
Im trying to install VMWare Workstation 9 with a bat script.
It is installed successfully, but it doesn´ttake the serial number of the script. I have to enter the serial number after installation manuelly 9 workstation to start a virtual machine.
Here is my script:
Msiexec /i "\\Path\vmwareworkstation_x64.msi" /qn REBOOT = REALLYSUPPRESS ADDLOCAL = ALL DESKTOPSHORTCUT = 1 SERIALNUMBER = "XXXXX-XXXXX-XXXXX-XXXXX-XXXXX".
See you there all the failures?
I hope someone has an idea...

Welcome to the community,

rather to extract the installation package and run the .msi file, you must run the .exe directly file with the permissions of the place. Please take a look at Re: SERIALNUMBER of VMware Workstation 8 property does not to see if that helps also with version 9.

André

VMware Workstation - Vista installation stops at "Completing Installation"

I use VMware Workstation v6.5.3 build 685404.
I try to install Vista business, an iso image located on my computer on a host machine virtual with 1024MB Ram and 16 GB on HDD.
However, the installation will stop at the stage of the "end of the installation. 3 points after the words "end of installation" continues to scroll, but the installation never goes beyond this point.
Any help in getting this to install entirely would be much appreciated.
Thank you.

16 GB of hard drive space seems very small. The amount of RAM, 1024 Mb, should be sufficient.

How long the installation stall right there?

What is the configuration of the host computer? (OS, memory Ram, size of hard drive,...)

Installation of VMWare Workstation on Fedora 20 10.1

Hello VMWare community!
So I tried for the past few days to install VMWare on my workstation. I tried both VMWare Workstation 9 and 10, but that didn't work either. The problem is just after installation, when are compilation of kernel modules.
Here is the log:

[root@hunt33rsmobilelinux downloads] # cat /tmp/vmware-root/vmware-modconfig-10793.log

2014-03 - 01 T 14: 43:20.629 + 01:00 | vthread-3 | I120: Log for VMware Workstation pid = version 10.0.1 10793 = build = build-1379776 option = output

2014-03 - 01 T 14: 43:20.629 + 01:00 | vthread-3 | I120: The process is 64-bit.

2014-03 - 01 T 14: 43:20.629 + 01:00 | vthread-3 | I120: Host codepage = UTF-8 encoding = UTF-8

2014-03 - 01 T 14: 43:20.629 + 01:00 | vthread-3 | I120: Host is the version of Fedora Linux 3.13.4 - 200.fc20.x86_64 20 (Heisenbug)

2014-03 - 01 T 14: 43:20.628 + 01:00 | vthread-3 | I120: Msg_Reset:

2014-03 - 01 T 14: 43:20.628 + 01:00 | vthread-3 | I120: [msg.dictionary.load.openFailed] cannot open the file ' / usr/lib/vmware/settings ': no such file or directory.

2014-03 - 01 T 14: 43:20.628 + 01:00 | vthread-3 | I120: ----------------------------------------

2014-03 - 01 T 14: 43:20.628 + 01:00 | vthread-3 | I120: Preferences file of the option PREFS not found in/usr/lib/vmware/settings. Using the default values.

2014-03 - 01 T 14: 43:20.628 + 01:00 | vthread-3 | I120: Msg_Reset:

2014-03 - 01 T 14: 43:20.628 + 01:00 | vthread-3 | I120: [msg.dictionary.load.openFailed] cannot open the file ' / root/.vmware/config ': no such file or directory.

2014-03 - 01 T 14: 43:20.628 + 01:00 | vthread-3 | I120: ----------------------------------------

2014-03 - 01 T 14: 43:20.628 + 01:00 | vthread-3 | I120: Optional preferences PREFS not found in root/.vmware/config file. Using the default values.

2014-03 - 01 T 14: 43:20.628 + 01:00 | vthread-3 | I120: PREF cannot verify the permissions for the preferences file.

2014-03 - 01 T 14: 43:20.628 + 01:00 | vthread-3 | I120: Msg_Reset:

2014-03 - 01 T 14: 43:20.628 + 01:00 | vthread-3 | I120: [msg.dictionary.load.openFailed] cannot open the file ' / root/.vmware/preferences ': no such file or directory.

2014-03 - 01 T 14: 43:20.628 + 01:00 | vthread-3 | I120: ----------------------------------------

2014-03 - 01 T 14: 43:20.628 + 01:00 | vthread-3 | I120: PREF cannot load the user's preferences.

2014-03 - 01 T 14: 43:20.629 + 01:00 | vthread-3 | W110: Connecting to /tmp/vmware-root/vmware-modconfig-10793.log

2014-03 - 01 T 14: 43:20.632 + 01:00 | vthread-3 | I120: Obtaining information on the use of the kernel running.

2014-03 - 01 T 14: 43:20.632 + 01:00 | vthread-3 | I120: Created new pathsHash.

2014-03 - 01 T 14: 43:20.632 + 01:00 | vthread-3 | I120: Setting header way for 3.13.4 - 200.fc20.x86_64 to "/ lib/modules/3.13.4-200.fc20.x86_64/build/include".

2014-03 - 01 T 14: 43:20.632 + 01:00 | vthread-3 | I120: Validation of path ' / lib/modules/3.13.4-200.fc20.x86_64/build/include ' for kernel version "3.13.4 - 200.fc20.x86_64.

2014-03 - 01 T 14: 43:20.632 + 01:00 | vthread-3 | I120: using/usr/lib64/ccache/CCG to preprocess check

2014-03 - 01 T 14: 43:20.638 + 01:00 | vthread-3 | I120: Pre-treated UTS_RELEASE, obtained the value "3.13.4 - 200.fc20.x86_64.

2014-03 - 01 T 14: 43:20.638 + 01:00 | vthread-3 | I120: The path of the header ' / lib/modules/3.13.4-200.fc20.x86_64/build/include ' to the core "3.13.4 - 200.fc20.x86_64" is valid. Boo!

2014-03 - 01 T 14: 43:20.721 + 01:00 | vthread-3 | I120: Reading in info for the vmmon module.

2014-03 - 01 T 14: 43:20.721 + 01:00 | vthread-3 | I120: Reading in info for module vmnet.

2014-03 - 01 T 14: 43:20.721 + 01:00 | vthread-3 | I120: Reading in info for the vmblock module.

2014-03 - 01 T 14: 43:20.721 + 01:00 | vthread-3 | I120: Reading in info for vmci module.

2014-03 - 01 T 14: 43:20.721 + 01:00 | vthread-3 | I120: Reading in info for the vsock module.

2014-03 - 01 T 14: 43:20.721 + 01:00 | vthread-3 | I120: Definition of vsock to depend on vmci.

2014-03 - 01 T 14: 43:20.721 + 01:00 | vthread-3 | I120: Modinfo calling over 'vmmon.

2014-03 - 01 T 14: 43:20.723 + 01:00 | vthread-3 | I120: ' / sbin/modinfo ' came out with a status of 0.

2014-03 - 01 T 14: 43:20.723 + 01:00 | vthread-3 | I120: Modinfo invoking on "vmnet".

2014-03 - 01 T 14: 43:20.724 + 01:00 | vthread-3 | I120: ' / sbin/modinfo ' came out with status 256.

2014-03 - 01 T 14: 43:20.724 + 01:00 | vthread-3 | I120: Modinfo invoking on 'vmblock '.

2014-03 - 01 T 14: 43:20.725 + 01:00 | vthread-3 | I120: ' / sbin/modinfo ' came out with status 256.

2014-03 - 01 T 14: 43:20.725 + 01:00 | vthread-3 | I120: Modinfo calling over 'vmci.

2014-03 - 01 T 14: 43:20.727 + 01:00 | vthread-3 | I120: ' / sbin/modinfo ' came out with status 256.

2014-03 - 01 T 14: 43:20.727 + 01:00 | vthread-3 | I120: Modinfo calling over 'vsock.

2014-03 - 01 T 14: 43:20.728 + 01:00 | vthread-3 | I120: ' / sbin/modinfo ' came out with a status of 0.

2014-03 - 01 T 14: 43:20.735 + 01:00 | vthread-3 | I120: must be installed: vmnet status: 0

2014-03 - 01 T 14: 43:20.742 + 01:00 | vthread-3 | I120: Obtaining information on the use of the kernel running.

2014-03 - 01 T 14: 43:20.742 + 01:00 | vthread-3 | I120: Setting header way for 3.13.4 - 200.fc20.x86_64 to "/ lib/modules/3.13.4-200.fc20.x86_64/build/include".

2014-03 - 01 T 14: 43:20.742 + 01:00 | vthread-3 | I120: Validation of path ' / lib/modules/3.13.4-200.fc20.x86_64/build/include ' for kernel version "3.13.4 - 200.fc20.x86_64.

2014-03 - 01 T 14: 43:20.742 + 01:00 | vthread-3 | I120: using/usr/lib64/ccache/CCG to preprocess check

2014-03 - 01 T 14: 43:20.748 + 01:00 | vthread-3 | I120: Pre-treated UTS_RELEASE, obtained the value "3.13.4 - 200.fc20.x86_64.

2014-03 - 01 T 14: 43:20.748 + 01:00 | vthread-3 | I120: The path of the header ' / lib/modules/3.13.4-200.fc20.x86_64/build/include ' to the core "3.13.4 - 200.fc20.x86_64" is valid. Boo!

2014-03 - 01 T 14: 43:20.830 + 01:00 | vthread-3 | I120: Kernel header path comes from FileEntry: /lib/modules/3.13.4-200.fc20.x86_64/build/include

2014-03 - 01 T 14: 43:20.830 + 01:00 | vthread-3 | I120: update the kernel header path to the /lib/modules/3.13.4-200.fc20.x86_64/build/include

2014-03 - 01 T 14: 43:20.830 + 01:00 | vthread-3 | I120: Validation of path ' / lib/modules/3.13.4-200.fc20.x86_64/build/include ' for kernel version "3.13.4 - 200.fc20.x86_64.

2014-03 - 01 T 14: 43:20.830 + 01:00 | vthread-3 | I120: using/usr/lib64/ccache/CCG to preprocess check

2014-03 - 01 T 14: 43:20.837 + 01:00 | vthread-3 | I120: Pre-treated UTS_RELEASE, obtained the value "3.13.4 - 200.fc20.x86_64.

2014-03 - 01 T 14: 43:20.837 + 01:00 | vthread-3 | I120: The path of the header ' / lib/modules/3.13.4-200.fc20.x86_64/build/include ' to the core "3.13.4 - 200.fc20.x86_64" is valid. Boo!

2014-03 - 01 T 14: 43:20.838 + 01:00 | vthread-3 | I120: Compiler found at "/ usr/lib64/ccache/gcc.

2014-03 - 01 T 14: 43:20.841 + 01:00 | vthread-3 | I120: Got gcc version "4.8.2.

2014-03 - 01 T 14: 43:20.841 + 01:00 | vthread-3 | I120: The GCC version corresponds to the minor version of GCC kernel like a glove.

2014-03 - 01 T 14: 43:20.841 + 01:00 | vthread-3 | I120: With the help of the compiler provided by the user "/ usr/lib64/ccache/gcc.

2014-03 - 01 T 14: 43:20.844 + 01:00 | vthread-3 | I120: Got gcc version "4.8.2.

2014-03 - 01 T 14: 43:20.844 + 01:00 | vthread-3 | I120: The GCC version corresponds to the minor version of GCC kernel like a glove.

2014-03 - 01 T 14: 43:20.847 + 01:00 | vthread-3 | I120: Try to find a PBM adapted for the core "3.13.4 - 200.fc20.x86_64.

2014-03 - 01 T 14: 43:20.847 + 01:00 | vthread-3 | I120: No corresponding PBM set has been found for the core "3.13.4 - 200.fc20.x86_64.

2014-03 - 01 T 14: 43:20.847 + 01:00 | vthread-3 | I120: The GCC version corresponds to the minor version of GCC kernel like a glove.

2014-03 - 01 T 14: 43:20.847 + 01:00 | vthread-3 | I120: Validation of path ' / lib/modules/3.13.4-200.fc20.x86_64/build/include ' for kernel version "3.13.4 - 200.fc20.x86_64.

2014-03 - 01 T 14: 43:20.847 + 01:00 | vthread-3 | I120: using/usr/lib64/ccache/CCG to preprocess check

2014-03 - 01 T 14: 43:20.853 + 01:00 | vthread-3 | I120: Pre-treated UTS_RELEASE, obtained the value "3.13.4 - 200.fc20.x86_64.

2014-03 - 01 T 14: 43:20.853 + 01:00 | vthread-3 | I120: The path of the header ' / lib/modules/3.13.4-200.fc20.x86_64/build/include ' to the core "3.13.4 - 200.fc20.x86_64" is valid. Boo!

2014-03 - 01 T 14: 43:20.857 + 01:00 | vthread-3 | I120: The GCC version corresponds to the minor version of GCC kernel like a glove.

2014-03 - 01 T 14: 43:20.857 + 01:00 | vthread-3 | I120: Validation of path ' / lib/modules/3.13.4-200.fc20.x86_64/build/include ' for kernel version "3.13.4 - 200.fc20.x86_64.

2014-03 - 01 T 14: 43:20.857 + 01:00 | vthread-3 | I120: using/usr/lib64/ccache/CCG to preprocess check

2014-03 - 01 T 14: 43:20.863 + 01:00 | vthread-3 | I120: Pre-treated UTS_RELEASE, obtained the value "3.13.4 - 200.fc20.x86_64.

2014-03 - 01 T 14: 43:20.863 + 01:00 | vthread-3 | I120: The path of the header ' / lib/modules/3.13.4-200.fc20.x86_64/build/include ' to the core "3.13.4 - 200.fc20.x86_64" is valid. Boo!

2014-03 - 01 T 14: 43:20.863 + 01:00 | vthread-3 | I120: Temp dir using ' / tmp '.

2014-03 - 01 T 14: 43:20.864 + 01:00 | vthread-3 | I120: Obtaining information on the use of the kernel running.

2014-03 - 01 T 14: 43:20.864 + 01:00 | vthread-3 | I120: Setting header way for 3.13.4 - 200.fc20.x86_64 to "/ lib/modules/3.13.4-200.fc20.x86_64/build/include".

2014-03 - 01 T 14: 43:20.864 + 01:00 | vthread-3 | I120: Validation of path ' / lib/modules/3.13.4-200.fc20.x86_64/build/include ' for kernel version "3.13.4 - 200.fc20.x86_64.

2014-03 - 01 T 14: 43:20.864 + 01:00 | vthread-3 | I120: using/usr/lib64/ccache/CCG to preprocess check

2014-03 - 01 T 14: 43:20.870 + 01:00 | vthread-3 | I120: Pre-treated UTS_RELEASE, obtained the value "3.13.4 - 200.fc20.x86_64.

2014-03 - 01 T 14: 43:20.870 + 01:00 | vthread-3 | I120: The path of the header ' / lib/modules/3.13.4-200.fc20.x86_64/build/include ' to the core "3.13.4 - 200.fc20.x86_64" is valid. Boo!

2014-03 - 01 T 14: 43:20.951 + 01:00 | vthread-3 | I120: Modinfo invoking on "vmnet".

2014-03 - 01 T 14: 43:20.953 + 01:00 | vthread-3 | I120: ' / sbin/modinfo ' came out with status 256.

2014-03 - 01 T 14: 43:20.993 + 01:00 | vthread-3 | I120: The setting for vmnet destination path to ' / lib/modules/3.13.4-200.fc20.x86_64/misc/vmnet.ko '.

2014-03 - 01 T 14: 43:20.993 + 01:00 | vthread-3 | I120: Extraction of the source vmnet "/ usr/lib/vmware/modules/source/vmnet.tar".

2014-03 - 01 T 14: 43:20.996 + 01:00 | vthread-3 | I120: Extract successfully the vmnet source.

2014-03 - 01 T 14: 43:20.996 + 01:00 | vthread-3 | I120: Module construction with the command ' / usr/bin/make - j8 - C/tmp/modconfig-zXW96r/vmnet-only-automatic generation HEADER_DIR=/lib/modules/3.13.4-200.fc20.x86_64/build/include CC = / usr/lib64/ccache/gcc IS_GCC_3 = no ".

2014-03 - 01 T 14: 43:22.104 + 01:00 | vthread-3 | W110: Vmnet failed. Cannot run the command build.

I have tried of course updated everything. yum update is ok, so I'm a bit with no idea.
So, did you ever find this problem?
Thank you
Matthew
- Fedora is not a host for VMware Workstation/Player-supported operating system. Note that although not officially supported as a host nevertheless operating system I run it under Fedora 20, but with the stock kernel.
- I do not think that the 3.13.4 kernel is still supported, even on a supported host OSes.
- Take a look at: VMware modules & core 3.13

VMware Workstation 9: could not open/dev/vmmon: no such file or directory

I'll have a plethora of problems installing and get VMware Workstation 9 (9.0.2 build-1031769) to work on Ubuntu 13.04 (kernel 3.8.0 - 26-generic).
I experienced exactly the same process on my laptop and it works perfectly, while on the desktop, it seems that everything breaks. Could someone give me some kind of help / advice on how I can do to get this working. I tried full uninstall / reinstall of the software, headers of the kernel, kernel images, different kernels, patches here on fresh installs of everything I can think of. Here are the issues I encounter in the order of importance (or so I think):
(1) whenever I try to open my new (and virtual) machine, I get the error sequence of:
"Could not open/dev/vmmon: no such file or directory. " Please make sure that the "vmmon" kernel module is loaded. '--> 'Failed to initialize the device monitor. "->" cannot change the power state of VM: could not find a valid peer to connect to '

(2) every time I try to run the following command to configure the modules on a completely fresh setting (reinstalled kernel, vmware) I get the following output:
sudo modconfig vmware - console - install-all
Stopping VMware services:
Demon of authentication makes VMware
VM communication interface socket family is
Virtual machine communication interface is
Virtual machine monitor makes
File system is blocking
Using 2.6.x kernel build system.
do: enter the directory "/ tmp/modconfig-G9S0TM/vmmon-only '.
/ usr/bin/make /lib/modules/3.8.0-26-generic/build/include/ - c... SUBDIRS = $PWD SRCROOT = $PWD. \
MODULEBUILDDIR = modules
make [1]: Entering directory ' / usr/src/linux-headers-3.8.0-26-generic'
CC [M] /tmp/modconfig-G9S0TM/vmmon-only/linux/driver.o
CC [M] /tmp/modconfig-G9S0TM/vmmon-only/linux/driverLog.o
CC [M] /tmp/modconfig-G9S0TM/vmmon-only/linux/hostif.o
CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/apic.o
CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/comport.o
CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/cpuid.o
CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/hashFunc.o
CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/memtrack.o
CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/phystrack.o
CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/task.o
CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/vmx86.o
CC [M] /tmp/modconfig-G9S0TM/vmmon-only/vmcore/moduleloop.o
LD [M] /tmp/modconfig-G9S0TM/vmmon-only/vmmon.o
Construction modules, step 2.
MODPOST modules 1
Warning: "mcount" [/ tmp/modconfig-G9S0TM/vmmon-only/vmmon.ko] undefined!
CC /tmp/modconfig-G9S0TM/vmmon-only/vmmon.mod.o
LD [M] /tmp/modconfig-G9S0TM/vmmon-only/vmmon.ko
make [1]: leaving directory ' / usr/src/linux-headers-3.8.0-26-generic'
/ usr/bin/make - c $PWD SRCROOT = $PWD. \
MODULEBUILDDIR = postgeneration
make [1]: entering directory ' / tmp/modconfig-G9S0TM/vmmon-only '.
make [1]: 'postgeneration' is up-to-date.
make [1]: leaving directory ' / tmp/modconfig-G9S0TM/vmmon-only '.
CP f vmmon.ko. /... vmmon.o
make: leaving directory ' / tmp/modconfig-G9S0TM/vmmon-only '.
Using 2.6.x kernel build system.
make: entering directory ' / tmp/modconfig-G9S0TM/vmnet-only»
/ usr/bin/make /lib/modules/3.8.0-26-generic/build/include/ - c... SUBDIRS = $PWD SRCROOT = $PWD. \
MODULEBUILDDIR = modules
make [1]: Entering directory ' / usr/src/linux-headers-3.8.0-26-generic'
CC [M] /tmp/modconfig-G9S0TM/vmnet-only/driver.o
CC [M] /tmp/modconfig-G9S0TM/vmnet-only/hub.o
CC [M] /tmp/modconfig-G9S0TM/vmnet-only/userif.o
CC [M] /tmp/modconfig-G9S0TM/vmnet-only/netif.o
CC [M] /tmp/modconfig-G9S0TM/vmnet-only/bridge.o
CC [M] /tmp/modconfig-G9S0TM/vmnet-only/filter.o
CC [M] /tmp/modconfig-G9S0TM/vmnet-only/procfs.o
CC [M] /tmp/modconfig-G9S0TM/vmnet-only/smac_compat.o
CC [M] /tmp/modconfig-G9S0TM/vmnet-only/smac.o
CC [M] /tmp/modconfig-G9S0TM/vmnet-only/vnetEvent.o
CC [M] /tmp/modconfig-G9S0TM/vmnet-only/vnetUserListener.o
LD [M] /tmp/modconfig-G9S0TM/vmnet-only/vmnet.o
Construction modules, step 2.
MODPOST modules 1
Warning: "mcount" [/ tmp/modconfig-G9S0TM/vmnet-only/vmnet.ko] undefined!
CC /tmp/modconfig-G9S0TM/vmnet-only/vmnet.mod.o
LD [M] /tmp/modconfig-G9S0TM/vmnet-only/vmnet.ko
make [1]: leaving directory ' / usr/src/linux-headers-3.8.0-26-generic'
/ usr/bin/make - c $PWD SRCROOT = $PWD. \
MODULEBUILDDIR = postgeneration
make [1]: entering directory ' / tmp/modconfig-G9S0TM/vmnet-only.
make [1]: 'postgeneration' is up-to-date.
make [1]: leaving directory ' / tmp/modconfig-G9S0TM/vmnet-only.
CP f vmnet.ko. /... vmnet.o
make: leaving directory ' / tmp/modconfig-G9S0TM/vmnet-only.
Using 2.6.x kernel build system.
do: enter the directory "/ tmp/modconfig-G9S0TM/vmblock-only.
/ usr/bin/make /lib/modules/3.8.0-26-generic/build/include/ - c... SUBDIRS = $PWD SRCROOT = $PWD. \
MODULEBUILDDIR = modules
make [1]: Entering directory ' / usr/src/linux-headers-3.8.0-26-generic'
CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/block.o
CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/control.o
CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/dentry.o
CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/file.o
CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/filesystem.o
CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/inode.o
CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/stubs.o
CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/module.o
/tmp/modconfig-G9S0TM/vmblock-only/Linux/control.c: in function 'ExecuteBlockOp ':
/tmp/modconfig-G9S0TM/vmblock-only/Linux/control.c:285: warning: assignment of incompatible pointer type
/tmp/modconfig-G9S0TM/vmblock-only/Linux/control.c:296: warning: passing argument 1 of the "putname" incompatible pointer type
include/Linux/FS.h:2052: Note: expected ' struct filename *' but argument is of type ' char *'
CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/super.o
/tmp/modconfig-G9S0TM/vmblock-only/Linux/inode.c:49: warning: initialization from incompatible pointer type
/tmp/modconfig-G9S0TM/vmblock-only/Linux/dentry.c:38: warning: initialization from incompatible pointer type
/tmp/modconfig-G9S0TM/vmblock-only/Linux/dentry.c: in function 'DentryOpRevalidate ':
/tmp/modconfig-G9S0TM/vmblock-only/Linux/dentry.c:104: warning: argument passing 2 of 'actualDentry-> d_op-> d_revalidate' makes whole pointer without a cast
/tmp/modconfig-G9S0TM/vmblock-only/Linux/dentry.c:104: Note: expected 'unsigned int' but argument is of type ' struct nameidata *'
LD [M] /tmp/modconfig-G9S0TM/vmblock-only/vmblock.o
Construction modules, step 2.
MODPOST modules 1
Warning: "mcount" [/ tmp/modconfig-G9S0TM/vmblock-only/vmblock.ko] undefined!
Warning: "putname" [/ tmp/modconfig-G9S0TM/vmblock-only/vmblock.ko] undefined!
CC /tmp/modconfig-G9S0TM/vmblock-only/vmblock.mod.o
LD [M] /tmp/modconfig-G9S0TM/vmblock-only/vmblock.ko
make [1]: leaving directory ' / usr/src/linux-headers-3.8.0-26-generic'
/ usr/bin/make - c $PWD SRCROOT = $PWD. \
MODULEBUILDDIR = postgeneration
make [1]: entering directory ' / tmp/modconfig-G9S0TM/vmblock-only.
make [1]: 'postgeneration' is up-to-date.
make [1]: leaving directory ' / tmp/modconfig-G9S0TM/vmblock-only.
CP f vmblock.ko. /... vmblock.o
make: leaving directory ' / tmp/modconfig-G9S0TM/vmblock-only.
Using 2.6.x kernel build system.
do: enter the directory "/ tmp/modconfig-G9S0TM/vmci-only.
/ usr/bin/make /lib/modules/3.8.0-26-generic/build/include/ - c... SUBDIRS = $PWD SRCROOT = $PWD. \
MODULEBUILDDIR = modules
make [1]: Entering directory ' / usr/src/linux-headers-3.8.0-26-generic'
CC [M] /tmp/modconfig-G9S0TM/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-G9S0TM/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciContext.o
CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciDatagram.o
CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciDriver.o
CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciHashtable.o
CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciEvent.o
CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciQPair.o
CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciResource.o
CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciRoute.o
CC [M] /tmp/modconfig-G9S0TM/vmci-only/driverLog.o
LD [M] /tmp/modconfig-G9S0TM/vmci-only/vmci.o
Construction modules, step 2.
MODPOST modules 1
Warning: "mcount" [/ tmp/modconfig-G9S0TM/vmci-only/vmci.ko] undefined!
CC /tmp/modconfig-G9S0TM/vmci-only/vmci.mod.o
LD [M] /tmp/modconfig-G9S0TM/vmci-only/vmci.ko
make [1]: leaving directory ' / usr/src/linux-headers-3.8.0-26-generic'
/ usr/bin/make - c $PWD SRCROOT = $PWD. \
MODULEBUILDDIR = postgeneration
make [1]: entering directory ' / tmp/modconfig-G9S0TM/vmci-only.
make [1]: 'postgeneration' is up-to-date.
make [1]: leaving directory ' / tmp/modconfig-G9S0TM/vmci-only.
CP f vmci.ko. /... VMCI.o
make: leaving directory ' / tmp/modconfig-G9S0TM/vmci-only.
Using 2.6.x kernel build system.
do: enter the directory "/ tmp/modconfig-G9S0TM/vsock-only '.
/ usr/bin/make /lib/modules/3.8.0-26-generic/build/include/ - c... SUBDIRS = $PWD SRCROOT = $PWD. \
MODULEBUILDDIR = modules
make [1]: Entering directory ' / usr/src/linux-headers-3.8.0-26-generic'
CC [M] /tmp/modconfig-G9S0TM/vsock-only/linux/af_vsock.o
CC [M] /tmp/modconfig-G9S0TM/vsock-only/linux/notify.o
CC [M] /tmp/modconfig-G9S0TM/vsock-only/linux/notifyQState.o
CC [M] /tmp/modconfig-G9S0TM/vsock-only/linux/stats.o
CC [M] /tmp/modconfig-G9S0TM/vsock-only/linux/util.o
CC [M] /tmp/modconfig-G9S0TM/vsock-only/linux/vsockAddr.o
CC [M] /tmp/modconfig-G9S0TM/vsock-only/driverLog.o
LD [M] /tmp/modconfig-G9S0TM/vsock-only/vsock.o
Construction modules, step 2.
MODPOST modules 1
Warning: "mcount" [/ tmp/modconfig-G9S0TM/vsock-only/vsock.ko] undefined!
CC /tmp/modconfig-G9S0TM/vsock-only/vsock.mod.o
LD [M] /tmp/modconfig-G9S0TM/vsock-only/vsock.ko
make [1]: leaving directory ' / usr/src/linux-headers-3.8.0-26-generic'
/ usr/bin/make - c $PWD SRCROOT = $PWD. \
MODULEBUILDDIR = postgeneration
make [1]: entering directory ' / tmp/modconfig-G9S0TM/vsock-only '.
make [1]: 'postgeneration' is up-to-date.
make [1]: leaving directory ' / tmp/modconfig-G9S0TM/vsock-only '.
CP f vsock.ko. /... vsock.o
make: leaving directory ' / tmp/modconfig-G9S0TM/vsock-only '.
Starting VMware services:
Virtual machine monitor failed
Virtual machine communication interface failed
Family of VM communication interface socket failed
File system is blocking
Virtual Ethernet failed
Demon of authentication makes VMware
Cannot start the services
(3) I often get the Ubuntu "this program has planted" messages on "/ usr/lib/vmware-installer/2.1.0/vmis-launcher" "' (this message of crash always occurs when you run the"vmware-modconfig"above command on a new installation.
(4) at different times during Assembly and have VMware workstation on my system I get Ubuntu hangs on "/ usr/lib/vmware/bin/appLoader" and even "/ bin/su" (especially when you are trying to install - su NEVER blocks anywhere else).
Thoughts / ideas on what is happening on earth / what could have caused this all go so downhill / how to go about fixing?
Thank you

Solved.

The problem is that for another program I used gcc - 4. 4 instead of later. Restore the (by update-alternatives - config ) for gcc, g ++ and CPC - bin.

Not a very graceful exit to have a version not valid I would say, maybe some sort of basic check could be added to ensure that the correct versions are present?

installation of vmware workstation 6.5 on windows 10 error

After you install vmware workstation 6.5 on windows 10 it gets error and restart. Is vmware workstation 6.5 support windows 10? FAILED TO INSTALL. vmware workstation 6.5 on windows 8, 8.1 and 10 support. ALL SUPPORT. I still don't understand...

VMware Workstation 6.x do not support Windows 10 and will never support Windows 10.

VMware Workstation 6.x reached "end of support" four years, October 1, 2011: Matrix.pdf product lifecycle

We produce updates for release until its date of "end of support". A product may not work properly with host OSes, processors or comments OSes that are not compatible with the product, especially the things that have been published after the date of "end of support". We put a huge amount of effort to ensure that new hardware and operating systems works with each new major release of VMware Workstation, but we cannot go back and update any previous version of product to add support for all hardware and operating systems more recent. If we tried to do this, VMware Workstation cost much more that it is today, simply because of the amount of work required to maintain!

You need to upgrade your installation of VMware Workstation to something more recent, or downgrade your host operating system to a version compatible with VMware Workstation 6.5.

I hope this helps!

--

Darius

Installation of VMWare Workstation 11 freezes with gray screen!

Hello
I know this is a very known issue, but difficult to solve, I can't install VMWare Workstation V11 (tried with the old version 8, the same) since as soon as I click Setup, I have a gray screen and installation seems suspended it.
Tried the same thing with VMWare Player, same result, even with older versions...
No way to close the gray screen, unless you kill the process.
My case is laptop Thinkpad T510, native W7 64-bit, processor Intel i5, 4 GB ram, Java utility installed and 100% updated, Nvidia GPU, nothing strange.
Microsoft Security essential only running, no other AV or firewall...
I tried to save two files reading autour on this community, but this does not solve the problem.
I see not what is a well known problem and it is absurd does not have a way to solve it on VMWare...
Any help is very appreciated!
Thank you very much
Concerning
Denis Ferrari

Hi all

problem solved right and - in my case - was a strange key with a small '' L '' name to cancel here:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\

It may be useful

Installation of VMWare Workstation 11.1.0 on Win 8.1 is THAT MSI will fail with the error "could not write value vmware - tray.exe for \software\microsoft\windows'currentversion\run-cles.

Hi all
The MSI failed with the error message as "could not write value vmware - tray.exe in \SOFTWARE\Microsoft\Windows'CurrentVersion\Run key. Make sure you have fufficient access to that key, or contact your support staff' while trying to install vmware workstation 11.1.0 in windows 8.1.
I tried to call the installer with run as administrator but it does not help, please suggest me overcome this error.

Hi Vincentand welcome to the VMware communities!

This error indicates that you have some security software (antivirus or antimalware software) that protects the part of the registry. Can you try to temporarily disable all security software on your host computer and see if the installation can move forward?

See you soon,.

--

Darius

Any Installation of Vmware Workstation failed in my machine, why? See the details

Hey guys, I'm trying to install vmware workstation 11,10 even though 9, but unfortunately it shows this kind of error every time.
then I try to install from appdata/local/temp, but it shows the error of capture4... I tried many things to fix this... but I failed...
So guys help me please install... sorely lacking...
is my laptop config: core i5 - 3230M, ram - 4 GB os-win7 64 bit sp1...
need help please...

Welcome to the community,

the problem is probably caused by the apostrophe in the name of the folder of the user. Try at each logon with a different user (temporary) account, or change the temp/tmp environment variable to point to a different directory (existing), for example, "C:\TEMP".

André

Installation of Windows Server 2003 on vmware workstation 9

Hello
I try to install windows server 2003 R2 x 64 edition as a guest OS on vmware workstation 9. But it gives me the time hard the same installation.
First I had the
"found no hard drives installed in your computer error.
I was able to fix this by downloading it pilot vmware scsi. Now I get NTLDR is missing, restart the computer.

I have install windows OS was frank. Anyone faced this problem. Please advise me? I have 2 CD (Cd1 and Cd2) of Windows server 2003 edition.

Any help is appreciated

Thanks in advance

1 you shouldn't have to download all the drivers for the vHDD, as LSI Logic drivers are included in Windows Server 2003. In other words, you have not selected correct SCSI (LSI Logic) controller.

Now I get NTLDR is missing, restart the computer.

Make sure that the disk is disconnected.

Failed installation of VMware Workstation 9 on new install of win 7

I looked at the discussion of installation has failed VMware Workstation 9, verified that I am administrator, cleaned folder and looked at the registry and I'm still having problems. The name of the account used is not Admin/Admin or anything close.
This is a new installation today of windows 7 with all updates applied. Avast is my anti-virus software. The behavior does not change with it running or disabled.
I think that the problem to be that KLM/Sofware/VMware Inc. does not appear. I checked that I can create keys.
"In my installs I've seen: message" failure of the MSI MSI "and once"the MSI MSI failed. " Authorization of VMware (VMAuthService) failed to start service.
Here are the logs from my last install.
Can someone provide me with more information about the problem and how to get this installed?
Thank you

Finally got this resolved after many setup logs sent to VMware. I came across the registry problems and VMAuthdServices fail to start due to software AV.

In short, following http://kb.vmware.com/kb/1031302 (KB1031302) is important as well as some comments from howellrj. Here's what I did in detail and why during my various tests of installation:

http://KB.VMware.com/kb/1031302

1 I used the only account on the system, which did not have a name as owner, admin, administrator, which has administrator privileges

2 wiped % TEMP % whenever I made an attempt to install

3 MS KB 942288 not recommended for Win7 so I jumped

4 no earlier version of VMware Workstation has been installed on the system, so I jumped

5 ran http://support.microsoft.com/kb/2438651/en-us (MS KB2438651) whenever I made an attempt to install. He has never found anything wrong

6 was not running WinXP so I jumped

7 has made run msconfig to disable all services and should follow https://support3.avast.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=1334 (Avast KB1334) to disable Avast self protection mode. Even with Avast protection auto mode disabled and all the disabled Avast shields were always running and prevent. The only way to clear the checkpoint was to remove Avast completely.

8 I ran sfc/scannow before each installation to be sure. No problems have ever been found.

So, here is what I did to get the software installed successfully:

An item copied to my system

1 AV Installer on my system

2 use FixIt of MS KB 2438651

Disconnected the network B

C restart the system with network not connected

D removed Avast

E to restart the system with network not connected

1 erase TEMP

2 Ran FixIt utility of MS KB 2438651

3 ran sfc/scannow

F install VMware Workstation

G restart the system

H check VMware Workstation starts

I install Avast

J stop the system

K connecting to the network

L reboot the system with connected network

M update Avast

N reconfigure Avast

VMware Workstation 7.1.3 Installer empty in Windows 7 x 64

Hello
I am trying to install a new copy of VMware Workstation 7.1.3 in my PC (WIndows 7 x 64), and I have a white screen instead of the installation steps, please see the image below:
Can someone help me with this problem? Thank you.

Hi all

I had a lot of pain with this and spent all day trying to reset the internet settings, java update and finally found the solution has been associated with an adobe update that fills the internet zone settings in the registry and prevents the display of the Setup window is displayed according to the original screenshot stuck by hiperjp.

Here is the solution

Export the key below before deleting. Do a right click and export.

You must remove 1 (parasite) of additional area

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\¬]

Basically it has a Pseudo-graphique number, you will see before the zone number 0.

It seems that it is a bug in update of Adobe flash player, but I'm not sure.

This additional area prevents the desktop gadgets to figure out properly and also prevented an other Java windows look in other products Secunia 2 being one of them.

Thank heavens, it drove me crazy!

Putneyboy

(Beginner) of the initial steps for the new installation of vmware workstation & guest os

Hi, very new for the virtual machine. I need help on what type of software (vmware), need and the first steps of the installation.
Current configuration: a portable 3 separate HD, 1 computer = Windows 7, 2 = XP, 3 is Linux RH. I have manually swap HD to work on each operating system.
Req: A laptop with Windows 7 as main OS and two other OS (XP and Linux) Guest.
(1) I prefer not to install OS and the entire application again for the guest operating system (XP and linux), will like to convert, copy, etc.
(2) can I install multiple OS (XP) for testing of applications and then delete them?
(3) can I use a different version of an application in a guest operating system?
The software that I need to buy:
VMware workstation 7.1
Version of the converted VMware? (this may be free, I think)
ThinApp 4. ???
If these are vmware software that I need is a step by step installation, in particular of the convert.
Thank you, ralph

Hi Raoul,.

Welcome to the forums.

VMware vCenter Converter Standalone is a free download that is accessible to everyone, so you can use it to convert your existing machines.

For testing purposes, you can create a virtual machine "or" with all standard applications, and then use the function 'linked-clone"of the workstation. In this way, you can have several machines quickly with the same basic configuration to test different applications.

It is more complicated to have multiple versions of the same application in a single virtual machine. ThinApp seems to be the solution, but it should require the application packages (I have no experience with ThinApp) construction. It's a bit complicated just to test. Way the easiest would be to create a new virtual machine for each version of the application.

Workstation and the converter are very easy to install if you use a standard configuration.

Good luck.

Concerning

Franck

How to replicate laboratory installation class in your vmware workstation 7

Hello
I have completed vSphere install and configure the class last month, but because of the short time, I couldn't much laboratory class. I do lab myself I have top of the range laptop Toshiba Tecra A11-S3540 with i7 2.24 processor and memory of 8 GB. I installed vmware workstation 7 on my laptop and I have not all ESX software for installation and the official class lab manual.
Is it possible I can do same laboratory within the workstation in a proper way. as do I make team or do I need to install individual ESX hosts within the workstation or I'm not real lab in my computer. I know it is not possible to reach every piece of laboratory class, but at least I can do some hands on via lab. I just want to learn through formal laboratory because I just finished my training as a classroom and everything is fresh in my mind.
I can't buy expensive server to make the lab or my hands world real opportunity.
Any help would be great.
Thank you

I used the following instructions http://www.yellow-bricks.com/2009/05/08/running-vsphere-within-workstation-will-take-up-a-lot-of-memory/

If you find this or any other answer useful please consider awarding points marking the answer correct or useful

VMware Workstation 11 installation directory

Similar Questions

"found no hard drives installed in your computer error.

Maybe you are looking for