Install vCMA in VMware Workstation?

I would like to install the vCMA thin iPad client vSphere demo on my laptop.  Two questions:

  • Is vCMA 64-bit?
  • Can I run the vCMA as a VMware Workstation VM (and not as a device of ESXi)?

When I try to import the FVO in my computer is giving me an error of bad descriptor.

-MattG

Hi Matt,

Apparently, the current vCMA is based on CentOS 5.2 32 bit. Check with 'cat/etc/issue' and 'uname - a '.

It should work well on a workstation or player as long as it can access your vCenter or ESX via the network.

Simply, I downloaded the Zip file, compressed and open without any problems.

Good luck.

Concerning

Franck

Tags: VMware

Similar Questions

  • Problem installing Windows on VMWare Workstation 11 10

    Good evening

    I'm a french user on VMWare.

    I have a problem when I try to install Windows on VMWare Workstation 11 10, I'm stuck here:

    Capture.PNG

    I tried several times to reinstall.

    I use this iso standard: Windows10_TechnicalPreview_x64_FR - FR_9926.iso

    Can you help me?

    See you soon.

    Set up 2 x 2 cores CPU and memory: 3 GB

  • How to install 64-bit vmware workstation 9 on a win 7 64-bit operating system

    I am trying to load the 64-bit version of the workstation 9 on a 64-bit windows system 7.

    I down loaded the bundle (VMware-workstation-full-version 9.0.0 - 812388.exe) that has the 64-bit and 32-bit.  When I run the Setup, it puts

    C:\Programs(x86 folder) that I am under the impression is for 32-bit applications.

    I have two questions

    (1) how to determine which version of workstation (64 or 32) I loaded?

    (2) if it is 32, how a force installing 64-bit?

    VMware Workstation is the two 32-bit 64 bit.  On 64-bit host, it uses a 64-bit vmware-vmx with it process the lats and the Virtual Machine itself, but the front-end GUI is 32-bit.

  • install debian on vmware workstation 7 comments 8, win7 64 bit host

    Hello

    someone knows how to do this?

    I always get: "cannot find the operating system.

    The middle of my installation is an ISO. Most of the other ISO linux can be installed, such as fedora, ubuntu, suse, but NO debian (checked with 5, 6 and 7).

    What is the problem with the comments of debian?

    Thank you

    Unless you install will do a physical examination and under normal circumstances, we should not have to burn an ISO Image of an optical medium to install it on a Virtual Machine and to do so arbitrarily to install in a virtual machine is kind of insane!   I nor Darius have a problem installing the ISO Image and admission of the chinaski007 has not bothered to validate it against the checksum published then in the circumstances, it is probably a corrupt image or user of any kind error.

    Do not confuse this thread with your ISO is a URL so that it would be nice because I find it very interesting to note that if your serious about a DVD image was a valid ISO Image and would not start image but optical media of this picture, I would like to know where the fault lies as she is certainly an anomaly in the standard boot image.

  • How to configure the network adapter when you run ESXi on VmWare workstation?

    How to configure the network card installing ESXi on VmWare workstation 6.0.0?

    These are the options: I tried bridged, host-only NAP.  None of them works

    Network Setting Option.PNGNo Network Adapter.PNG

    What Miss me? driver or adapater?

    I'm running on vmware workstation on Windows 7 with Lenovo laptop.

    in the configuration of your virtual machine, the main issue is memory. you gave the 2 GB of RAM, whereas ESXi 6 cannot go forward without minimum 4 GB of RAM.

    If please have 4 GB of RAM and re-run Setup. you will get through.

    message about the network card should also not appear after that. What kind of network you choose depends on your need.

  • How to move the Virtual Machine VMWare Workstation 10 to a completely different computer

    I have a laptop that is going to become my 'old' laptop, I bought and am always set up a new computer.

    I have a VM THAT evolution created on the 'old' portable using VMWare Workstation 10.  I installed the software VMWare Workstation 10 on the new laptop computer and am ready to move to the existing VM development since the old laptop again to continue the development of software on the virtual machine to the new machine.

    I never moved a computer virtual from one computer to another, and I guess that all I have to do is to copy and move the folder and all its content from the old laptop to the new, and then I'll be back in business?

    Just make sure it is this simple before doing so.

    Thanks for any input.

    It's as simple as that. When you start in the new machine, it should ask if you copied or moved. Answer that you moved it will keep the same MAC address and you will not be able to connect the two copies at the same time. You copied it saying assigns a new MAC and they both can connect, but a Windows machine can ask to reactivate. Seems to me he asked also to reactivate when I copied it for an Intel system AMD system, but it was a long time ago

    Lou

  • 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?

  • VMware Workstation 7.1 on Windows 7 x 64

    Hello

    I installed the new VMware Workstation 7.1 on my x 64 windows 7, before I download there written x 32 - x 64 version but when I start default insstallation installation location was C:\*Program files (x 86) * \VMware, which means application for x 32 bit x 64 No.

    I have Intel E8400 CPU, MB: Maximus formula

    so is - anyone can write any solution about it.

    Thank you

    sikvdila wrote:

    I installed the new VMware Workstation 7.1 on my x 64 windows 7, before I download there written x 32 - x 64 version but when I start default insstallation installation location was C:\*Program files (x 86) * \VMware, which means application for x 32 bit x 64 No.

    You should not use the installation folder as the basis for that determination.  Pieces of VMware Workstation are 32-bit while we have x 64 versions for other parts.  We decided that it would be simpler to install all in one place, rather than splitting to the top of the installation on both 'Program Files' and 'Program Files (x 86) ".

    I've just interested in my vmawre runs as x64bit softare or x 32?

    What does "run as software 64-bit" mean?  The user interface is a 32-bit process (vmware.exe), but virtual machines are running in 64-bit processes (vmware - vmx.exe).  The 32-bit process will run as a 32-bit software and 64-bit processes will run as 64 - bit ones.

  • K6V69AV #ABA: HP Desktop 500-520qe: cannot install VMWare Workstation

    I try to install the virtual machine using vmware workstation or vmware player.  But it gives me the message saying Intel vt - x is not enabled. I've seen a few videos youtube that says that I need to enable virtualization, but I don't seem to have seen.  Can anyone suggest if there is something else?

    Hello

    Open the command run and enter: MSINFO32

    The returned information will tell you if virtualization is enabled.  If this isn't the case, then you need to make a change in the BIOS to turn on VT is defined by default to disable.  See the image below.

  • VMware Workstation 12.1.1 Pro is unable to install the network grows on CentOS 6.8 host

    Just upgraded my 6.7 CentOS Server (where the VMware Workstation 12.1.1 worked fine) to 6.8.

    After a reboot, VMware has done, it is usual thing where she wanted to reinstall its readers. He doesn't have to install the network component. Here are my logs:

    2016-05-28T18:21:09.477-07:00| vthread-4| I125: Log for VMware Workstation pid=27658 version=12.1.1 build=build-3770994 option=Release
