Environment:

Ubuntu Server 15.04

VMware-Player-7.1.0-2496824.x86_64.bundle

Hello,

The kernel module updater fails to build vmnet:

2015-05-08T11:55:17.757+02:00| vthread-4| I120: Successfully extracted the vmnet source.

2015-05-08T11:55:17.757+02:00| vthread-4| I120: Building module with command "/usr/bin/make -j8 -C /tmp/modconfig-Hx4jdX/vmnet-only auto-build HEADER_DIR=/lib/modules/3.19.0-16-generic/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2015-05-08T11:55:18.894+02:00| vthread-4| W110: Failed to build vmnet.  Failed to execute the build command.

No more description of the error is available in the log which is attached below.

Any suggestion?

Hi All

I have installed Windows Server 2008 on Vmware player but one thing I am facing very weird, Guest OS is shutdown automatically after few hours, I have set  Guest OS Power Options to NEVER but still I am facing the same, can anyone help ?

Host - Windows 7   8GB Ram

Guest  - Windows Server 2008    4 GB Ram

Thanks

ds4u

Nuts & Bolts of DataStage

Host is an Asus notebook (N-series) with Windows 8.1. Two-finger gestures are enabled (ASUS "Smart Gestures").

Guest OSes, on latest VMware Player are: Windows 10 Preview, and Linux Mint 17.

In both guest OSes I couldn't get two-finger scroll working so far.

The ASUS touchpad in system devices, on Host OS, is just described as "ASUS Touchpad", duh.

I also tried the "Two-Finger Scroll" application on Host two-finger-scroll - Two finger gestures for Synaptics TouchPads on Windows - Google Project Hosting

but it gives an error: interface not registered.

Hi guys,

I'm running a Linux Mint guest on Win7 x32 using VMWare Player 6.0.5. It's basically going well, but I'm unable to install Tools. I open a terminal in the directory of the extracted files, then run the command under SUDO, but the command is not found. I'm attaching a shot of the command line and the target directory.

I re-extracted the Tools package, which is why the folder has " (2) appended to it, but that made no difference. Any help would be appreciated.

Paul

HI:

I've got a Win 2012 R2 Essentials server running under ESXi 5.5. I'd like to experiment with disaster recovery by running VMWare Player, or Workstation, or whatever on a 64 bit Win7 Pro and copying the VM files from the server to the Workstation. Then hopefully as a test, the server could be shut down and restarted on the Win7 workstation. Of course the workstation will have to have enough resources to handle it's os, plus vmware plus the server os, and performance might suffer.

This seems like it should work. In the distant past I once copied a virtual machine between an ESXi 3.5 and 4.0 machine as a test and it worked.

Do you guys have any recommendations, or comments concerning VMWare Player or Workstation for this exercise?

Thanks in advance.

Cla.

when configuring the latest VMWare tools, I receive the following error:

"The vmxnet driver is no longer supported on kernels 3.3 and greater. Please  upgrade to a newer virtual NIC. (e.g., vmxnet3 or e1000e)"

I have followed instructions on a few different posts to try to fix this, and none have worked.

I have tried running the vmware tools configuration script with --clobber-kernel-modules=vmxnet - that didn't help.

I tried changing ethernet0.virtualDev = "vmxnet" to "vmxnet3" in the .vmx file - that didn't help either.

Running Ubuntu 14.04 on VMWare Player 6.0.6 build-2700073 on Windows 7. The VM image in question is Ubuntu 14.04 on Linux kernel 1.13.0-43.

This is for bridged mode (which I need) - running in NAT mode works fine.

$ uname -a

Linux ubuntu 3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

dust@ubuntu:~/Desktop/vmware-tools-distrib

$ sudo ./vmware-install.pl --clobber-kernel-modules=vmxnet

The previous installation was made by the tar installer (version 4).

Keeping the tar4 installer database format.

You have a version of VMware Tools installed.  Continuing this install will

first uninstall the currently installed version.  Do you wish to continue?

(yes/no) [yes]

Uninstalling the tar installation of VMware Tools.

Stopping services for vmware-tools

vmware-tools stop/waiting

Stopping services for vmware-tools-thinprint

vmware-tools-thinprint stop/waiting

File /etc/pulse/default.pa is backed up to /etc/pulse/default.pa.old.8.

