Hi all,

I can't for the life of me figure out if I'm blind or if this just isn't built into Workstation Player 12.

In my guest OS (Windows 10 x86) I have an exe that is minimized to the tray. When I go into Unity mode I am unable to see the program in the tray of the host OS (Windows 10 x64). If I then exit Unity and view the guest OS in a window, the program is visible in the tray. Is it possible to show the guest OS tray in the host while in Unity mode?

I know this is possible using Parallels on a Mac but as I am new the VMWare and only trailing at the moment I was hoping it is something that is achievable.

Many thanks all!

I have an integrated Intel Arrandale HD Graphics card:

DirectX 10

OpenGL 2.1

With this card on Windows host 3D acceleration in Windows guest works fine in VMware:

- Player 7

- Workstation Player 12 when using this fix Re: Workstation 12 Pro: No 3D support is available from the host. The 3D features of the virtual machine will be disabled.

On Linux host 3D acceleration in Windows guest doesn't work neither in Player 7 nor in Workstation Player 12.

I already tried:

- different Linux distros

- ensured that 3D acceleration works in Linux itself

- installed libtxc-dxtn-s2tc-bin and libtxc-dxtn-s2tc0 packages

- added mks.gl.allowBlacklistedDrivers = "TRUE"

So questions are:

1. Is there a magic setting to make VMware work for my card?

2. I make a suspicion that it works on Windows host because it uses not yet EOL DirectX 10 API there and doesn't work on Linux as it uses probably EOL OpenGL 2.1 API there.

So what is the requirement for OpenGL version that card must support?

3. What VMWare products of which versions will work for my card?

Thanks!

Solution:

     Properly configuring your Virtual Controller of your guest VM likely the most successful way to prevent this issues.

Symptoms:

     While testing DMA functionality of one of our USB devices our test was failing due to incorrect data (data corruption) being received. We looked into the failure further and discovered one method of causing this was by leaving the default usb virtual controller default configuration of 3.0 when only usb 2.0 was supported or vice versa. This only affects Windows 8 and 10, Windows 7 was not affected so maybe this is an Microsoft problem.

Summary:

     The Help does not mention that this step is required but merely saying if select xHCI then everything works. VMware support stated that configuring as a 2.0 or 3.0 explicitly was the expect way to do it. We have logs from both sides of the vm that the corruption is occurring in the virtual USB controller and no an issue with our driver or our device.  Most of the time the 3.0 controller worked fine for other transfer mechanisms but for our DMA transfers we typically saw corruption very quickly.

During one case a expected value was 39 and we received x27 after the virtual controller. Notice status is showing everything is ok.

USB Monitor log (inside VM)

Request:

     Can someone document or give me a ticket # stating that this is an issue and I'll document it for my customer? I want to defer these VM configuration questions your way to help ensure the end customers get the correct information.

Hi,

i want to use the "cycle multiple monitors" feature with a disabled topbar.

I disabled the bar, using pref.vmplayer.fullscreen.nobar = "TRUE" in the preferences.ini.

It works all well to the point, i want to use my second monitor, because there is no hotkey for this feature. (i only saw the button in the bar so far)

So my question is now:

Is there any opportunity to use "cycle multiple monitors" without using the topbar, like a hidden hotkey?

Using Windows 8 Pro x64 with 16GB RAM as host and Windows 7 Home, Vista Home and Ubuntu 13.04 all 32bit (all 3GB of RAM and 4 virtual cores)

best regards,

thxandbye

VMware Player 7.1.2 build-2780323 running on Ubuntu 14.04 3.13.0-79-generic

I'm having a Devil of a time with Solaris.  The Live ISO would boot to a GUI, and the pointer was there and moving around with the mouse, but any click would just drop down Applications, I think it was.  The text installer just froze.  I can start gparted by tabbing and arrowing around, and it sees a single 290.24MB disk.

Any tricks to making this work?

If I power off a VM, the whole VMware Player closes, and I have to re-open it.  How do I keep Player itself open and running until I close it?