2016-05-28T18:21:09.477-07:00| vthread-4| I125: The process is 64-bit.
2016-05-28T18:21:09.477-07:00| vthread-4| I125: Host codepage=UTF-8 encoding=UTF-8
2016-05-28T18:21:09.477-07:00| vthread-4| I125: Host is Linux 2.6.32-642.el6.x86_64 CentOS release 6.8 (Final)
2016-05-28T18:21:09.476-07:00| vthread-4| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory.
2016-05-28T18:21:09.476-07:00| vthread-4| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.
2016-05-28T18:21:09.476-07:00| vthread-4| I125: DictionaryLoad: Cannot open file "/home/sa_schewee/.vmware/config": No such file or directory.
2016-05-28T18:21:09.476-07:00| vthread-4| I125: PREF Optional preferences file not found at /home/sa_schewee/.vmware/config. Using default values.
2016-05-28T18:21:09.501-07:00| vthread-4| W115: Logging to /tmp/vmware-root/vmware-27658.log
2016-05-28T18:21:09.511-07:00| vthread-4| I125: Obtaining info using the running kernel.
2016-05-28T18:21:09.511-07:00| vthread-4| I125: Created new pathsHash.
2016-05-28T18:21:09.511-07:00| vthread-4| I125: Setting header path for 2.6.32-642.el6.x86_64 to "/lib/modules/2.6.32-642.el6.x86_64/build/include".
2016-05-28T18:21:09.511-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.511-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h
2016-05-28T18:21:09.511-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
2016-05-28T18:21:09.518-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.518-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid.  Whoohoo!
2016-05-28T18:21:09.587-07:00| vthread-4| I125: found symbol version file /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers
2016-05-28T18:21:09.587-07:00| vthread-4| I125: Reading symbol versions from /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers.
2016-05-28T18:21:09.597-07:00| vthread-4| I125: Read 12201 symbol versions
2016-05-28T18:21:09.597-07:00| vthread-4| I125: Reading in info for the vmmon module.
2016-05-28T18:21:09.597-07:00| vthread-4| I125: Reading in info for the vmnet module.
2016-05-28T18:21:09.597-07:00| vthread-4| I125: Reading in info for the vmblock module.
2016-05-28T18:21:09.597-07:00| vthread-4| I125: Reading in info for the vmci module.
2016-05-28T18:21:09.597-07:00| vthread-4| I125: Reading in info for the vsock module.
2016-05-28T18:21:09.597-07:00| vthread-4| I125: Setting vsock to depend on vmci.
2016-05-28T18:21:09.597-07:00| vthread-4| I125: Invoking modinfo on "vmmon".
2016-05-28T18:21:09.600-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.
2016-05-28T18:21:09.600-07:00| vthread-4| I125: Invoking modinfo on "vmnet".
2016-05-28T18:21:09.601-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.
2016-05-28T18:21:09.601-07:00| vthread-4| I125: Invoking modinfo on "vmblock".
2016-05-28T18:21:09.603-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.
2016-05-28T18:21:09.603-07:00| vthread-4| I125: Invoking modinfo on "vmci".
2016-05-28T18:21:09.605-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.
2016-05-28T18:21:09.605-07:00| vthread-4| I125: Invoking modinfo on "vsock".
2016-05-28T18:21:09.607-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.
2016-05-28T18:21:09.618-07:00| vthread-4| I125: to be installed: vmnet status: 0
2016-05-28T18:21:09.624-07:00| vthread-4| I125: Obtaining info using the running kernel.
2016-05-28T18:21:09.624-07:00| vthread-4| I125: Setting header path for 2.6.32-642.el6.x86_64 to "/lib/modules/2.6.32-642.el6.x86_64/build/include".
2016-05-28T18:21:09.624-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.624-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h
2016-05-28T18:21:09.624-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
2016-05-28T18:21:09.632-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.632-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid.  Whoohoo!
2016-05-28T18:21:09.701-07:00| vthread-4| I125: found symbol version file /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers
2016-05-28T18:21:09.702-07:00| vthread-4| I125: Reading symbol versions from /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers.
2016-05-28T18:21:09.711-07:00| vthread-4| I125: Read 12201 symbol versions
2016-05-28T18:21:09.711-07:00| vthread-4| I125: Kernel header path retrieved from FileEntry: /lib/modules/2.6.32-642.el6.x86_64/build/include
2016-05-28T18:21:09.711-07:00| vthread-4| I125: Update kernel header path to /lib/modules/2.6.32-642.el6.x86_64/build/include
2016-05-28T18:21:09.711-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.711-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h
2016-05-28T18:21:09.711-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
2016-05-28T18:21:09.719-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.719-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid.  Whoohoo!
2016-05-28T18:21:09.720-07:00| vthread-4| I125: Found compiler at "/usr/bin/gcc"
2016-05-28T18:21:09.724-07:00| vthread-4| I125: Got gcc version "4.4.7".
2016-05-28T18:21:09.724-07:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.
2016-05-28T18:21:09.724-07:00| vthread-4| I125: Using user supplied compiler "/usr/bin/gcc".
2016-05-28T18:21:09.727-07:00| vthread-4| I125: Got gcc version "4.4.7".
2016-05-28T18:21:09.727-07:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.
2016-05-28T18:21:09.729-07:00| vthread-4| I125: Trying to find a suitable PBM set for kernel "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.729-07:00| vthread-4| I125: No matching PBM set was found for kernel "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.729-07:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.
2016-05-28T18:21:09.729-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.729-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h
2016-05-28T18:21:09.729-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
2016-05-28T18:21:09.737-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.737-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid.  Whoohoo!
2016-05-28T18:21:09.738-07:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.
2016-05-28T18:21:09.738-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.738-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h
2016-05-28T18:21:09.738-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
2016-05-28T18:21:09.746-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.746-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid.  Whoohoo!
2016-05-28T18:21:09.746-07:00| vthread-4| I125: Using temp dir "/tmp".
2016-05-28T18:21:09.747-07:00| vthread-4| I125: Obtaining info using the running kernel.
2016-05-28T18:21:09.747-07:00| vthread-4| I125: Setting header path for 2.6.32-642.el6.x86_64 to "/lib/modules/2.6.32-642.el6.x86_64/build/include".
2016-05-28T18:21:09.747-07:00| vthread-4| I125: Validating path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for kernel release "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.747-07:00| vthread-4| I125: Failed to find /lib/modules/2.6.32-642.el6.x86_64/build/include/generated/utsrelease.h
2016-05-28T18:21:09.747-07:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
2016-05-28T18:21:09.755-07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "2.6.32-642.el6.x86_64".
2016-05-28T18:21:09.755-07:00| vthread-4| I125: The header path "/lib/modules/2.6.32-642.el6.x86_64/build/include" for the kernel "2.6.32-642.el6.x86_64" is valid.  Whoohoo!
2016-05-28T18:21:09.825-07:00| vthread-4| I125: found symbol version file /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers
2016-05-28T18:21:09.825-07:00| vthread-4| I125: Reading symbol versions from /lib/modules/2.6.32-642.el6.x86_64/build/Module.symvers.
2016-05-28T18:21:09.834-07:00| vthread-4| I125: Read 12201 symbol versions
2016-05-28T18:21:09.834-07:00| vthread-4| I125: Invoking modinfo on "vmnet".
2016-05-28T18:21:09.836-07:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.
2016-05-28T18:21:10.081-07:00| vthread-4| I125: Setting destination path for vmnet to "/lib/modules/2.6.32-642.el6.x86_64/misc/vmnet.ko".
2016-05-28T18:21:10.081-07:00| vthread-4| I125: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar".
2016-05-28T18:21:10.087-07:00| vthread-4| I125: Successfully extracted the vmnet source.
2016-05-28T18:21:10.087-07:00| vthread-4| I125: Building module with command "/usr/bin/make -j8 -C /tmp/modconfig-tH7bci/vmnet-only auto-build HEADER_DIR=/lib/modules/2.6.32-642.el6.x86_64/build/include CC=/usr/bin/gcc IS_GCC_3=no"
2016-05-28T18:21:11.063-07:00| vthread-4| W115: Failed to build vmnet.  Failed to execute the build command.

    Hi, I faced the same problem, and now I have corrected this issue.

    He was vmnet.ko, at least for me.

    Here's how to solve,

    You can find the latest vmnet.ko of /lib/modules/~previous_kernel_version~/misc/vmnet.ko

    Copy vmnet.ko into your current/lib/modules/your_current_version/misc folder.

    And then run vmware, if you fail at the first, please run again.

    If so, you can run vmwre!

    I hope this will help you.

    Good day.

  • The upgrade from VMware Workstation 12: can I install above?

    So I just bought a license to upgrade to workstation 12. Now, I noticed that it is (finally) 64-bit native. However, 11 Workstation is native 32-bit. Can I just install VMware Workstation 12 top like I did the upgrade from 10 to 11? Because the 10 and 11 were native 32-bit.

    The question is moot.
    Upgrade has always meant uninstall the old version, install the new version.
    If you do it yourself, you have more control, but the results will be the same.

    The safest option is: uninstall manually - reboot - check registry for services that have not been removed - if necessary, repair registry - restarts again and then install the new version right after the restart.

  • Cannot install VMware Workstation on Windows 8.1 Pro 64 bit 11.1.1 - Please help

    You want to install VMware Workstation 11.1.1 on new 8.1 Windows Pro 64-bit PC.

    I had VMware Workstation 11.1.0, and deleted the original installer but did not finish the installation of the new version

    The installer gets about 2/3 way (progress bar) and then crashes, Windows Installer says Event Viewer hung.

    Race tried without firewall and AV, always not install question

    A ran the installer with / clean option and then tried again, but still he did not finish the installation process (crashes at the same place)

    Noticed in the Manager tasks that VMware Installer runs at about 14% of CPU, but nothing happens

    I'm really at a loss as to why I can't install VMware Workstation 11.1.1, all the other soft\ware settles very well.

    Please could someone help me?

    Thank you

    Peter

    Ran Windows Update Troubleshooter

    It fixed a number of things

    I could then install VMware Workstation

    No idea but why the installer got himself in this State

  • VMware Workstation 11 crashes after installing VMware tools

    As the title suggests, VMware Workstation 11 crashes after installing VMware Tools with a guest Windows 7 x 64. I am running VMware on a host Windows 7 x 64. It happens every time I try to install the guest operating system. Attached to this post are all the newspapers that I could find that I thought would help solve the problem.


    Thank you

    Wila

    Hello again,

    Maybe the following post helps (where you installed Visual Studio)

    How to troubleshoot Workstation (vmui) - Access Violation Crash? How to troubleshoot Workstation Crash (vmui) - Access Violation? How to troubleshoot Workstation Crash (vmui) - Access Violation?

    --

    Wil

    As you may already know, VMware has just released a major update for 11 workstation (including VMware tools updated). Workstation now works almost perfectly. I don't have accidents since then. This means that I have was right in my post above. This is indeed nothing more than a BETA version of VMware buggy, lazy, masked as a "final". Wow, it looks like that a respectable company like this would not resort to such unethical practices. I mean that you would expect this kind of crap of a company like Electronic Arts, but VMware? Come on guys, you're better than this!

  • VMware tools install fails - Centos 6.2 on VMware Workstation 8

    Some setting in context.

    ArcSight make an OVF vmware assessment based on Centos 6.2. I am able to install VMware tools on the ESXi 5.1 platform supported but NOT on VMware Workstation version 8.0.6 build 1035888 which is apparently not supported but works fine on my laptop.


    The big problem here is that the time on the host computer is massively adrift without VMware tools and make more from the point of the eval worthless SIEM.


    I'm sure it's a problem of script, but is not certain. When configuring VMware tools that occurs the following


    START INSTALLATION TEXT

    [root@logger bin]./vmware-config-tools.pl # ]

    Initializing...

    Ensuring services for VMware Tools are arrested.

    [EXPERIMENTAL] The synchronization of VMware filesystem (vmsync) driver is a new feature which

    creates backups of virtual machines. Please refer to the VMware Knowledge Base

    For more details on this ability. You want to enable this feature?

    [None]

    Before you can compile modules, you must have the following installed...

    do

    CCG

    headers of the kernel running kernel

    Looking for a CCG...

    The path "" is not a valid path to the GCC binary.

    You want to change it? [Yes]

    What is the location of the program CCG on your machine? CCG

    The path "/ usr/bin/gcc" is not a valid path to the GCC binary.

    You want to change it? [Yes]

    TEXT OF INSTALLATION END

    I played with the script Perl, but similar problems continue with the location of the kernel headers having precisely defined the variable PATH CCG.

    A few pieces of information of the host.

    [root@logger bin] # uname - m.

    2.6.32 - 220.EL6.x86_64 x86_64

    [root@logger bin] # gcc - v

    Using plug integrated.

    Target: x86_64-redhat-linux

    Configured with:... / configure - prefix = / usr - mandir = / usr/share/man - infodir = / usr/share/info-with-bugurl = http://Bugzilla.redhat.com/Bugzilla --enable-bootstrap--enable-shared--enable-threads = posix--enable-vérification = libération--with-système-zlib--enable-__cxa_atexit--disable-libunwind-exceptions--enable-gnu-unique-objet--enable-langues = c, c ++, objc, obj-c + +, java, fortran, ada--enable-java-awt = gtk--disable-dssi--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre--enable-libgcj-multifile--enable-java-maintainer-mode--with-ecj-jar=/usr/share/java/eclipse-ecj.jar--disable-libjava-multilib--avec-ppl--avec-cloog--avec-tune = generic--avec arch_32 = i686--build = x86_64-redhat-linux

    Thread model: posix

    GCC version 4.4.6 20110731 (Red Hat 4.4.6 - 3) (CCG)

    [root@logger bin] # / usr/bin/make - v

    GNU Make 3.81

    Copyright (C) 2006 Free Software Foundation, Inc.

    This is free software; See the source for copying conditions.

    There is NO WARRANTY; not even a MARKET value or fitness for a

    PARTICULAR PURPOSE.

    This program built for x86_64-unknown-linux-gnu

    [root@logger bin] # / usr/bin/make - v

    GNU Make 3.81

    Copyright (C) 2006 Free Software Foundation, Inc.

    This is free software; See the source for copying conditions.

    There is NO WARRANTY; not even a MARKET value or fitness for a

    PARTICULAR PURPOSE.

    This program built for x86_64-unknown-linux-gnu

    [root@logger bin] #


    Thank you in advance. Kevin

    I solved this problem by upgrading VM Workstation v10 v8.

    All installed now.

    As a newbie here, is there a way I can move this post a status resolved?

  • Cannot install VMWare workstation... Help, please

    Greetings and respect, community.

    I'm having a problem installing VMWare Workstation 8 or 9...

    Here is the error message

    Error: 'c:\users\admin~1\AppData\Local\Temp\vmware_1371916406\vmware workstation.msi' failed

    I deleted TEMP files. I did everything that I could find about this error.


    My laptop configuration

    Oenvironment system: Windows 7 Ultimate 64 - bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130104 - 1431)

    Language: English (regional setting: English)

    Manufacturer: Hewlett-Packard

    Model: HP Pavilion Notebook PC g6

    BIOS: Version InsydeH2O 03.61.01F.32

    Processor: Intel (r) Core i3 - 2330M CPU @ 2.20 GHz (4 CPUs), ~2.2GHz

    Memory: 4096 MB RAM

    Available OS memory: 4044MB RAM

    Page file: 3003MB used, 5081 MB of available space

    Windows Dir: C:\Windows

    Please help me solve this error message


    Hi akpraveenand welcome to the VMware communities!

    Your laptop has Avast! Antivirus installed?  We have seen some recent reports of Avast! origin of the failure you see there.  If you have Avast! installed, you will need to uninstall temporarily to be able to install VMware Workstation (disabling Avast! is not enough).

    If you use another system antivirus or antimalware software, it may be interesting to try to disable it during the installation of VMware Workstation.

    Let us know if that solved the problem for you!

    --

    Darius

Maybe you are looking for