update-initramfs: Generating /boot/initrd.img-3.13.0-43-generic

update-initramfs: Generating /boot/initrd.img-3.13.0-39-generic

The removal of VMware Tools 9.6.5 build-2700074 for Linux completed

successfully.

Installing VMware Tools.

In which directory do you want to install the binary files?

[/usr/bin]

What is the directory that contains the init directories (rc0.d/ to rc6.d/)?

[/etc]

What is the directory that contains the init scripts?

[/etc/init.d]

In which directory do you want to install the daemon files?

[/usr/sbin]

In which directory do you want to install the library files?

[/usr/lib/vmware-tools]

The path "/usr/lib/vmware-tools" does not exist currently. This program is

going to create it, including needed parent directories. Is this what you want?

[yes]

In which directory do you want to install the documentation files?

[/usr/share/doc/vmware-tools]

The path "/usr/share/doc/vmware-tools" does not exist currently. This program

is going to create it, including needed parent directories. Is this what you

want? [yes]

The installation of VMware Tools 9.6.5 build-2700074 for Linux completed

successfully. You can decide to remove this software from your system at any

time by invoking the following command: "/usr/bin/vmware-uninstall-tools.pl".

Before running VMware Tools for the first time, you need to configure it by

invoking the following command: "/usr/bin/vmware-config-tools.pl". Do you want

this program to invoke the command for you now? [yes]

Initializing...

Making sure services for VMware Tools are stopped.

The module vmci has already been installed on this system by another installer

or package and will not be modified by this installer.

The module vsock has already been installed on this system by another installer

or package and will not be modified by this installer.

The module vmxnet3 has already been installed on this system by another

installer or package and will not be modified by this installer.

The module pvscsi has already been installed on this system by another

installer or package and will not be modified by this installer.

The module vmmemctl has already been installed on this system by another

installer or package and will not be modified by this installer.

The VMware Host-Guest Filesystem allows for shared folders between the host OS

and the guest OS in a Fusion or Workstation virtual environment.  Do you wish

to enable this feature? [yes]

Before you can compile modules, you need to have the following installed...

make

gcc

kernel headers of the running kernel

Searching for GCC...

Detected GCC binary at "/usr/bin/gcc".

The path "/usr/bin/gcc" appears to be a valid path to the gcc binary.

Would you like to change it? [no]

Searching for a valid kernel header path...

Detected the kernel headers at "/lib/modules/3.13.0-43-generic/build/include".

The path "/lib/modules/3.13.0-43-generic/build/include" appears to be a valid

path to the 3.13.0-43-generic kernel headers.

Would you like to change it? [no]

Using 2.6.x kernel build system.