I'm getting the following error after installing a Windows 7 Machines with the VMware Workstation 12 Player:

VMware Player unrecoverable error: (vthread-11) Exception 0xc0000005(access violation) has occurred.

I have tried it with Win7-32Bit and Win7-64Bit.

The host ist an Win 10 System with a I7-6700 and a Mainboard Gigabyte GA-B150-HD3P and it es a privat environment.

For both VM-machines I have saved the folder with the Log-files. 

Maybe there is a solution for this problem.

Hello,

I'm using VMWare workstation player 12 in linux (LXLE distribution, based on ubuntu), with a guest OS based on windows XP. This setup is working fine whenever I configure it with "bridged" or "NAT". Strangely, I don't have the option "custom" in my network settings, so I cannot test it.

Now, for security concerns, I'd like the guest would connect to different network of the host.

For that purpose, I created a VLAN and configured everything so that the host is receiving both VLAN tagged (via a virtual eth0.2 NIC) and "normal" untagged traffic (via the physical eth0 NIC). I also created a virtual bridge (bridge-utils package - brctl commands) where I associated the eth0.2 NIC.

In other words:

eth0 (physical) --> receives "normal" lan packets, gets its IP via the DHCP server from the 192.168.2.x network. This is my home LAN, which I want to keep secured, and therefore don't want the guest to access.

eth0.2 (virtual, based on the physical eth0) --> receives and decodes VLAN2 tagged packets, gets its IP via the DHCP server from the 192.168.1.x network. This is an external LAN, which I don't mind if its secured or not and where I'd like the guest to connect.

br0 --> virtual bridge witch has the eth0.2 card. I believe id need to add to it some sort of "vmnet" card in order to establish communication to the external LAN.

I'd believe what I'm missing here is to somehow add a vmnet NIC to the bridge, but unfortunately I don't have a vmnet0 NIC neither the option "custom" in the VMWare network settings.

Other alternative would be, maybe, to associate the bridge option (in VMWare player network settings) to eth0.2 instead of eth0, but either way, I'm not being able to get it sorted.

My ifconfig -a only reports:

- br0 (bridge)

- eth0 (physical NIC)

- eth0.2 (virtual NIC associated to the VLAN)

- vmnet1 (which I believe is NAT)

- vmnet8 (which I believe is Host-to-host)

Any idea/suggestion on how can I close this gap? I feel I'm so close and yet so far....

Thanks,

Joao

Hi,

Newbie, so likely I'm doing something obviously wrong, but here goes:

I have used the standalone VMWare vCentre Convertor to create a VM of a laptop drive I want as a VM, which has run successfully.  However, when I try to open this in Player, I get the following error:

This virtual machine is configured for 64-bit guest operating systems. However, 64-bit operation is not possible.

This host supports Intel VT-x, but Intel VT-x is disabled.

Intel VT-x might be disabled if it has been disabled in the BIOS/firmware settings or the host has not been power-cycled since changing this setting.

(1) Verify that the BIOS/firmware settings enable Intel VT-x and disable 'trusted execution.'

(2) Power-cycle the host if either of these BIOS/firmware settings have been changed.

(3) Power-cycle the host if you have not done so since installing VMware Player.

(4) Update the host's BIOS/firmware to the latest version.

For more detailed information, see http://vmware.com/info?id=152.

The Host machine is running 64-Bit Win10, and I've run the recommended Intel check tool and it confirms VT-x is available, and the VMWare tool confirms 64-bit operation.  The Host is a HP Z840 Xeon ES-2620 2.4GHz 16GB RAM running Win10 Pro 64-bit.  The machine that was converted to a VM using convertor is a Core i7-2670QM 2.2GHz 8GB RAM Win 7 Ultimate 64-bit laptop.

Any/all help very gratefully received!

TC

I installed VMWare Workstation Player 12.1.0-3272444.x86_64 onto a Linux Mint 17.3 (3.19.0-32-generic Kernel) system. From what I've read, the issue with being unable to launch the initial VMWare GUI is supposed to be fixed at this release.

