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

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.

Is it possible to run an existing Mac OS v10.9 or v10.10 guest VM in VmWare Player v12.0.1 (on 64bit Win 7 host OS) or is this only possible in VmWare Workstation?

At least I saw a Mac OS v10.8.5 guest VM machine which runs successfully in VmWare player on a Win 7 64bit host OS.

Surprisingly a new Mac OS v10.9 or v10.10 guest VM machine could NOT be started on the same VmWare player on the same machine.

During startup it always freezes.

So what changed in VmWare Player that it seems not to accept newer macOS guest VMs any more?

Matt

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?

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

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.

I don't think this is a duplicate post, as I haven't found an answer to the issue as yet..

I like to keep my display always on, so I have Windows' power settings set to 'Turn off the display: never' under my power plan.

However, even before powering up my guest OS (Ubuntu 15.10 at the moment), Windows' power settings get changed to 'Turn off the display: after 15 minutes' as soon as I start up Workstation 12 Player.

It was happening earlier too (late last year), on a previous install of Windows 7, but I never got around to addressing it.

Is anyone else having this issue, or able to suggest a potential fix?

Windows 7 Home Premium 64-bit (host)

VMware Workstation 12 Player

Ubuntu 15.10 Wily Werewolf 64-bit (guest)

Please Provide the me the Motherboard Model.

Hello all,

I have been having issues with my VM ever since I installed VMWare. It crashes about twice a day with the error below. Sometimes it's a different vthread crashing, but it's always the pollDefault NOT_IMPLEMENTED error. I am at my wit's end and could really use some help.

VMware Player unrecoverable error: (vthread-10)

NOT_IMPLEMENTED bora\lib\pollDefault\pollDefault.c:3914

My host OS is Windows 10 Home x64 that I upgraded from Windows 8 when I first bought my laptop. The guest OS is running Windows 7. I am using VMWare Workstation Player 12. I was previously using Workstation 11 and upgraded to 12 Player in the hopes that the error would resolve itself. Obviously, this thread indicates that the problem remained.

Attached are my log file and vmsupport ZIP.

Any help would be greatly appreciated. Thank you!

After upgrading from Windows 7 to Windows 10, I uninstalled the VMWare Workstation and then installed Workstation 12 Player.

When I try to open a Virtual Machine that was created by WMWare Workstation v71, I see the error message:
"Failed to open virtual machine: Error while loading this virtual machine's policies: VMDB failure".

Is there a way to get around this, or am I out of luck using that Virtual machine?

Hi,

It shows up but when I try to connect I get this:

and "Device driver software was not successfully installed".

Any ideas?

Jim

Just moved a UBUNTU 12.04 VM from XP Pro SP3 to W7 64b SP1 ... had to upgrade to VM Player 12.1.0

Issue: have a character based application running in Ubuntu that requires Telnet access ... in XP Pro with the VM network set to NAT the Ubuntu ifconfig IP address is accessible from XP ... in W7 I have been unable to see the Ubuntu IP address ... Ping fails ... Telnet Fails  ... started from scratch and loaded Ubuntu 14.04 ... still no IP address showing

- Both versions of Ubuntu connect to the internet

- Both versions of Ubuntu can ping the Host IP address

- Both versions immediately crash with BSOD if I choose Bridged OR vNet0 Auto Bridged settings

- Both vNet1 and vNet8 are connected and return Pings

- Norton 360 Firewall and security completely turned off ... still no IP address showing

- Ubuntu 14.04 connects to Windows share from Ubuntu so Samba config is working

- Ubuntu 14.04 telnetd was installed and configured but status indicates server isn't running

sudo apt-get install xinetd telnetd

I am not concerned about Telnet security as this is only being used on a small secure home intranet

Any suggestions would be greatly appreciated

Hi,

Maybe that has already been asked... but a quick search di end up with no real results and/or too many of them, most not relevant

So here's my question : I am currently running an "old" Mac Pro (4.1 upgraded to 5.1 ; Xeon CPU's upgraded to 2 X Hexa Cores @ 2.93Ghz ; 40GB or RAM ; several SSD's and HDD's inside the machine and outside of it).

The main system is Linux (don't ask why, but basically because I got fed up with Apple stepping backwards with each new product they release !).

I have to run Windows as a Guest OS.

VMWare allows me to do so, but I would like to improve things to have a Win 10 running even more smoothly than it does.

I think one of the major bottlenecks here is my GPU : it's an old ATI Radeon HD 5870 with 1GB of VRAM.

I am considering swapping it for a "Mac flashable card" (just in case I'll decide to resell that MacPro...).

So chances are I will get either an ATI Radeon HD 7970 (3GB RAM) or a GTX 680.

I think that performance wise they're more or less on par, but maybe VMWare uses resources  (Open CL, Cuda, Direct X...) and that would make one of the cards superior to it's competitor...

Anyone has some knowledge he'd like to share to advise on which card to choose ?

Thanks a lot.

Regards...

I realize that one cannot expect too much in regards to sound/VoIP within a VM but I would like to at least give it a try in troubleshooting this error, since the sound actually works for a short time. Basically, what happens is I start a VoIP application and make a call and talk just fine for about 3 or 4 minutes and then the sound input ceases (the other party can't hear me) and I get this vmware error:

Error while running sound stream

Recording may not work

I have tried this on multiple VoIP applications and experienced the same problem. Most of the google results I'm seeing are for the sound input never working in the first place. This is different. The sound works perfectly -- actually amazing quality -- until it suddenly stops. Even after it stops, I can still hear the other party but they say they can't hear me. I have tried using every possible setting in the Use physical sound card drop down menu of vmware. Below are my specs. Ideas?

Host: lubuntu 14.04.1 64-bit

vmware: Workstation 12 Player

Guest: Windows 7 Pro 64-bit

Hi,

I've been using vmplayer for a while, yet I cannot get two finger scroll to work in Ubuntu.

I'm using Hp omen laptop with touch screen with win 10 64 bit, I tried installing both Ubuntu 14.04 and 15.10 64 bit and both of them have the same issue.

This is what I get when I go to settings (it seems that the touchpad was not detected!!):

Any ideas?

Thanks