make: Entering directory `/tmp/modconfig-OyHNrF/vmhgfs-only'

/usr/bin/make -C /lib/modules/3.13.0-43-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \

      MODULEBUILDDIR= modules

make[1]: Entering directory `/usr/src/linux-headers-3.13.0-43-generic'

  CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/backdoor.o

  CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/backdoorGcc64.o

  CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/bdhandler.o

  CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/cpName.o

  CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/cpNameLinux.o

  CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/cpNameLite.o

  CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/dentry.o

  CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/dir.o

  CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/file.o

  CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/filesystem.o

  CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/fsutil.o

  CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/hgfsBd.o

  CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/hgfsEscape.o

  CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/hgfsUtil.o

  CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/inode.o

  CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/link.o

  CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/message.o

  CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/module.o

  CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/page.o

  CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/request.o

  CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/rpcout.o

  CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/stubs.o

  CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/super.o

  CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/transport.o

  CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/vmci.o

  CC [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/kernelStubsLinux.o

  LD [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/vmhgfs.o

  Building modules, stage 2.

  MODPOST 1 modules

  CC      /tmp/modconfig-OyHNrF/vmhgfs-only/vmhgfs.mod.o

  LD [M]  /tmp/modconfig-OyHNrF/vmhgfs-only/vmhgfs.ko

make[1]: Leaving directory `/usr/src/linux-headers-3.13.0-43-generic'

/usr/bin/make -C $PWD SRCROOT=$PWD/. \

      MODULEBUILDDIR= postbuild

make[1]: Entering directory `/tmp/modconfig-OyHNrF/vmhgfs-only'

make[1]: `postbuild' is up to date.

make[1]: Leaving directory `/tmp/modconfig-OyHNrF/vmhgfs-only'

cp -f vmhgfs.ko ./../vmhgfs.o

make: Leaving directory `/tmp/modconfig-OyHNrF/vmhgfs-only'

The vmxnet driver is no longer supported on kernels 3.3 and greater. Please

upgrade to a newer virtual NIC. (e.g., vmxnet3 or e1000e)

The vmblock enables dragging or copying files between host and guest in a

Fusion or Workstation virtual environment.  Do you wish to enable this feature?

[yes]

VMware automatic kernel modules enables automatic building and installation of

VMware kernel modules at boot that are not already present. This feature can be

enabled/disabled by re-running vmware-config-tools.pl.

Would you like to enable VMware automatic kernel modules?

[yes]

Thinprint provides driver-free printing. Do you wish to enable this feature?

[yes]

Disabling timer-based audio scheduling in pulseaudio.

Detected X server version 1.15.1

Distribution provided drivers for Xorg X server are used.

Skipping X configuration because X drivers are not included.

Creating a new initrd boot image for the kernel.

update-initramfs: Generating /boot/initrd.img-3.13.0-43-generic

vmware-tools-thinprint start/running

vmware-tools start/running

The configuration of VMware Tools 9.6.5 build-2700074 for Linux for this

running kernel completed successfully.

You must restart your X session before any mouse or graphics changes take

effect.

You can now run VMware Tools by invoking "/usr/bin/vmware-toolbox-cmd" from the

command line.

To enable advanced X features (e.g., guest resolution fit, drag and drop, and

file and text copy/paste), you will need to do one (or more) of the following:

1. Manually start /usr/bin/vmware-user

2. Log out and log back into your desktop session; and,

3. Restart your X session.

Enjoy,

--the VMware team

$ ~

Tento instalar a versão 6. Embora tecle primeiramente su, após o ENTER a mensagem é de Permissão negada. O estranho é que isso aconteceu depois que reinstalei o Mint, pois na 1a. vez, naõ enfrentei essas "coisas"...

Hello,

I want to test the linux kernel's mpt2sas driver. It is a driver for LSI Logic SCSI SAS-2 controller. I do not have the HW, and hence want to use VMPlayer to test it.

I see that VMware releases drivers for those controllers and hence this is a hardware that VMware can emulate:

https://my.vmware.com/web/vmware/details?downloadGroup=DT-ESXI5X-LSI-MPT2SAS-151006001VMW&productId=285

I installed VMplayer, and created a VM, but it did not have the

controller I wanted. I noticed that while creating the VM, if I change

the OS that I will be running on the VM, the VMplayer automatically

chooses a different SCSI controller (depending on what the gues OS has

drivers for, I believe). So after some experiments, the best I could

get (by selecting Windows Server 2012) is:

(from lspci output):

03:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS1068 PCI-X Fusion-MPT SAS (rev 01)

However, what I want is a SAS-2 controller, something like:

03:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 (rev 03)

Can you please let me know if I can emulate the SAS-2 controller using VMplayer?

Thanks,

Rajat

Hi there,

I'm running Windows 7 x86 Professional and VMware Player 3.0.0. Windows 7 is set to 150% larger fonts (DPI scaling).

If I start VMware Player with this DPI setting the guest VM is scaled aswell. If I set Windows 7 NOT to use DPI scaling only for VMware Player about 25% of the guest's screen is unreachable (lower-right). (See this screenshot: http://pix.sonhult.se/vmware.jpg)

The guest is running Ubuntu 9.10 x86.

Have anyone else been experimenting with DPI scaling and VMware Player? Any ideas?

Thanks in advance!

I;m a non commercial user of VMware player, mainly using it for illustrator 9.0. A day a go I tried to open the virtual player and got the following message:

Hi,

I am using vmware player 7.1.0 in windows 7. I installed ubuntu in it, with internet NAT setting it's working fine when I created. But once in a blue it stop the ethernet connection when starting my VM, from then ethernet connections are missing. I got this bug twice.

I checked with another os in the same vm they are working fine.

Please help me how to get ethernet connections back.

Kiran

Hi all,

VMWare newbie here. I'm migrating from VirtualBox to VMWare player and I can say this virtual system is really more efficient. However I'm working on a project were I need to use a ESC/POS printer.

Is a generic USB thermal printer, nothing fancy, but works fine on Ubuntu 14.04 (host 64bit). The problem is when I try to use it on the guest machine, another Ubuntu 14.04 (32bit) whit the latest guest tools.

I'm aware of thinprint, I know it create a serial port to connect to the host printer, and my pos printer is present on cups on port tpvmgp://POS58:2. I've tried to install directly on the guest using the drivers of the vendors but since the printer is not identified as an USB the cups settings are wrong.

When I try to connect to the guest the printer I get the message:

The specified device is claimed by another driver (usblp) on the host operating system. The device might be in use. To continue, the device will first be disconnected from its current driver.

When I try to print the document is processed and putted on "held". If I release it, the document will back to "held" instantaneously.

Any clue?

Thanks.

Hello,

I've just updated my kernel to 3.10.0-997-generic. After that VMWare Player doesn't start anymore.

I've tried to run patches and different solutions I found in google, but it didn't worked yet.

This is the log of my last attempt.

Thanks in advance

2013-06-14T21:42:29.306-03:00| vthread-3| I120: Log for VMware Workstation pid=14806 version=9.0.2 build=build-1031769 option=Release

2013-06-14T21:42:29.306-03:00| vthread-3| I120: The process is 64-bit.

2013-06-14T21:42:29.306-03:00| vthread-3| I120: Host codepage=UTF-8 encoding=UTF-8

2013-06-14T21:42:29.306-03:00| vthread-3| I120: Host is Linux 3.10.0-997-generic Ubuntu 12.10

2013-06-14T21:42:29.306-03:00| vthread-3| I120: Msg_Reset:

2013-06-14T21:42:29.306-03:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": No such file or directory.

2013-06-14T21:42:29.306-03:00| vthread-3| I120: ----------------------------------------

2013-06-14T21:42:29.306-03:00| vthread-3| I120: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.

2013-06-14T21:42:29.306-03:00| vthread-3| I120: Msg_Reset:

2013-06-14T21:42:29.306-03:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/config": No such file or directory.

2013-06-14T21:42:29.306-03:00| vthread-3| I120: ----------------------------------------

2013-06-14T21:42:29.306-03:00| vthread-3| I120: PREF Optional preferences file not found at /root/.vmware/config. Using default values.

2013-06-14T21:42:29.306-03:00| vthread-3| I120: Msg_Reset:

2013-06-14T21:42:29.306-03:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/preferences": No such file or directory.

2013-06-14T21:42:29.306-03:00| vthread-3| I120: ----------------------------------------

2013-06-14T21:42:29.306-03:00| vthread-3| I120: PREF Failed to load user preferences.

2013-06-14T21:42:29.306-03:00| vthread-3| W110: Logging to /tmp/vmware-root/vmware-modconfig-14806.log

2013-06-14T21:42:29.318-03:00| vthread-3| I120: Reading in info for the vmmon module.

2013-06-14T21:42:29.318-03:00| vthread-3| I120: Reading in info for the vmnet module.

2013-06-14T21:42:29.318-03:00| vthread-3| I120: Reading in info for the vmblock module.

2013-06-14T21:42:29.318-03:00| vthread-3| I120: Reading in info for the vmci module.

2013-06-14T21:42:29.318-03:00| vthread-3| I120: Reading in info for the vsock module.

2013-06-14T21:42:29.318-03:00| vthread-3| I120: Setting vsock to depend on vmci.

2013-06-14T21:42:29.318-03:00| vthread-3| I120: Created new pathsHash.

2013-06-14T21:42:29.318-03:00| vthread-3| I120: Invoking modinfo on "vmmon".

2013-06-14T21:42:29.320-03:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.

2013-06-14T21:42:29.320-03:00| vthread-3| I120: Invoking modinfo on "vmnet".

2013-06-14T21:42:29.322-03:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.

2013-06-14T21:42:29.322-03:00| vthread-3| I120: Invoking modinfo on "vmblock".

2013-06-14T21:42:29.324-03:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.

2013-06-14T21:42:29.324-03:00| vthread-3| I120: Invoking modinfo on "vmci".

2013-06-14T21:42:29.326-03:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.

2013-06-14T21:42:29.326-03:00| vthread-3| I120: Invoking modinfo on "vsock".

2013-06-14T21:42:29.328-03:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.

2013-06-14T21:42:29.345-03:00| vthread-3| I120: Obtaining info using the running kernel.

2013-06-14T21:42:29.345-03:00| vthread-3| I120: Setting header path for 3.10.0-997-generic to "/lib/modules/3.10.0-997-generic/build/include".

2013-06-14T21:42:29.345-03:00| vthread-3| I120: Validating path "/lib/modules/3.10.0-997-generic/build/include" for kernel release "3.10.0-997-generic".

2013-06-14T21:42:29.351-03:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "3.10.0-997-generic".

2013-06-14T21:42:29.351-03:00| vthread-3| I120: The header path "/lib/modules/3.10.0-997-generic/build/include" for the kernel "3.10.0-997-generic" is valid.  Whoohoo!

2013-06-14T21:42:29.517-03:00| vthread-3| I120: Kernel header path retrieved from FileEntry: /lib/modules/3.10.0-997-generic/build/include

2013-06-14T21:42:29.517-03:00| vthread-3| I120: Update kernel header path to /lib/modules/3.10.0-997-generic/build/include

2013-06-14T21:42:29.517-03:00| vthread-3| I120: Validating path "/lib/modules/3.10.0-997-generic/build/include" for kernel release "3.10.0-997-generic".

2013-06-14T21:42:29.523-03:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "3.10.0-997-generic".

2013-06-14T21:42:29.523-03:00| vthread-3| I120: The header path "/lib/modules/3.10.0-997-generic/build/include" for the kernel "3.10.0-997-generic" is valid.  Whoohoo!

2013-06-14T21:42:29.524-03:00| vthread-3| I120: Found compiler at "/usr/bin/gcc"

2013-06-14T21:42:29.526-03:00| vthread-3| I120: Got gcc version "4.7".

2013-06-14T21:42:29.526-03:00| vthread-3| I120: GCC minor version 4 does not match Kernel GCC minor version 4.  But that is ok.

2013-06-14T21:42:29.526-03:00| vthread-3| I120: Using user supplied compiler "/usr/bin/gcc".

2013-06-14T21:42:29.528-03:00| vthread-3| I120: Got gcc version "4.7".

2013-06-14T21:42:29.528-03:00| vthread-3| I120: GCC minor version 4 does not match Kernel GCC minor version 4.  But that is ok.

2013-06-14T21:42:29.532-03:00| vthread-3| I120: Trying to find a suitable PBM set for kernel "3.10.0-997-generic".

2013-06-14T21:42:29.532-03:00| vthread-3| I120: No matching PBM set was found for kernel "3.10.0-997-generic".

2013-06-14T21:42:29.532-03:00| vthread-3| I120: Validating path "/lib/modules/3.10.0-997-generic/build/include" for kernel release "3.10.0-997-generic".

2013-06-14T21:42:29.538-03:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "3.10.0-997-generic".

2013-06-14T21:42:29.538-03:00| vthread-3| I120: The header path "/lib/modules/3.10.0-997-generic/build/include" for the kernel "3.10.0-997-generic" is valid.  Whoohoo!

2013-06-14T21:42:29.538-03:00| vthread-3| I120: GCC minor version 4 does not match Kernel GCC minor version 4.  But that is ok.

2013-06-14T21:42:29.539-03:00| vthread-3| I120: Validating path "/lib/modules/3.10.0-997-generic/build/include" for kernel release "3.10.0-997-generic".

2013-06-14T21:42:29.545-03:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "3.10.0-997-generic".

2013-06-14T21:42:29.545-03:00| vthread-3| I120: The header path "/lib/modules/3.10.0-997-generic/build/include" for the kernel "3.10.0-997-generic" is valid.  Whoohoo!

2013-06-14T21:42:29.545-03:00| vthread-3| I120: GCC minor version 4 does not match Kernel GCC minor version 4.  But that is ok.

2013-06-14T21:42:29.545-03:00| vthread-3| I120: Using temp dir "/tmp".

2013-06-14T21:42:29.547-03:00| vthread-3| I120: Invoking modinfo on "vmnet".

2013-06-14T21:42:29.548-03:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.

2013-06-14T21:42:29.548-03:00| vthread-3| I120: Invoking modinfo on "vmblock".

2013-06-14T21:42:29.550-03:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.

2013-06-14T21:42:29.550-03:00| vthread-3| I120: Invoking modinfo on "vmci".

2013-06-14T21:42:29.552-03:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.

2013-06-14T21:42:30.327-03:00| vthread-3| I120: Setting destination path for vmnet to "/lib/modules/3.10.0-997-generic/misc/vmnet.ko".

2013-06-14T21:42:30.327-03:00| vthread-3| I120: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar".

2013-06-14T21:42:30.332-03:00| vthread-3| I120: Successfully extracted the vmnet source.

2013-06-14T21:42:30.332-03:00| vthread-3| I120: Building module with command "/usr/bin/make -j8 -C /tmp/modconfig-YkpUyf/vmnet-only auto-build HEADER_DIR=/lib/modules/3.10.0-997-generic/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2013-06-14T21:42:31.977-03:00| vthread-3| W110: Failed to build vmnet.  Failed to execute the build command.

2013-06-14T21:42:31.979-03:00| vthread-3| I120: Setting destination path for vmblock to "/lib/modules/3.10.0-997-generic/misc/vmblock.ko".

2013-06-14T21:42:31.979-03:00| vthread-3| I120: Extracting the vmblock source from "/usr/lib/vmware/modules/source/vmblock.tar".

2013-06-14T21:42:31.990-03:00| vthread-3| I120: Successfully extracted the vmblock source.

2013-06-14T21:42:31.990-03:00| vthread-3| I120: Building module with command "/usr/bin/make -j8 -C /tmp/modconfig-YkpUyf/vmblock-only auto-build HEADER_DIR=/lib/modules/3.10.0-997-generic/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2013-06-14T21:42:33.429-03:00| vthread-3| W110: Failed to build vmblock.  Failed to execute the build command.

2013-06-14T21:42:33.431-03:00| vthread-3| I120: Setting destination path for vmci to "/lib/modules/3.10.0-997-generic/misc/vmci.ko".

2013-06-14T21:42:33.431-03:00| vthread-3| I120: Extracting the vmci source from "/usr/lib/vmware/modules/source/vmci.tar".

2013-06-14T21:42:33.445-03:00| vthread-3| I120: Successfully extracted the vmci source.

2013-06-14T21:42:33.446-03:00| vthread-3| I120: Building module with command "/usr/bin/make -j8 -C /tmp/modconfig-YkpUyf/vmci-only auto-build HEADER_DIR=/lib/modules/3.10.0-997-generic/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2013-06-14T21:42:35.773-03:00| vthread-3| I120: Successfully built vmci.  Module is currently at "/tmp/modconfig-YkpUyf/vmci.o".

2013-06-14T21:42:35.773-03:00| vthread-3| I120: Found the vmci symvers file at "/tmp/modconfig-YkpUyf/vmci-only/Module.symvers".

2013-06-14T21:42:35.774-03:00| vthread-3| I120: Installing vmci from /tmp/modconfig-YkpUyf/vmci.o to /lib/modules/3.10.0-997-generic/misc/vmci.ko.

2013-06-14T21:42:35.774-03:00| vthread-3| I120: Registering file "/lib/modules/3.10.0-997-generic/misc/vmci.ko".

2013-06-14T21:42:36.234-03:00| vthread-3| I120: "/usr/lib/vmware-installer/2.1.0/vmware-installer" exited with status 0.

2013-06-14T21:42:36.234-03:00| vthread-3| I120: Registering file "/usr/lib/vmware/symvers/vmci-3.10.0-997-generic".

2013-06-14T21:42:36.686-03:00| vthread-3| I120: "/usr/lib/vmware-installer/2.1.0/vmware-installer" exited with status 0.

I recently installed VMWare Player on a Windows 2012 Server virtual machine at work to run a Cloudera Linux VM distribution, but every time I start the VM through VMWare it just stops. No error information and no other popup either. I'm confused because I've looked for some log files in the ProgramData directory under VMWare, however I don't see anything related to a LOG file. Has anybody else seen this behavior or know where the log files are? I'm using VMware Player v7.1.0 build-2496824 and trying to run the Cloudera VM from this download site:

http://www.cloudera.com/content/cloudera/en/downloads/quickstart_vms/cdh-5-4-x.html

Dear all,

I have been struggling with this for days now.

Specs which might be of interest: 64-bit machine with host Windows 7.

All I want to do is get Lubuntu up and running (Light-weight Ubuntu is the idea).  I first tried 32-bit versions of VM Player.

Installing VMware Tools has been OK with Ubuntu 15.04 and 14.04: screen resizing, copy-paste between host <-> guest fine.  I have tried over and again to get shared folders - it simply does not work.  I have done a lot of googling... and followed a lot of what people have said. 

Latest thing which leaves me flabbergasted is that I downloaded the latest version of VM Player: "64-bit for Windows".  Long story short: VMware Tools does not install, and the tar.gz file is nowhere to be found: Player --> Manage --> Install VMware tools results in *precisely nothing happening at all*.  Locating to the CD-ROM drive shows that it is ominously called "Lubuntu 14.0..." (not "VMware Tools...") and the vmware installation tar.gz is NOWHERE TO BE FOUND.

My installation protocol involves running software updater, and then apt-get build-essential.  As I say, I have succeeded with the 32-bit VM Players in getting VMware Tools to work... except for the essential shared folders thing.

Latest thinking: maybe I should get a much older version of VM Player.  Maybe the latest versions are just not fit for purpose. 

I regard myself as quite computery... for years I've harboured this idea of migrating over to Linux.  Every few years I make another attempt.  But the barriers to quite preposterous for someone working on their own.  On an old machine I have Lubuntu running fine.  But a VM on my main machine?  Gaaah.  I despair.

I have been using VMWare Player for a while now and really enjoy it.  I have it installed on a couple PCs that are connected to a domain network.  Each host machine is Windows 7 as well as each guest VM on it.  I have them all configured with NAT and that works great....well it did up until this morning.  Yesterday all was good and I could connect to other servers on the netowrk as well as get out to the internet from the guest machines.  Today that is not the case.  No internet/network connectivity.   Funny thing is that all 3 seperate VMs I have set up on 3 different host PCs have the same issue. All worked fine yesterday.  I have tried disabling/enabling the virtual network adapters, VMnet1 and VMnet8, without any change.  I do have netowrk connectivity on all 3 host PCs so really cant understand why all 3 VMs are having this issue.  Any thoughts?  Any suggestions on a fix?  Thanks.

I'm trying to use Bluetooth headset (LG HBM-210) on the Vmware Player guest.  Both guest and host are running Windows 8.1 x64.

The Bluetooth headset  is paired and working as indicated by the Device Manager and Bluetooth Settings in both guest and host.

The headset is working perfectly in the host, but I cannot see the Bluetooth headset from the Control Panel>Sound of the guest.

How do I make the headset connect to the guest.

Two screen shots are attached.

Thanks

Installed Ubuntu 14.04 Guest and updated and all good.

Followed instructions on this page and almost all good

http://theholmesoffice.com/how-to-share-folders-between-windows-and-ubuntu-using-vmware-player/

Ran this command and it shows the drives and folders that I defined as Shared-Folders

vmware-hgfsclient

Ran this and it put shortcuts on the desktop

ln -s /mnt/hgfs/shared-directory ~/Desktop/Name-of-the-folder  {edit} Yes, I used the real Shared Folder names

If I double click on the shortcut OR try to copy a file to it from Ubuntu, I get

This link cannot be used because its target “/mnt/hgfs/shared-directory” doesn't exist.

Where am I going wrong?

And, how do I make it work?

Also /mnt/hgfs is empty even with Ctrl-H

Also edited the fstab file as per...

VMware Workstation 10 Documentation Center

.host:/ /mnt/hgfs vmhgfs defaults 0 0

Rebooted Ubuntu and got an error "Error mounting hgfs - S=skip, M=manual fix."

I skipped.

No matter which button I push, it ignores it and starts over in a loop. I am trying to create a VM of Win 7 from an MDT iso image. I have done this dozens of times until this week, now this pop up window prevents me from doing so.

I have tried several different user accts. I have tried it locally on the same box. I have even removed the last 2 months worth of patches and updates from the system, nothing seems to work.

I downloaded the trial version of VMWare Workstation 11.  When I do the install it tries to uninstall VMWare Player 7.  The uninstall fails with the cryptic error message 'MSI Fail.'

I've found various articles about this around the web and even tried a few 'solutions' to no avail.  Is there a sure fire way to uninstall the Player so I can try the Workstation?