The installation went exceptionally smoothly and I had no problems getting a VM up and running. It's a personal non-commercial installation BTW.

However, on about one load in five of the Host OS, the Launcher for VMWare just seems to time out and the initial GUI is never presented no matter how many times you try. Rebooting the Host OS invariably seems to clear the problem - until the next time.

I looked in /var/log/vmware and the only files are of the vmware-usbarb-nnnn.log variety.

In a failure situation the log file always ends like this :-

2016-03-06T12:43:25.722Z| usbArb| I125: USBArbRuleStore: Loading device rules from '/etc/vmware/usbarb.rules'.

2016-03-06T12:43:25.722Z| usbArb| I125: VMware USB Arbitration Service Version 15.1.7

2016-03-06T12:43:25.722Z| usbArb| I125: USBGL: USB Sysfs found at /dev/bus/usb

2016-03-06T12:43:25.722Z| usbArb| I125: USBArb: Attempting to connect to existing arbitrator on /var/run/vmware/usbarbitrator-socket.

2016-03-06T12:43:25.722Z| usbArb| I125: SOCKET creating new socket, connecting to /var/run/vmware/usbarbitrator-socket

2016-03-06T12:43:25.722Z| usbArb| I125: SOCKET connect failed, error 2: No such file or directory

2016-03-06T12:43:25.722Z| usbArb| I125: USBArb: Failed to connect to the existing arbitrator.

whereas in a success situation it continues :-

2016-03-06T13:31:16.234Z| usbArb| I125: USBArbRuleStore: Loading device rules from '/etc/vmware/usbarb.rules'.

2016-03-06T13:31:16.234Z| usbArb| I125: VMware USB Arbitration Service Version 15.1.7

2016-03-06T13:31:16.235Z| usbArb| I125: USBGL: USB Sysfs found at /dev/bus/usb

2016-03-06T13:31:16.235Z| usbArb| I125: USBArb: Attempting to connect to existing arbitrator on /var/run/vmware/usbarbitrator-socket.

2016-03-06T13:31:16.235Z| usbArb| I125: SOCKET creating new socket, connecting to /var/run/vmware/usbarbitrator-socket

2016-03-06T13:31:16.235Z| usbArb| I125: SOCKET connect failed, error 2: No such file or directory

2016-03-06T13:31:16.235Z| usbArb| I125: USBArb: Failed to connect to the existing arbitrator.

2016-03-06T13:31:49.920Z| usbArb| I125: USBArb: UsbArbPipeConnected: Connected to client, socket:4

2016-03-06T13:31:54.115Z| usbArb| I125: USBArb: Client 3018 connected (version: 7)

2016-03-06T13:34:07.570Z| usbArb| I125: USBArb: UsbArbPipeConnected: Connected to client, socket:12

2016-03-06T13:34:39.180Z| usbArb| I125: USBArb: Client 3644 connected (version: 7)

and then there are messages relating to the successful starting and eventual shutdown of the client OS VM.

My knowledge/skill level in this area is very low so I'd be most grateful for any help in trying to understand what is happening here and hopefully correct it.

I have the workstation 12 player and upgraded to windows 10. Now the xpmode will not load. "xpmode not allowed"

Anyone know how to fix this?

My VMware player keeps freezing on me when my freezes up (like during backup or virusscan), but when the host response again, the player does not.  I can see the clock moving and if I had something running I can see responses in the window, but the player will no longer accept input from either the keyboard or the mouse.  I can't do anything but kill it with Task Manager on the host.  Once I've done that, I then have to log off my host and log back in before it will let me start the player again.

Is there anything I can do to prevent this or recover without having to log completely off my host?

Before upgrading to Win 10, I have graphics resolution problems with VMware Workstation 12 Player Using a Dell Optiplex 7010, the graphics displays could be set to 1920x1080 before using ISO 8.1 Pro x64, now since the upgrade, the best setting I can set the VM too is 1152x864 resolution and it's using the Microsoft Basic Display Adapter???, that no good.

Is there a way I can get a higher resolution back in the display settings which I had previously at 1920x1080?

Cheers

edit by wila : Discussion moved from VMware Fusion® (for Mac) to Workstation Player

I was trying to install VMware Player 6.0.2 in a Windows 8.1 Professional 64-bit O/S.

I kept on having "Script Error" (cf image below).

After some investigations, I found out the cause of the problem.  It's because the user name contains an apostrophe.  In some countries, it's natural to have an apostrophe in the name, eg Jeanne d'Arc.  For privacy issue, I won't mention the real name in my case, so let's say it's Jeanne d'Arc.  In this problem, the path to "index.htm" is

C:\users\Jeanne d'Arc\AppData\Local\Temp\vmware_xxxxxxx\index.htm

Then I created another user name "Jeanne d Arc".  I used this new account to run the setup again and I didn't have the "Script Error".  It's then clear to me that the apostrophe in user name (and thus in file path) was the cause of the problem.

I suspect this problem can also occur for VMware Workstation setup.

Hi,

on Workstation player 12, on Windows 10 host.

A VM with Wi Server 2008 can not ping Host and can not connect to internet.

Here are configurations :

And in Vm machine :

But at start it can not connect to Host and get a correct IP. Then it has default IP (168.....)

Thank you for help.

Hey all, bear with me I'm a Linux newbie and even of a noob with VMware player...

I have CentOS setup as a virtual machine, my PC is running Win7. When I make changes to CentOS, i.e. I set an image for the desktop background, I configured MySQL, Apache, edited default profile to change the look of the terminal window, etc., all done while logged in as root...When I reload CentOS in the player, all changes are gone and its reverted back to the default install config.

Every single time little things such as the desktop background image, & terminal settings are gone, but the changes to Apache, etc. are random. A few times it saved the config changes I made, but this last time after I reloaded they were all gone and it was back to the default install config....

Is the player corrupt and I need to remove/reinstall? Is it some stupid setting I'm missing that needs to be enabled? Am I screwing something up in CentOS itself?

TIA!

Hello,

I have a High DPI (3000x2000) Screen notebook with 13,5 Zoll with Windows 10

I still need a Windows 8.1 so I installed it in the VM Ware Player. So far so good, the DPI setting is passed to the VM Guest. in Windows itself no big issues, but as you know, not all programs like this high DPI settings.

I would prefer to restrict the Guest resolution to max of 1600x...or may be better 1400x... with a normal DPI setting. I can set up this resolution somehow, but if I enable full Screen it changes or it shows me a small window on the black background.

I was expecting to have the Screen scaled (magnified) to the Full screen. The correct english term is "stretch" .

How to I do this. I could not find any Option or possibility in the VM Player 12 (NOT the full workstation).

Kind regards and many thanks

Markus

Hey, I've have Vmware on my PC for a long time but now i cant get rid of it. it came from andydroid and its really annoying. can some help me uninstall it cause i cant do it,or can i get get the link to the version that i have? Thanks

I installed vmware on fedora 23,  precise version:vmware-player, 12.1.0.3272444

I has installed kernel devel, kernel header, of my kernel version. installed GCC, make & CO. under ubuntu called build-essential.

VMware ask to compile kernel module, it compile module, but cannot start via systemd

I has just setenforce 0

Graphics interface, return that there a error, and that has produced a log in tmp, file:/tmp/vmware-****/vmware-8212.log

<--------------------------------------------------------------------------------------------------------------------------------->

2016-03-12T18:00:21.679+01:00| modconfig| I125: Log for VMware Workstation pid=8212 version=12.1.0 build=build-3272444 option=Release

2016-03-12T18:00:21.679+01:00| modconfig| I125: The process is 64-bit.

2016-03-12T18:00:21.679+01:00| modconfig| I125: Host codepage=UTF-8 encoding=UTF-8

2016-03-12T18:00:21.679+01:00| modconfig| I125: Host is Linux 4.4.2-301.fc23.x86_64 Fedora release 23 (Twenty Three)

2016-03-12T18:00:21.679+01:00| modconfig| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory.

2016-03-12T18:00:21.679+01:00| modconfig| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.

2016-03-12T18:00:21.679+01:00| modconfig| I125: DictionaryLoad: Cannot open file "/root/.vmware/config": No such file or directory.

2016-03-12T18:00:21.679+01:00| modconfig| I125: PREF Optional preferences file not found at /root/.vmware/config. Using default values.

2016-03-12T18:00:21.722+01:00| modconfig| I125: Initialized!  Lets do this thing...

2016-03-12T18:00:21.722+01:00| modconfig| I125: Obtaining info using the running kernel.

2016-03-12T18:00:21.722+01:00| modconfig| I125: Created new pathsHash.

2016-03-12T18:00:21.722+01:00| modconfig| I125: Setting header path for 4.4.2-301.fc23.x86_64 to "/lib/modules/4.4.2-301.fc23.x86_64/build/include".

2016-03-12T18:00:21.722+01:00| modconfig| I125: Validating path "/lib/modules/4.4.2-301.fc23.x86_64/build/include" for kernel release "4.4.2-301.fc23.x86_64".

2016-03-12T18:00:21.722+01:00| modconfig| I125: Failed to find /lib/modules/4.4.2-301.fc23.x86_64/build/include/linux/version.h

2016-03-12T18:00:21.722+01:00| modconfig| I125: /lib/modules/4.4.2-301.fc23.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2016-03-12T18:00:21.722+01:00| modconfig| I125: using /usr/bin/gcc for preprocess check

2016-03-12T18:00:21.735+01:00| modconfig| I125: Preprocessed UTS_RELEASE, got value "4.4.2-301.fc23.x86_64".

2016-03-12T18:00:21.735+01:00| modconfig| I125: The header path "/lib/modules/4.4.2-301.fc23.x86_64/build/include" for the kernel "4.4.2-301.fc23.x86_64" is valid.  Whoohoo!

2016-03-12T18:00:21.921+01:00| modconfig| I125: found symbol version file /lib/modules/4.4.2-301.fc23.x86_64/build/Module.symvers

2016-03-12T18:00:21.921+01:00| modconfig| I125: Reading symbol versions from /lib/modules/4.4.2-301.fc23.x86_64/build/Module.symvers.

2016-03-12T18:00:21.942+01:00| modconfig| I125: Read 16483 symbol versions

2016-03-12T18:00:21.942+01:00| modconfig| I125: Reading in info for the vmmon module.

2016-03-12T18:00:21.942+01:00| modconfig| I125: Reading in info for the vmnet module.

2016-03-12T18:00:21.942+01:00| modconfig| I125: Reading in info for the vmblock module.

2016-03-12T18:00:21.942+01:00| modconfig| I125: Reading in info for the vmci module.

2016-03-12T18:00:21.942+01:00| modconfig| I125: Reading in info for the vsock module.

2016-03-12T18:00:21.942+01:00| modconfig| I125: Setting vsock to depend on vmci.

2016-03-12T18:00:21.956+01:00| modconfig| I125: Trying to find a suitable PBM set for kernel "4.4.2-301.fc23.x86_64".

2016-03-12T18:00:21.956+01:00| modconfig| I125: No matching PBM set was found for kernel "4.4.2-301.fc23.x86_64".

2016-03-12T18:00:21.956+01:00| modconfig| I125: Found compiler at "/usr/bin/gcc"

2016-03-12T18:00:21.961+01:00| modconfig| I125: Got gcc version "5.3.1".

then i try this for, compile modules by command line:

~]# bash -x vmware-modconfig --console --build-mod vmnet

+ set -e

+ ETCDIR=/etc/vmware

+ . /etc/vmware/bootstrap

++ PREFIX=/usr

++ BINDIR=/usr/bin

++ SBINDIR=/usr/sbin

++ LIBDIR=/usr/lib

++ DATADIR=/usr/share

++ SYSCONFDIR=/etc

++ DOCDIR=/usr/share/doc

++ MANDIR=/usr/share/man

++ INCLUDEDIR=/usr/include

++ INITDIR=/etc/rc.d

++ INITSCRIPTDIR=/etc/rc.d/init.d

+ VMISETCDIR=/etc/vmware-installer

+ . /etc/vmware-installer/bootstrap

++ VMWARE_INSTALLER=/usr/lib/vmware-installer/2.1.0

++ VERSION=2.1.0

++ VMISVERSION=2.1.0

++ VMISBUILDNUM=3215781

++ VMISPYVERSION=25

+ libdir=/usr/lib/vmware

+ export VMWARE_INSTALLER

+ args=

+ uiType=

+ useConsole=0

+ for i in '"$@"'

+ '[' --console = --console ']'

+ useConsole=1

+ for i in '"$@"'

+ '[' --build-mod = --console ']'

+ args=' --build-mod'

+ for i in '"$@"'

+ '[' vmnet = --console ']'

+ args=' --build-mod vmnet'

+ '[' -z \:0\]' i has add \ becose convert in emoticon

+ '[' 1 = 1 ']'

+ uiType=-console

+ export PATH=/sbin:/usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin

+ PATH=/sbin:/usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin

+ exec /usr/lib/vmware/bin/vmware-modconfig-console --build-mod vmnet

make: ingresso nella directory "/tmp/modconfig-W5uVO5/vmnet-only"

Using kernel build system.

/usr/bin/make -C /lib/modules/4.4.2-301.fc23.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \

  MODULEBUILDDIR= modules

make[1]: ingresso nella directory "/usr/src/kernels/4.4.2-301.fc23.x86_64"

  CC [M]  /tmp/modconfig-W5uVO5/vmnet-only/driver.o

  CC [M]  /tmp/modconfig-W5uVO5/vmnet-only/hub.o

  CC [M]  /tmp/modconfig-W5uVO5/vmnet-only/userif.o

  CC [M]  /tmp/modconfig-W5uVO5/vmnet-only/netif.o

In file included from include/linux/pci.h:35:0,

                 from /tmp/modconfig-W5uVO5/vmnet-only/compat_netdevice.h:27,

                 from /tmp/modconfig-W5uVO5/vmnet-only/netif.c:43:

include/linux/pci_ids.h:2252:0: warning: "PCI_VENDOR_ID_VMWARE" redefined

#define PCI_VENDOR_ID_VMWARE  0x15ad

^

In file included from /tmp/modconfig-W5uVO5/vmnet-only/net.h:38:0,

                 from /tmp/modconfig-W5uVO5/vmnet-only/vnetInt.h:26,

                 from /tmp/modconfig-W5uVO5/vmnet-only/netif.c:42:

/tmp/modconfig-W5uVO5/vmnet-only/vm_device_version.h:56:0: note: this is the location of the previous definition

#define PCI_VENDOR_ID_VMWARE                    0x15AD

^

  CC [M]  /tmp/modconfig-W5uVO5/vmnet-only/bridge.o

  CC [M]  /tmp/modconfig-W5uVO5/vmnet-only/procfs.o

  CC [M]  /tmp/modconfig-W5uVO5/vmnet-only/smac_compat.o

  CC [M]  /tmp/modconfig-W5uVO5/vmnet-only/smac.o

In file included from /tmp/modconfig-W5uVO5/vmnet-only/net.h:38:0,

                 from /tmp/modconfig-W5uVO5/vmnet-only/vnetInt.h:26,

                 from /tmp/modconfig-W5uVO5/vmnet-only/bridge.c:52:

/tmp/modconfig-W5uVO5/vmnet-only/vm_device_version.h:56:0: warning: "PCI_VENDOR_ID_VMWARE" redefined

#define PCI_VENDOR_ID_VMWARE                    0x15AD

^

In file included from include/linux/pci.h:35:0,

                 from /tmp/modconfig-W5uVO5/vmnet-only/compat_netdevice.h:27,

                 from /tmp/modconfig-W5uVO5/vmnet-only/bridge.c:51:

include/linux/pci_ids.h:2252:0: note: this is the location of the previous definition

#define PCI_VENDOR_ID_VMWARE  0x15ad

^

  CC [M]  /tmp/modconfig-W5uVO5/vmnet-only/vnetEvent.o

  CC [M]  /tmp/modconfig-W5uVO5/vmnet-only/vnetUserListener.o

  LD [M]  /tmp/modconfig-W5uVO5/vmnet-only/vmnet.o

  Building modules, stage 2.

  MODPOST 1 modules

  CC      /tmp/modconfig-W5uVO5/vmnet-only/vmnet.mod.o

  LD [M]  /tmp/modconfig-W5uVO5/vmnet-only/vmnet.ko

make[1]: uscita dalla directory "/usr/src/kernels/4.4.2-301.fc23.x86_64"

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

  MODULEBUILDDIR= postbuild

make[1]: ingresso nella directory "/tmp/modconfig-W5uVO5/vmnet-only"

make[1]: "postbuild" è aggiornato.

make[1]: uscita dalla directory "/tmp/modconfig-W5uVO5/vmnet-only"

cp -f vmnet.ko ./../vmnet.o

make: uscita dalla directory "/tmp/modconfig-W5uVO5/vmnet-only"

and finally:

~]# systemctl start vmware

Job for vmware.service failed because the control process exited with error code. See "systemctl status vmware.service" and "journalctl -xe" for details.

~]# systemctl status vmware

● vmware.service - SYSV: This service starts and stops VMware services

   Loaded: loaded (/etc/rc.d/init.d/vmware)

   Active: failed (Result: exit-code) since sab 2016-03-12 18:37:28 CET; 10min ago

     Docs: man:systemd-sysv-generator(8)

  Process: 14400 ExecStart=/etc/rc.d/init.d/vmware start (code=exited, status=1/FAILURE)

   CGroup: /system.slice/vmware.service

           ├─1287 /usr/lib/vmware/bin/vmware-vmblock-fuse -o subtype=vmware-vmblock,default_permissions,allow_other /var/run/vmblock-fuse

           └─1332 /usr/sbin/vmware-authdlauncher

mar 12 18:37:28 nocturne vmware[14400]: Virtual machine monitor[FAIL]

mar 12 18:37:28 nocturne vmware[14400]: Virtual machine communication interface[  OK  ]

mar 12 18:37:28 nocturne vmware[14400]: VM communication interface socket family[  OK  ]

mar 12 18:37:28 nocturne vmware[14400]: Blocking file system[  OK  ]

mar 12 18:37:28 nocturne vmware[14400]: Virtual ethernet[FAIL]

mar 12 18:37:28 nocturne vmware[14400]: VMware Authentication Daemon[  OK  ]

mar 12 18:37:28 nocturne systemd[1]: vmware.service: Control process exited, code=exited status=1

mar 12 18:37:28 nocturne systemd[1]: Failed to start SYSV: This service starts and stops VMware services.

mar 12 18:37:28 nocturne systemd[1]: vmware.service: Unit entered failed state.

mar 12 18:37:28 nocturne systemd[1]: vmware.service: Failed with result 'exit-code'.

Someone know how to resolve?

The title basically says it all.  This happend to me about a year ago with Mint 17.0 and I had a very hard time installing it.  There was a patch and a series of line commands.  It was so aweful that I was just happy when it finally worked.  I dont remember what I did and I just need to make it work again.

It seems to install ok but when I run Player then it ask me for permission to install some more stuff then fails:  something with vmnet or something like that.  I know millions of people must be having this problem but there is no clear cut solution that I can find on the net.  I have a 64 bit laptop and everthing worked fine there.  Appearently VMware is starting to stop all software support of 32 bit systems but I just bought this laptop and I am not ready to buy another desktop.   Thanks.