Are you the publisher? Claim or contact us about this channel


Embed this content in your HTML

Search

Report adult content:

click to rate:

Account: (login)

More Channels


Showcase


Channel Catalog


Channel Description:

All Content in Workstation Player

older | 1 | .... | 148 | 149 | (Page 150) | 151 | 152 | .... | 252 | newer

    0 0

    New Dell tablet with windows 10 PRO 64bit with the latest Workstation Player 12.1.

    I confirmed I downloaded the 64bit version

    taskmanager reflects 32bit

    is that because the virtual running is Win7 32bit?

     

    Sorry for newbie question

     

    this is what I downloaded and installed

     

    • VMware-player-12.1.1-3770994.exe
    • 3770994
    • 2016-04-21
    • MD5SUM: 7c55b7bac62746806b888cc36f8bbad4
      SHA1SUM: d63e0d2b95e1ba23afd1a9d04137b0ff8ea58cfc

     

    vmware 32bit.png

     

    system.png


    0 0

    So I was on a Win7 virtual machine, and I downloaded a shady software on purpose. My host's Avast blocked two viruses, so I rolled back to a snapshot and pledged to only use the VM for tech support scambaiting because I don't want my host to get wrecked, let alone allow viruses on my network where my mother has her work laptop.

    Make sure you're using a VPN and have up-to-date antivirus software before messing with viruses.


    0 0

    Hi guys I used to be able to create a osx virtual machine on my Elitebook 2540p i7. I tried reinstalling player 12 but when I try to create a machine i can't choose OSX anymore I have Virtual Technology on in my bios settings. Is there anyone that had this problem or knows how to get it back up an running again?


    0 0

    I'm trying to install player 12 on Windows 10 (VMware-player-12.1.1-3770994.exe). It silently fails when run from desktop icon (as admin or not) and command prompt (also admin or not). Also disabling antivirus prior to install doesn't seem to make any difference.

    It comes up with the splash screen, then a little dialog which is displayed and closed too fast to read then nothing...

    There don't seem to be any error messages on the windows log.

    Player 12 installs and runs flawlessly on Ubuntu.

    Any suggestions for either getting it to install or figuring out why it isn't?

    Cheers


    0 0

    I have a DSP software development VM for some old tools that only run on WinXP. I set this up years ago using VMware Workstation 6.5.5. I need to transfer this VM to another company and run it using VM Player or Workstation. The XP VM is a .vmdk and won't run under latest

     

    How can I convert this Workstation 6.5.5 .vmdk to run with current versions of player or workstation?

     

    If I roll back to 6.5.5 and run the XP VM, can I run the vCenter Converter within the VM to get to the new format?


    0 0

    hi,

    everything went fine since using Win7 als VM on Linux since 1 Month. Suddenly Win7 won't start any longer: "machine in use".

    Deleting all *.lck (even directory) had no effect. I moved "caches", but no success. First question when starting vmplayer

    is always: "Overtake ownership?". directly after click to "take ownership":

     

     

    Error opening virtual machine /sda4/vmachines/win7-prof64/win7-prof64.vmx:

    Taking ownership of this virtual machine failed.

    The virtual machine is in use by an application on your host computer.

    Configuration file: /sda4/vmachines/win7-prof64/win7-prof64.vmx.


    Persmissions are correct, it even worked for one month:

     

    drwxrwxr-x 7 pc16 users       4096  1. Sep 2016  .

    drwxr-xr-x 5 root root        4096  3. Aug 15:18 ..

    -rw-r--r-- 1 pc16 users          0 26. Jul 11:11 win7-prof64.vmsd

    -rw-r--r-- 1 pc16 users        369 26. Jul 12:12 win7-prof64.vmxf

    drwxr-xr-x 3 pc16 users       4096 26. Jul 12:55 XXX-caches

    -rw------- 1 pc16 users    7700689 29. Jul 23:11 vmmcores-1.gz

    -rw------- 1 pc16 users     524288  3. Aug 16:33 win7-prof64-s015.vmdk

    -rw------- 1 pc16 users     524288  3. Aug 16:39 win7-prof64-s019.vmdk

    -rw------- 1 pc16 users     524288  3. Aug 16:39 win7-prof64-s024.vmdk

    -rw------- 1 pc16 users     524288  3. Aug 16:39 win7-prof64-s023.vmdk

    -rw------- 1 pc16 users     524288  3. Aug 16:39 win7-prof64-s022.vmdk

    -rw------- 1 pc16 users     524288  3. Aug 16:39 win7-prof64-s021.vmdk

    -rw------- 1 pc16 users     524288  3. Aug 16:39 win7-prof64-s020.vmdk

    -rw------- 1 pc16 users     524288  3. Aug 16:39 win7-prof64-s030.vmdk

    -rw------- 1 pc16 users     524288  3. Aug 16:39 win7-prof64-s029.vmdk

    -rw------- 1 pc16 users     524288  3. Aug 16:39 win7-prof64-s028.vmdk

    -rw------- 1 pc16 users     524288  3. Aug 16:39 win7-prof64-s027.vmdk

    -rw------- 1 pc16 users     524288  3. Aug 16:39 win7-prof64-s026.vmdk

    -rw------- 1 pc16 users     524288  3. Aug 16:39 win7-prof64-s025.vmdk

    -rw------- 1 pc16 users     262144  3. Aug 17:03 win7-prof64-s031.vmdk

    -rw------- 1 pc16 users   86179840  8. Aug 12:19 win7-prof64-s013.vmdk

    -rw------- 1 pc16 users 4252499968  8. Aug 12:25 win7-prof64-s008.vmdk

    -rw------- 1 pc16 users       1782 24. Aug 10:56 win7-prof64.vmdk

    -rw------- 1 pc16 users 2422734848 24. Aug 12:49 win7-prof64-s007.vmdk

    -rw------- 1 pc16 users 4252499968 24. Aug 12:49 win7-prof64-s002.vmdk

    -rw------- 1 pc16 users 4235329536 24. Aug 12:49 win7-prof64-s001.vmdk

    -rw------- 1 pc16 users       8684 24. Aug 12:49 win7-prof64.nvram

    -rw-r--r-- 1 pc16 users     301642 24. Aug 12:49 vmware-2.log

    -rw------- 1 pc16 users 1302855680  1. Sep 10:21 win7-prof64-s018.vmdk

    -rw------- 1 pc16 users 3120300032  1. Sep 10:21 win7-prof64-s017.vmdk

    -rw------- 1 pc16 users 2498953216  1. Sep 10:21 win7-prof64-s016.vmdk

    -rw------- 1 pc16 users 3339714560  1. Sep 10:21 win7-prof64-s014.vmdk

    -rw------- 1 pc16 users  290258944  1. Sep 10:21 win7-prof64-s012.vmdk

    -rw------- 1 pc16 users  375717888  1. Sep 10:21 win7-prof64-s011.vmdk

    -rw------- 1 pc16 users  250609664  1. Sep 10:21 win7-prof64-s010.vmdk

    -rw------- 1 pc16 users 2213478400  1. Sep 10:21 win7-prof64-s009.vmdk

    -rw------- 1 pc16 users 2790129664  1. Sep 10:21 win7-prof64-s006.vmdk

    -rw------- 1 pc16 users 3798990848  1. Sep 10:21 win7-prof64-s005.vmdk

    -rw------- 1 pc16 users 4252237824  1. Sep 10:21 win7-prof64-s004.vmdk

    -rw------- 1 pc16 users 4222287872  1. Sep 10:21 win7-prof64-s003.vmdk

    drwxr-xr-x 2 pc16 users       4096  1. Sep 11:05 caches

    -rw-r--r-- 1 pc16 users      72590  1. Sep 11:09 vmware-1.log

    -rw-r--r-- 1 pc16 users      57740  1. Sep 11:09 vmware-0.log

    -rwxr-xr-x 1 pc16 users       2776  1. Sep 11:14 win7-prof64.vmx

    -rw-r--r-- 1 pc16 users      68964  1. Sep 11:14 vmware.log



    A xubuntu 14.04 runs fine as VM on the same host. Only win7-prof won't start. A new vmem was

    created once this morning. But then never again. I shut down xubuntu14.04, I stopped vmware rc-file,

    I restartet vmware, I tried to start win7 only. No success, same error. I restarted xubuntu.


    Very often no question "Take ownership .." appears. vmplayer just only starts a process that "hangs".

    At command line start: no errors are reported.


    Disk space is at 40% , some hundred gigabyte free.



    Starting a copy of the machine from 3. August I get the same problem. So its not a problem

    of the Win7 installation. But no software was installed/ changed. It's a vmplayer-problem. A gtkmm-problem?



    # cat /tmp//vmware-pc16/vmware-vmplayer-9203.log

    2016-09-01T17:06:15.118+02:00| vmplayer| I120: Log for VMware Player pid=9203 version=7.1.0 build=build-2496824 option=Release

    2016-09-01T17:06:15.118+02:00| vmplayer| I120: The process is 64-bit.

    2016-09-01T17:06:15.118+02:00| vmplayer| I120: Host codepage=ISO-8859-1 encoding=ISO-8859-1

    2016-09-01T17:06:15.118+02:00| vmplayer| I120: Host is Linux 2.6.31.5-0.1-desktop openSUSE 11.2 (x86_64)

    2016-09-01T17:06:15.110+02:00| vthread-4| I120: UTIL: Change file descriptor limit from soft 1024,hard 8192 to soft 4096,hard 8192.

    2016-09-01T17:06:15.110+02:00| vmplayer| I120: VTHREAD initialize main thread 4 "vmplayer" pid 9203

    2016-09-01T17:06:15.110+02:00| vmplayer| I120: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": Datei oder Verzeichnis nicht gefunden.

    2016-09-01T17:06:15.110+02:00| vmplayer| I120: Msg_Reset:

    2016-09-01T17:06:15.110+02:00| vmplayer| I120: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": Datei oder Verzeichnis nicht gefunden.

    2016-09-01T17:06:15.110+02:00| vmplayer| I120: ----------------------------------------

    2016-09-01T17:06:15.110+02:00| vmplayer| I120: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.

    2016-09-01T17:06:15.111+02:00| vmplayer| I120: DictionaryLoad: Cannot open file "/home/pc16/.vmware/config": Datei oder Verzeichnis nicht gefunden.

    2016-09-01T17:06:15.111+02:00| vmplayer| I120: Msg_Reset:

    2016-09-01T17:06:15.111+02:00| vmplayer| I120: [msg.dictionary.load.openFailed] Cannot open file "/home/pc16/.vmware/config": Datei oder Verzeichnis nicht gefunden.

    2016-09-01T17:06:15.111+02:00| vmplayer| I120: ----------------------------------------

    2016-09-01T17:06:15.111+02:00| vmplayer| I120: PREF Optional preferences file not found at /home/pc16/.vmware/config. Using default values.

    2016-09-01T17:06:15.125+02:00| vmplayer| I120: LOCALE de_DE.ISO-8859-1 -> NULL

    2016-09-01T17:06:15.126+02:00| vmplayer| I120: OBJLIB-LIB: Objlib initialized.

    2016-09-01T17:06:15.145+02:00| vmplayer| I120: HALLoadLibrary: Opened libhal.so.1.

    2016-09-01T17:06:15.145+02:00| vmplayer| I120: HALLoadLibrary: Opened libdbus-1.so.3.

    2016-09-01T17:06:15.145+02:00| vmplayer| I120: HALLoadLibrary: Opened libdbus-glib-1.so.2.

    2016-09-01T17:06:15.150+02:00| vmplayer| I120: Unable to classify bus of cdrom: /dev/sr0 (/org/freedesktop/Hal/devices/storage_model_DVDRAM_GH24NSD1).  Using SCSI.

    2016-09-01T17:06:15.151+02:00| vmplayer| I120: Unable to classify bus of disk: /dev/sdb (/org/freedesktop/Hal/devices/storage_serial_ST1000DM003_1ER162_Z4Y5MQ0X).  Using SCSI.

    2016-09-01T17:06:15.152+02:00| vmplayer| I120: Unable to classify bus of disk: /dev/sda (/org/freedesktop/Hal/devices/storage_serial_WDC_WD1003FBYZ_010FB0_WD_WCAW32NXA3RS).  Using SCSI.

    2016-09-01T17:06:15.170+02:00| vmplayer| I120: HAL05DeviceAdded: Error getting 'pci.vendor' property: No property pci.vendor on device with id /org/freedesktop/Hal/devices/pci_1b21_1142.

    2016-09-01T17:06:15.170+02:00| vmplayer| I120: HAL05GetPciDeviceInfo: DBus Error getting device information: No property pci.vendor on device with id /org/freedesktop/Hal/devices/pci_1b21_1142

    2016-09-01T17:06:15.182+02:00| vmplayer| I120: HAL05Init: HAL05 Initialized successfully.

    2016-09-01T17:06:15.205+02:00| vmplayer| I120: UUID: Unable to open /sys/firmware/efi/systab: Datei oder Verzeichnis nicht gefunden

    2016-09-01T17:06:15.205+02:00| vmplayer| I120: UUID: Unable to open /dev/mem: Keine Berechtigung

    2016-09-01T17:06:15.238+02:00| vmplayer| I120: UUID: Invalid gethostid routine. Value = 0.

    2016-09-01T17:06:15.240+02:00| vmplayer| I120: vmxFilePath="/usr/lib/vmware/bin/vmware-vmx"

    2016-09-01T17:06:15.240+02:00| vmplayer| I120: vmxFilePathDebug="/usr/lib/vmware/bin/vmware-vmx-debug"

    2016-09-01T17:06:15.240+02:00| vmplayer| I120: vmxFilePathStats="/usr/lib/vmware/bin/vmware-vmx-stats"

    2016-09-01T17:06:15.245+02:00| vmplayer| I120: SMBIOS: can't open /dev/mem: Insufficient permission to access the file

    2016-09-01T17:06:15.245+02:00| vmplayer| I120: VmhsHostInfoPopulateSystem:  Could not get information from smbios to populate VMDB.

    2016-09-01T17:06:15.309+02:00| vmplayer| I120: ReadProxyFile: Failed to read file: /etc/vmware/hostd/proxy.xml

    2016-09-01T17:06:15.309+02:00| vmplayer| I120: SOCKET creating new socket, connecting to /var/run/vmware/usbarbitrator-socket

    2016-09-01T17:06:15.309+02:00| vmplayer| I120: REM-USB: Protocol version min:15 current:16. hostId:52 8a fa c9 6a 8a 03 31-e0 9d 11 9a ad 56 33 f9

    2016-09-01T17:06:15.310+02:00| vmplayer| I120: REM-USB: Initializing 'Generic' backend

    2016-09-01T17:06:15.310+02:00| vmplayer| I120: DictionaryLoad: Cannot open file "/home/pc16/.vmware/preferences-private": Datei oder Verzeichnis nicht gefunden.

    2016-09-01T17:06:15.311+02:00| vmplayer| I120: CDS: Initializing a CDS updater client 1.0 for product player-linux, version 7.1.0 (workspace /tmp/vmware-pc16)

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: LOCALE de_DE.ISO-8859-1 -> NULL

    2016-09-01T17:06:15.360+02:00| vmplayer| W110: Using log file /tmp/vmware-pc16/vmware-vmplayer-9203.log

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: Foundry Init: setting up global state (1 poll threads, 0 worker threads).

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: Vix_InitializeGlobalState: vixLogLevel = 0

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: Vix_InitializeGlobalState: vixApiTraceLevel = 0

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: Vix_InitializeGlobalState: vixDebugPanicOnVixAssert = 0

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: Vix_InitializeGlobalState: vixLogRefcountOnFinalRelease = 0

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: Vix_InitializeGlobalState: asyncOpWarningThreshold = 1000000

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: Vix_InitializeGlobalState: enableSyncOpSelection = FALSE

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: Vix_InitializeGlobalState: enableExternalThreadInterface = TRUE

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: Vix_InitializeGlobalState: enableVigor = FALSE

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: LOCALE de_DE.ISO-8859-1 -> NULL

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: VixHost_ConnectEx: version -1, hostType 3, hostName (null), hostPort 0, options 8707

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: Printing loaded objects

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F6E1DC000-0x7F9F6E287924): /usr/lib/vmware/bin/vmplayer

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7FFFD3FFF000-0x7FFFD3FFF890): <no name>

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F6DDA7000-0x7F9F6DDBAF94): /lib64/libz.so.1

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F6DBA3000-0x7F9F6DBA4E78): /lib64/libdl.so.2

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F6D987000-0x7F9F6D99D000): /lib64/libpthread.so.0

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F6D770000-0x7F9F6D785474): /lib64/libgcc_s.so.1

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F6D415000-0x7F9F6D565C00): /lib64/libc.so.6

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F6DFBD000-0x7F9F6DFDA1F0): /lib64/ld-linux-x86-64.so.2

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F6C404000-0x7F9F6C4F2F0C): /usr/lib/vmware/lib/libglib-2.0.so.0/libglib-2.0.so.0

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F6C729000-0x7F9F6C8C1314): /usr/lib/vmware/lib/libcrypto.so.1.0.1/libcrypto.so.1.0.1

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F6C19D000-0x7F9F6C1F9DAC): /usr/lib/vmware/lib/libssl.so.1.0.1/libssl.so.1.0.1

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F6BE2E000-0x7F9F6BF92224): /usr/lib/vmware/lib/libxml2.so.2/libxml2.so.2

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F6BBD9000-0x7F9F6BC2C780): /lib64/libm.so.6

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F6C625000-0x7F9F6C6289DC): /usr/lib/vmware/lib/libgthread-2.0.so.0/libgthread-2.0.so.0

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F6B9D0000-0x7F9F6B9D70BC): /lib64/librt.so.1

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F6B88D000-0x7F9F6B8CD81C): /usr/lib/vmware/lib/libgobject-2.0.so.0/libgobject-2.0.so.0

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F6B66C000-0x7F9F6B6897BC): /usr/lib/vmware/lib/libatk-1.0.so.0/libatk-1.0.so.0

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F6B456000-0x7F9F6B46AECC): /usr/lib/vmware/lib/libgcc_s.so.1/libgcc_s.so.1

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F6B14B000-0x7F9F6B2371DC): /usr/lib/vmware/lib/libstdc++.so.6/libstdc++.so.6

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F6AF45000-0x7F9F6AF49CDF): /usr/lib/vmware/lib/libsigc-2.0.so.0/libsigc-2.0.so.0

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F6AE42000-0x7F9F6AE44594): /usr/lib/vmware/lib/libgmodule-2.0.so.0/libgmodule-2.0.so.0

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F6ACE5000-0x7F9F6AD3DF62): /usr/lib/vmware/lib/libglibmm-2.4.so.1/libglibmm-2.4.so.1

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F6AB99000-0x7F9F6ABDE2D0): /usr/lib/vmware/lib/libatkmm-1.6.so.1/libatkmm-1.6.so.1

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F6A956000-0x7F9F6AA93DD4): /usr/lib/vmware/lib/libpixman-1.so.0/libpixman-1.so.0

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F6A842000-0x7F9F6A855774): /usr/lib/vmware/lib/libz.so.1/libz.so.1

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F6A6BB000-0x7F9F6A73C9C4): /usr/lib/vmware/lib/libfreetype.so.6/libfreetype.so.6

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F6A599000-0x7F9F6A5B8E94): /usr/lib/vmware/lib/libexpat.so.0/libexpat.so.0

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F6A364000-0x7F9F6A396BD4): /usr/lib64/libfontconfig.so.1

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F6A13B000-0x7F9F6A160734): /lib64/libexpat.so.1

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F69F18000-0x7F9F69F3A5FC): /usr/lib/vmware/lib/libpng12.so.0/libpng12.so.0

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F69E0F000-0x7F9F69E17554): /usr/lib/vmware/lib/libXrender.so.1/libXrender.so.1

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F69AD3000-0x7F9F69C08A84): /usr/lib64/libX11.so.6

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F698B6000-0x7F9F698D0E7C): /usr/lib64/libxcb.so.1

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F696B2000-0x7F9F696B3E2C): /usr/lib64/libXau.so.6

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F6950E000-0x7F9F695AC86C): /usr/lib/vmware/lib/libcairo.so.2/libcairo.so.2

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F692C0000-0x7F9F6930A679): /usr/lib/vmware/lib/libcairomm-1.0.so.1/libcairomm-1.0.so.1

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F6911A000-0x7F9F691BBD2C): /usr/lib/vmware/lib/libgio-2.0.so.0/libgio-2.0.so.0

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F68F04000-0x7F9F68F162F8): /lib64/libresolv.so.2

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F68CE3000-0x7F9F68D02FEC): /usr/lib/vmware/lib/libgck.so.0/libgck.so.0

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F68ADF000-0x7F9F68AE1AEC): /lib64/libgpg-error.so.0

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F68867000-0x7F9F688DB144): /lib64/libgcrypt.so.11

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F6871F000-0x7F9F68763A2C): /usr/lib/vmware/lib/libpango-1.0.so.0/libpango-1.0.so.0

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F685F0000-0x7F9F6861DE94): /usr/lib/vmware/lib/libpangoft2-1.0.so.0/libpangoft2-1.0.so.0

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F684E4000-0x7F9F684EEA64): /usr/lib/vmware/lib/libpangocairo-1.0.so.0/libpangocairo-1.0.so.0

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F683E2000-0x7F9F683E3854): /usr/lib/vmware/lib/libXinerama.so.1/libXinerama.so.1

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F681D0000-0x7F9F681E0B1C): /usr/lib64/libXext.so.6

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F680CB000-0x7F9F680CF74C): /usr/lib/vmware/lib/libXfixes.so.3/libXfixes.so.3

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F67FC1000-0x7F9F67FC9AD4): /usr/lib/vmware/lib/libXcursor.so.1/libXcursor.so.1

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F67EBF000-0x7F9F67EC0C3C): /usr/lib/vmware/lib/libXcomposite.so.1/libXcomposite.so.1

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F67DBD000-0x7F9F67DBE77C): /usr/lib/vmware/lib/libXdamage.so.1/libXdamage.so.1

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F67CA3000-0x7F9F67CBB734): /usr/lib/vmware/lib/libgdk_pixbuf-2.0.so.0/libgdk_pixbuf-2.0.so.0

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F67AFD000-0x7F9F67B9DA24): /usr/lib/vmware/lib/libgdk-x11-2.0.so.0/libgdk-x11-2.0.so.0

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F67601000-0x7F9F679EF674): /usr/lib/vmware/lib/libgtk-x11-2.0.so.0/libgtk-x11-2.0.so.0

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F673A8000-0x7F9F673F7484): /usr/lib/vmware/lib/libgcr.so.0/libgcr.so.0

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F671F6000-0x7F9F67299C80): /usr/lib/vmware/lib/libgiomm-2.4.so.1/libgiomm-2.4.so.1

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F670C9000-0x7F9F670F37BA): /usr/lib/vmware/lib/libpangomm-1.4.so.1/libpangomm-1.4.so.1

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F66F7D000-0x7F9F66FC3D32): /usr/lib/vmware/lib/libgdkmm-2.4.so.1/libgdkmm-2.4.so.1

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F66E77000-0x7F9F66E7C1D9): /usr/lib/vmware/lib/libglibmm_generate_extra_defs-2.4.so.1/libglibmm_generate_extra_defs-2.4.so.1

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F66900000-0x7F9F66CDBB74): /usr/lib/vmware/lib/libgtkmm-2.4.so.1/libgtkmm-2.4.so.1

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F667F4000-0x7F9F667FEFD4): /usr/lib/vmware/lib/libpangox-1.0.so.0/libpangox-1.0.so.0

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F666E1000-0x7F9F666F349C): /usr/lib/vmware/lib/libXft.so.2/libXft.so.2

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F665D9000-0x7F9F665DFB3C): /usr/lib/vmware/lib/libpangoxft-1.0.so.0/libpangoxft-1.0.so.0

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F663A2000-0x7F9F663D6CA4): /usr/lib64/librsvg-2.so.2

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F66162000-0x7F9F6619BE5C): /usr/lib64/libgsf-1.so.114

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F65F26000-0x7F9F65F5DDBC): /usr/lib64/libcroco-0.6.so.3

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F65D17000-0x7F9F65D2400C): /lib64/libbz2.so.1

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F65B0E000-0x7F9F65B1552C): /usr/lib64/libXrandr.so.2

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F65992000-0x7F9F659FC377): /usr/lib/vmware/lib/libview.so.3/libview.so.3

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F6578C000-0x7F9F65790684): /usr/lib64/libXdmcp.so.6

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F64DC9000-0x7F9F654F7A5C): /usr/lib/vmware/lib/libvmwarebase.so.0/libvmwarebase.so.0

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F64B66000-0x7F9F64BC5AF4): /usr/lib/vmware/lib/libcurl.so.4/libcurl.so.4

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F6430B000-0x7F9F64936ED4): /usr/lib/vmware/lib/libgvmomi.so.0/libgvmomi.so.0

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F640DB000-0x7F9F64107800): /usr/lib/vmware/lib/libcds.so/libcds.so

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F6260A000-0x7F9F63CAA00F): /usr/lib/vmware/lib/libvmwareui.so.0/libvmwareui.so.0

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F623FF000-0x7F9F62407DEC): /usr/lib64/libXi.so.6

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F61EAB000-0x7F9F61FD683B): /usr/lib/vmware/lib/libvmplayer.so/libvmplayer.so

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F6137D000-0x7F9F6137E268): /usr/lib64/gconv/ISO8859-1.so

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F6DFEE000-0x7F9F6E01646C): /usr/lib/vmware/libconf/lib/gtk-2.0/2.10.0/engines/libclearlooks.so

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F600F7000-0x7F9F600FB23C): /usr/lib/vmware/libconf/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-png.so

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F5AE20000-0x7F9F5AE21314): /usr/lib/vmware/libconf/lib/gtk-2.0/2.10.0/loaders/svg_loader.so

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F5AC0F000-0x7F9F5AC1E80C): /usr/lib64/libhal.so.1

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F5A9CF000-0x7F9F5AA0CDAC): /lib64/libdbus-1.so.3

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: [0x7F9F5A7AD000-0x7F9F5A7CCF7C): /usr/lib64/libdbus-glib-1.so.2

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: End printing loaded objects

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: NewComponentMgr: 7.1.0(2496824)

    2016-09-01T17:06:15.360+02:00| vmplayer| I120: CDS: Initializing a CDS updater client 1.0 for product unknown, version 7.1.0.2496824 (workspace /tmp/vmware-pc16)

    2016-09-01T17:06:15.410+02:00| vmplayer| I120: LOCALE de_DE.ISO-8859-1 -> NULL

    2016-09-01T17:06:15.460+02:00| vmplayer| I120: CDS: Found cached version 7.1.0 build 2496824 for vmware-player

    2016-09-01T17:06:15.460+02:00| vmplayer| I120: RefreshComponentListWithDefaults: CDS_UNKNOWN_PRODUCT_ERROR for product player-windows

    2016-09-01T17:06:15.508+02:00| vmplayer| I120: CDS: No cached version for vmware-tools-darwin

    2016-09-01T17:06:15.556+02:00| vmplayer| I120: CDS: No cached version for vmware-tools-freebsd

    2016-09-01T17:06:15.605+02:00| vmplayer| I120: CDS: No cached version for vmware-tools-linux

    2016-09-01T17:06:15.655+02:00| vmplayer| I120: CDS: No cached version for vmware-tools-netware

    2016-09-01T17:06:15.707+02:00| vmplayer| I120: CDS: No cached version for vmware-tools-solaris

    2016-09-01T17:06:15.757+02:00| vmplayer| I120: CDS: No cached version for vmware-tools-winPre2k

    2016-09-01T17:06:15.807+02:00| vmplayer| I120: CDS: No cached version for vmware-tools-windows

    2016-09-01T17:06:15.855+02:00| vmplayer| I120: CDS: No cached version for vmware-workstation

    2016-09-01T17:06:15.855+02:00| vmplayer| I120: RefreshComponentListWithDefaults: CDS_UNKNOWN_PRODUCT_ERROR for product ws-windows

    2016-09-01T17:06:15.856+02:00| vmplayer| I120: NewComponentMgr: 7.1.0(2496824)

    2016-09-01T17:06:15.856+02:00| vmplayer| I120: CDS: Initializing a CDS updater client 1.0 for product player-linux, version 7.1.0.2496824 (workspace /tmp/vmware-pc16)

    2016-09-01T17:06:15.906+02:00| vmplayer| I120: LOCALE de_DE.ISO-8859-1 -> NULL

    2016-09-01T17:06:15.957+02:00| vmplayer| I120: CDS: Found cached version 7.1.0 build 2496824 for vmware-player

    2016-09-01T17:06:15.957+02:00| vmplayer| I120: RefreshComponentListWithDefaults: CDS_UNKNOWN_PRODUCT_ERROR for product player-windows

    2016-09-01T17:06:16.009+02:00| vmplayer| I120: CDS: No cached version for vmware-tools-darwin

    2016-09-01T17:06:16.058+02:00| vmplayer| I120: CDS: No cached version for vmware-tools-freebsd

    2016-09-01T17:06:16.109+02:00| vmplayer| I120: CDS: No cached version for vmware-tools-linux

    2016-09-01T17:06:16.161+02:00| vmplayer| I120: CDS: No cached version for vmware-tools-netware

    2016-09-01T17:06:16.209+02:00| vmplayer| I120: CDS: No cached version for vmware-tools-solaris

    2016-09-01T17:06:16.258+02:00| vmplayer| I120: CDS: No cached version for vmware-tools-winPre2k

    2016-09-01T17:06:16.307+02:00| vmplayer| I120: CDS: No cached version for vmware-tools-windows

    2016-09-01T17:06:16.361+02:00| vmplayer| I120: CDS: No cached version for vmware-workstation

    2016-09-01T17:06:16.361+02:00| vmplayer| I120: RefreshComponentListWithDefaults: CDS_UNKNOWN_PRODUCT_ERROR for product ws-windows

    2016-09-01T17:06:16.394+02:00| vmplayer| I120: OnHostTopologyChanged, found host monitor 0: 1280x1024 @ 0,0

    2016-09-01T17:06:16.394+02:00| vmplayer| I120: OnHostTopologyChanged, I'm now on monitor 0: 1280x1024 @ 0,0

    2016-09-01T17:06:16.394+02:00| vmplayer| I120: OnWindowManagerChanged: found Window Manager: KWin, with fullscreen capability: 2

    2016-09-01T17:06:16.401+02:00| vmplayer| W110: Gtk: paschal-ovum: missing action paschal-ovum

    2016-09-01T17:06:18.022+02:00| vmplayer| I120: VMMgr::OpenVM (cfgPath=/sdb2/vmachines/rsync_delete/win7-prof64/win7-prof64.vmx)

    2016-09-01T17:06:18.025+02:00| vthread-5| I120: VTHREAD initialize thread 5 "vthread-5" pid 9867

    2016-09-01T17:06:18.028+02:00| vthread-5| I120: /sdb2/vmachines/rsync_delete/win7-prof64/win7-prof64.vmx: Reloading config state.

    2016-09-01T17:06:18.032+02:00| vthread-5| I120: VMHS: Transitioned vmx/execState/val to poweredOff

    2016-09-01T17:07:18.107+02:00| vthread-5| I120: /sdb2/vmachines/rsync_delete/win7-prof64/win7-prof64.vmx: Failed to connect to path testAutomation-fd.

    2016-09-01T17:07:18.107+02:00| vthread-5| I120: VTHREAD initialize thread 5 "vthread-5" pid 9868

    2016-09-01T17:08:18.178+02:00| vthread-5| I120: /sdb2/vmachines/rsync_delete/win7-prof64/win7-prof64.vmx: Failed to connect to path testAutomation-fd.

    2016-09-01T17:08:18.178+02:00| vthread-5| I120: VTHREAD initialize thread 5 "vthread-5" pid 9885

    2016-09-01T17:08:18.179+02:00| vigorCnx| I120: VTHREAD start thread 5 "vigorCnx" pid 9894

    2016-09-01T17:08:18.192+02:00| vmplayer| I120: SnapshotTree: Emitting refresh (/sdb2/vmachines/rsync_delete/win7-prof64/win7-prof64.vmx)

    2016-09-01T17:08:18.192+02:00| vmplayer| I120: ReadProxyFile: Failed to read file: /etc/vmware/hostd/proxy.xml

    2016-09-01T17:08:18.192+02:00| vmplayer| I120: Setting power state poweredOff

    2016-09-01T17:08:18.199+02:00| vmplayer| I120: VMMgr: Finished opening VM at /vm/#090ce29dafcd2b31/ from /sdb2/vmachines/rsync_delete/win7-prof64/win7-prof64.vmx

    2016-09-01T17:08:18.697+02:00| vmplayer| I120: VMHSGetDataFileKey: Could not get the dataFileKey from VMDB




    vmware.log (the end:)

    [...]

    2016-09-01T11:14:41.044+02:00| vmx| I120: Successfully loaded worldswitch fault handlers from .switchNMI. Size = 128.

    2016-09-01T11:14:41.044+02:00| vmx| I120: Successfully loaded worldswitch fault handlers from .switchNMI. Size = 128.

    2016-09-01T11:14:41.044+02:00| vmx| I120: Successfully loaded worldswitch fault handlers from .switchNMI. Size = 128.

    2016-09-01T11:14:41.044+02:00| vmx| I120: vmm64-modules: [vmm.vmm64, mmu-hwmmu.vmm64, vprobe-none.vmm64, hv-vt.vmm64, gphys-ept.vmm64, vmsafe-none.vmm64, callstack-none.vmm64, vmce-none.vmm64, vvtd-none.vmm64, ahci-ahci.vmm64, {SharedAreaReservations} .shared_per_vm_vmx:0x2ac0, {SharedInterVcpuVmxSection}, {SharedInterVcpuSection}, <MonSrcFile>, e1000Shared=0xfffffffffc0d4c00, ahciShared=0xfffffffffc0d4000, ahciRegs=0xfffffffffc0d3000, hvLoadedAsAddr=0x1, useNPTAsAddr=0x1, numVCPUsAsAddr=0x4, busmemFrameSizeLog2AsAddr=0x2, busmemFrameSizeAsAddr=0x4]

    2016-09-01T11:14:41.044+02:00| vmx| I120: vmm64-vcpus: 4

    2016-09-01T11:14:41.046+02:00| vmx| I120: KHZEstimate 3398368

    2016-09-01T11:14:41.046+02:00| vmx| I120: MHZEstimate 3398

    2016-09-01T11:14:41.046+02:00| vmx| I120: NumVCPUs 4

    2016-09-01T11:14:41.046+02:00| vmx| I120: Guest OS (20497) not supported for replay debugging.

    2016-09-01T11:14:41.047+02:00| vmx| I120: UUID: Unable to open /sys/firmware/efi/systab: No such file or directory

    2016-09-01T11:14:41.047+02:00| vmx| I120: UUID: Found _DMI_ signature.

    2016-09-01T11:14:41.047+02:00| vmx| I120: UUID: SMBIOS UUID is reported as 'fe e8 73 98 46 25 c3 99-e2 04 08 62 66 46 67 3e'.

    2016-09-01T11:14:41.047+02:00| vmx| I120: UUID: location-UUID is 56 4d 93 52 19 f7 8f 23-40 eb 24 cc 2e de bb a2

    2016-09-01T11:14:41.048+02:00| vmx| I120: AIOGNRC: numThreads=17 ide=0, scsi=1, passthru=0

    2016-09-01T11:14:41.048+02:00| vmx| I120: WORKER: Creating new group with numThreads=17 (17)

    2016-09-01T11:14:41.048+02:00| WT| I120: VTHREAD start thread 9 "WT" pid 23837

    2016-09-01T11:14:41.048+02:00| vmx| A115: ConfigDB: Setting replay.supported = "FALSE"

    2016-09-01T11:14:41.124+02:00| vmx| I120: StateLogger::Replay State = 0

    2016-09-01T11:14:41.124+02:00| vmx| I120: StateLogger::minDEThreshold: 115

    2016-09-01T11:14:41.124+02:00| vmx| A115: ConfigDB: Setting replay.filename = ""

    2016-09-01T11:14:41.171+02:00| vmx| I120: WORKER: Creating new group with numThreads=1 (18)

    2016-09-01T11:14:41.171+02:00| vmx| I120: MainMem: CPT Host WZ=0 PF=3072 D=0

    2016-09-01T11:14:41.171+02:00| vmx| I120: MainMem: CPT PLS=1 PLR=1 BS=1 BlkP=32 Mult=4 W=50

    2016-09-01T11:14:41.171+02:00| vmem| I120: VTHREAD start thread 10 "vmem" pid 23838

    2016-09-01T11:14:41.171+02:00| vmem| I120: UUID: location-UUID is 56 4d 93 52 19 f7 8f 23-40 eb 24 cc 2e de bb a2

    2016-09-01T11:14:41.171+02:00| vmx| I120: MainMem: Opened paging file, '/tmp/vmware-pc16/564d9352-19f7-8f23-40eb-24cc2edebba2/vmem' (swap).

    2016-09-01T11:14:41.171+02:00| vmx| I120: MStat: Creating Stat vm.uptime

    2016-09-01T11:14:41.171+02:00| vmx| I120: MStat: Creating Stat vm.suspendTime

    2016-09-01T11:14:41.171+02:00| vmx| I120: MStat: Creating Stat vm.powerOnTimeStamp

    2016-09-01T11:14:41.171+02:00| vmx| I120: VMXAIOMGR: Using: simple=Generic unbuf=Generic

    2016-09-01T11:14:41.172+02:00| vmx| I120: WORKER: Creating new group with numThreads=1 (19)

    2016-09-01T11:14:41.173+02:00| vmx| I120: WORKER: Creating new group with numThreads=16 (35)

    2016-09-01T11:14:41.173+02:00| vmx| I120: MigrateResetStaleVMDBHostLog: Hostlog ./win7-prof64-b295f18f.hlog doesn't exist.

    2016-09-01T11:14:41.173+02:00| vmx| I120: TimeTracker host to guest rate conversion 623768464 @ 3398368000Hz -> 0 @ 3398368000Hz

    2016-09-01T11:14:41.173+02:00| vmx| I120: TimeTracker host to guest rate conversion ((x * 2147483648) >> 31) + -623768464

    2016-09-01T11:14:41.173+02:00| vmx| I120: Disabling TSC scaling since host does not support it.

    2016-09-01T11:14:41.173+02:00| vmx| I120: TSC offsetting enabled.

    2016-09-01T11:14:41.173+02:00| vmx| I120: timeTracker.globalProgressMaxAllowanceMS: 2000

    2016-09-01T11:14:41.173+02:00| vmx| I120: timeTracker.globalProgressToAllowanceNS: 1000

    2016-09-01T11:14:41.173+02:00| vmx| A115: ConfigDB: Setting scsi0:0.redo = ""

    2016-09-01T11:14:41.173+02:00| vmx| I120: DISK: OPEN scsi0:0 '/sda4/vmachines/win7-prof64/win7-prof64.vmdk' persistent R[]

    2016-09-01T11:14:41.174+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [0]: "win7-prof64-s001.vmdk" (0x1a)

    2016-09-01T11:14:41.174+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [1]: "win7-prof64-s002.vmdk" (0x1a)

    2016-09-01T11:14:41.174+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [2]: "win7-prof64-s003.vmdk" (0x1a)

    2016-09-01T11:14:41.174+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [3]: "win7-prof64-s004.vmdk" (0x1a)

    2016-09-01T11:14:41.174+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [4]: "win7-prof64-s005.vmdk" (0x1a)

    2016-09-01T11:14:41.174+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [5]: "win7-prof64-s006.vmdk" (0x1a)

    2016-09-01T11:14:41.174+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [6]: "win7-prof64-s007.vmdk" (0x1a)

    2016-09-01T11:14:41.175+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [7]: "win7-prof64-s008.vmdk" (0x1a)

    2016-09-01T11:14:41.175+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [8]: "win7-prof64-s009.vmdk" (0x1a)

    2016-09-01T11:14:41.175+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [9]: "win7-prof64-s010.vmdk" (0x1a)

    2016-09-01T11:14:41.175+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [10]: "win7-prof64-s011.vmdk" (0x1a)

    2016-09-01T11:14:41.175+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [11]: "win7-prof64-s012.vmdk" (0x1a)

    2016-09-01T11:14:41.175+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [12]: "win7-prof64-s013.vmdk" (0x1a)

    2016-09-01T11:14:41.175+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [13]: "win7-prof64-s014.vmdk" (0x1a)

    2016-09-01T11:14:41.175+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [14]: "win7-prof64-s015.vmdk" (0x1a)

    2016-09-01T11:14:41.175+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [15]: "win7-prof64-s016.vmdk" (0x1a)

    2016-09-01T11:14:41.175+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [16]: "win7-prof64-s017.vmdk" (0x1a)

    2016-09-01T11:14:41.175+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [17]: "win7-prof64-s018.vmdk" (0x1a)

    2016-09-01T11:14:41.175+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [18]: "win7-prof64-s019.vmdk" (0x1a)

    2016-09-01T11:14:41.175+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [19]: "win7-prof64-s020.vmdk" (0x1a)

    2016-09-01T11:14:41.175+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [20]: "win7-prof64-s021.vmdk" (0x1a)

    2016-09-01T11:14:41.175+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [21]: "win7-prof64-s022.vmdk" (0x1a)

    2016-09-01T11:14:41.175+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [22]: "win7-prof64-s023.vmdk" (0x1a)

    2016-09-01T11:14:41.176+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [23]: "win7-prof64-s024.vmdk" (0x1a)

    2016-09-01T11:14:41.176+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [24]: "win7-prof64-s025.vmdk" (0x1a)

    2016-09-01T11:14:41.176+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [25]: "win7-prof64-s026.vmdk" (0x1a)

    2016-09-01T11:14:41.176+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [26]: "win7-prof64-s027.vmdk" (0x1a)

    2016-09-01T11:14:41.176+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [27]: "win7-prof64-s028.vmdk" (0x1a)

    2016-09-01T11:14:41.176+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [28]: "win7-prof64-s029.vmdk" (0x1a)

    2016-09-01T11:14:41.176+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [29]: "win7-prof64-s030.vmdk" (0x1a)

    2016-09-01T11:14:41.176+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [30]: "win7-prof64-s031.vmdk" (0x1a)

    2016-09-01T11:14:41.176+02:00| vmx| I120: DISKLIB-LINK : Opened '/sda4/vmachines/win7-prof64/win7-prof64.vmdk' (0x1a): twoGbMaxExtentSparse, 251658240 sectors / 120 GB.

    2016-09-01T11:14:41.176+02:00| vmx| I120: DISKLIB-LIB : Opened "/sda4/vmachines/win7-prof64/win7-prof64.vmdk" (flags 0x1a, type twoGbMaxExtentSparse).

    2016-09-01T11:14:41.176+02:00| vmx| I120: DiskGetGeometry: Reading of disk partition table

    2016-09-01T11:14:41.176+02:00| vthread-10| I120: VTHREAD start thread 10 "vthread-10" pid 23839

    2016-09-01T11:14:41.176+02:00| vmx| I120: DISK: Disk '/sda4/vmachines/win7-prof64/win7-prof64.vmdk' has UUID '60 00 c2 9e 63 06 32 cd-37 c7 f1 91 77 ce 3b 52'

    2016-09-01T11:14:41.176+02:00| vmx| I120: DISK: OPEN '/sda4/vmachines/win7-prof64/win7-prof64.vmdk' Geo (15665/255/63) BIOS Geo (15665/255/63)

    2016-09-01T11:14:41.224+02:00| vmx| I120: DISK: Opening disks took 50 ms.

    2016-09-01T11:14:41.224+02:00| vmx| I120: SOCKET creating new socket, connecting to /var/run/vmware/usbarbitrator-socket

    2016-09-01T11:14:41.224+02:00| vmx| I120: USB: Initializing 'Virtual Hub' backend

    2016-09-01T11:14:41.224+02:00| vmx| I120: USB: Initializing 'Generic' backend

    2016-09-01T11:14:41.224+02:00| vmx| I120: USB: Initializing 'Virtual HID' backend

    2016-09-01T11:14:41.224+02:00| vmx| I120: USB: Initializing 'Remote Device' backend

    2016-09-01T11:14:41.225+02:00| vmx| I120: RemoteUSBVMX: Retrieved hostId [fe e8 73 98 46 25 c3 99-e2 04 08 62 66 46 67 3e]

    2016-09-01T11:14:41.225+02:00| vmx| I120: RemoteUSBVMX: Protocol version min:15 current:16

    2016-09-01T11:14:41.225+02:00| vmx| I120: RemoteUSBVMX: no delay setting is TRUE.

    2016-09-01T11:14:41.225+02:00| vmx| I120: USB: Initializing 'Virtual Mass Storage' backend

    2016-09-01T11:14:41.225+02:00| vmx| I120: USB: Initializing 'Virtual CCID' backend

    2016-09-01T11:14:41.225+02:00| vmx| I120: USB-CCID: dlopened default libpcsclite.so.1.

    2016-09-01T11:14:41.225+02:00| vmx| I120: USB-CCID: Could not establish context: SCARD_E_NO_SERVICE(0x8010001d).

    2016-09-01T11:14:41.225+02:00| vmx| W110: Could not initialize emulated USB smart card subsystem.

    2016-09-01T11:14:41.225+02:00| vmx| I120: USB: Unable to initialize 'Virtual CCID' backend

    2016-09-01T11:14:41.225+02:00| vmx| I120: USB: Initializing 'Virtual Bluetooth' backend

    2016-09-01T11:14:41.225+02:00| vmx| I120: USB: Initializing 'Virtual Audio' backend

    2016-09-01T11:14:41.225+02:00| vmx| I120: USB: Initializing 'Virtual Video' backend

    2016-09-01T11:14:41.227+02:00| vmx| I120: MKS PowerOn

    2016-09-01T11:14:41.227+02:00| mks| I120: VTHREAD start thread 2 "mks" pid 23840

    2016-09-01T11:14:41.227+02:00| mks| I120: MKS thread is alive

    2016-09-01T11:14:41.227+02:00| mks| I120: MKS-RenderMain: RenderMain: PowerOn allowed 0 1 0 1 0

    2016-09-01T11:14:41.227+02:00| mks| I120: MKS-RenderMain: Collecting RenderOps caps...

    2016-09-01T11:14:41.231+02:00| mks| I120: Printing loaded objects

    2016-09-01T11:14:41.231+02:00| mks| I120: [0x400000-0x113560C): /usr/lib/vmware/bin/vmware-vmx

    2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FFF5D3FF000-0x7FFF5D3FF890): <no name>

    2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7ABD3A000-0x7FF7ABD8D780): /lib64/libm.so.6

    2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7ABB36000-0x7FF7ABB37E78): /lib64/libdl.so.2

    2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7AB91A000-0x7FF7AB930000): /lib64/libpthread.so.0

    2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7AB711000-0x7FF7AB7180BC): /lib64/librt.so.1

    2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7AB3D5000-0x7FF7AB50AA84): /usr/lib64/libX11.so.6

    2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7AB1CE000-0x7FF7AB1D2E34): /usr/lib64/libXtst.so.6

    2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7AAFBC000-0x7FF7AAFCCB1C): /usr/lib64/libXext.so.6

    2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7AADB1000-0x7FF7AADB9E34): /usr/lib64/libXcursor.so.1

    2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7AABAB000-0x7FF7AABAFA0C): /usr/lib64/libXfixes.so.3

    2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7AA9A8000-0x7FF7AA9A9824): /usr/lib64/libXinerama.so.1

    2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7AA79E000-0x7FF7AA7A6BEC): /usr/lib64/libXrender.so.1

    2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7AA593000-0x7FF7AA59BDEC): /usr/lib64/libXi.so.6

    2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7AA37D000-0x7FF7AA390F94): /lib64/libz.so.1

    2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7AA166000-0x7FF7AA17B474): /lib64/libgcc_s.so.1

    2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7A9E0B000-0x7FF7A9F5BC00): /lib64/libc.so.6

    2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7ABF8F000-0x7FF7ABFAC1F0): /lib64/ld-linux-x86-64.so.2

    2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7A9BEE000-0x7FF7A9C08E7C): /usr/lib64/libxcb.so.1

    2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7A99EA000-0x7FF7A99EBE2C): /usr/lib64/libXau.so.6

    2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7A8AFE000-0x7FF7A8C96314): /usr/lib/vmware/lib/libcrypto.so.1.0.1/libcrypto.so.1.0.1

    2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7A8897000-0x7FF7A88F3DAC): /usr/lib/vmware/lib/libssl.so.1.0.1/libssl.so.1.0.1

    2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7A868E000-0x7FF7A86951CC): /usr/lib64/libnuma.so.1

    2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7A7A1A000-0x7FF7A7A1A980): /lib64/libaio.so.1

    2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF6E5FF3000-0x7FF6E60979D5): /usr/lib64/libGL.so.1

    2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF6E4B96000-0x7FF6E5A60B04): /usr/lib64/libGLcore.so.1

    2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF6E4A94000-0x7FF6E4A94DD0): /usr/lib64/tls/libnvidia-tls.so.1

    2016-09-01T11:14:41.231+02:00| mks| I120: End printing loaded objects

    2016-09-01T11:14:41.258+02:00| mks| I120: MKS-X: XI major version 1, minor version 4

    2016-09-01T11:14:41.271+02:00| mks| I120: GLHostX11: DISPLAY: "localhost:10.0" only supports GLX 1.2, GLBE requires GLX 1.3 or higher.

    2016-09-01T11:14:41.301+02:00| mks| I120: GLHostX11: DISPLAY: "localhost:10.0" only supports GLX 1.2, GLBE requires GLX 1.3 or higher.

    2016-09-01T11:14:41.308+02:00| mks| I120: GLHostX11: Created context with GL 2.1, core: 0, robust: 0

     

     

    The error "GLBE requires GLX 1.3 or higher" was no problem so far. Win7 started perfectly.

     

    BTW: Host ist Suse 11.2,  2.6.31.5-0.1-desktop, no other host system possible due to a commercial program.

     

     

    vmware-0.log

    ===========

    [...]

    2016-09-01T11:09:45.061+02:00| vmx| I120: CPU4: PMC: IA32, Nehalem-C or later PMC: smmFrz (hw): (1)

    2016-09-01T11:09:45.061+02:00| vmx| I120:  [c:0 f:1 e:0]

    2016-09-01T11:09:45.061+02:00| vmx| I120: CPU5: PMC: IA32, Nehalem-C or later PMC: smmFrz (hw): (1)

    2016-09-01T11:09:45.061+02:00| vmx| I120:  [c:0 f:1 e:0]

    2016-09-01T11:09:45.061+02:00| vmx| I120: CPU6: PMC: IA32, Nehalem-C or later PMC: smmFrz (hw): (1)

    2016-09-01T11:09:45.061+02:00| vmx| I120:  [c:0 f:1 e:0]

    2016-09-01T11:09:45.061+02:00| vmx| I120: CPU7: PMC: IA32, Nehalem-C or later PMC: smmFrz (hw): (1)

    2016-09-01T11:09:45.061+02:00| vmx| I120:  [c:0 f:1 e:0]

    2016-09-01T11:09:45.061+02:00| vmx| I120: MONITOR MODE: allowed modes          : BT32 HV HWMMU

    2016-09-01T11:09:45.061+02:00| vmx| I120: MONITOR MODE: user requested modes   : BT32 HV HWMMU

    2016-09-01T11:09:45.061+02:00| vmx| I120: MONITOR MODE: guestOS preferred modes: HWMMU HV BT32

    2016-09-01T11:09:45.061+02:00| vmx| I120: MONITOR MODE: filtered list          : HWMMU HV BT32

    2016-09-01T11:09:45.061+02:00| vmx| I120: HV Settings: virtual exec = 'hardware'; virtual mmu = 'hardware'

    2016-09-01T11:09:45.065+02:00| vmx| I120: OvhdMem_PowerOn: initial admission: paged   569118 nonpaged     6073 anonymous     9947

    2016-09-01T11:09:45.065+02:00| vmx| I120: VMMEM: Initial Reservation: 2285MB (MainMem=3072MB)

    2016-09-01T11:09:45.065+02:00| vmx| I120: MemSched_PowerOn: balloon minGuestSize 209715 (80% of min required size 262144)

    2016-09-01T11:09:45.065+02:00| vmx| I120: MemSched: reserved mem (in MB) min 128 max 6972 recommended 6972

    2016-09-01T11:09:45.065+02:00| vmx| I120: MemSched: pg 569118 np 6073 anon 9947 mem 786432

    2016-09-01T11:09:45.065+02:00| vmx| I120: MemSched: numvm 2 locked pages: num 399485 max 1768448

    2016-09-01T11:09:45.065+02:00| vmx| I120: MemSched: locked Page Limit: host 1975122 config 1784832 dynam -1

    2016-09-01T11:09:45.065+02:00| vmx| I120: MemSched: minmempct 50 minalloc 302522 admitted 1

    2016-09-01T11:09:45.065+02:00| vmx| W110: NUMA: automatic VM sizing request ignored

    2016-09-01T11:09:45.065+02:00| vmx| I120: Host: Disabling thread priority boosting to work around Linux SMP bug.

    2016-09-01T11:09:45.065+02:00| vmx| I120: MsgHint: msg.hostposix.othervms

    2016-09-01T11:09:45.065+02:00| vmx| I120+ It appears that other virtual machines are running. Some host devices may be unavailable to this virtual machine. Some host devices (such as CD-ROM drives) may be shared among several virtual machines by toggling the entries in the "VM > Removable Devices" menu.

    2016-09-01T11:09:45.065+02:00| vmx| I120+ Select OK to continue, Cancel to power off.

    2016-09-01T11:09:45.065+02:00| vmx| I120+ ---------------------------------------

    2016-09-01T11:09:49.296+02:00| vmx| I120: Module Host power on failed.

    2016-09-01T11:09:49.296+02:00| vmx| I120: VMX_PowerOn: ModuleTable_PowerOn = 0

    2016-09-01T11:09:49.298+02:00| vmx| I120: Vix: [22455 mainDispatch.c:4291]: VMAutomation_ReportPowerOpFinished: statevar=1, newAppState=1873, success=1 additionalError=0

    2016-09-01T11:09:49.300+02:00| vmx| I120: Vix: [22455 mainDispatch.c:4291]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=1 additionalError=0

    2016-09-01T11:09:49.300+02:00| vmx| I120: Transitioned vmx/execState/val to poweredOff

    2016-09-01T11:09:49.300+02:00| vmx| I120: Vix: [22455 mainDispatch.c:4291]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=0 additionalError=0

    2016-09-01T11:09:49.300+02:00| vmx| I120: Vix: [22455 mainDispatch.c:4330]: Error VIX_E_FAIL in VMAutomation_ReportPowerOpFinished(): Unknown error

    2016-09-01T11:09:49.303+02:00| vmx| I120: Vix: [22455 mainDispatch.c:4291]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=1 additionalError=0

    2016-09-01T11:09:49.303+02:00| vmx| I120: Transitioned vmx/execState/val to poweredOff

    2016-09-01T11:09:49.303+02:00| vmx| I120: VMIOP: Exit

    2016-09-01T11:09:49.304+02:00| vmx| I120: Vix: [22455 mainDispatch.c:842]: VMAutomation_LateShutdown()

    2016-09-01T11:09:49.304+02:00| vmx| I120: Vix: [22455 mainDispatch.c:792]: VMAutomationCloseListenerSocket. Closing listener socket.

    2016-09-01T11:09:49.305+02:00| vmx| I120: Flushing VMX VMDB connections

    2016-09-01T11:09:49.306+02:00| vmx| I120: VmdbDbRemoveCnx: Removing Cnx from Db for '/db/connection/#1/'

    2016-09-01T11:09:49.306+02:00| vmx| I120: VmdbCnxDisconnect: Disconnect: closed pipe for pub cnx '/db/connection/#1/' (0)

    2016-09-01T11:09:49.306+02:00| vmx| I120: VigorTransport_ServerDestroy: server destroyed.

    2016-09-01T11:09:49.308+02:00| vmx| I120: VMX exit (0).

    2016-09-01T11:09:49.308+02:00| vmx| I120: OBJLIB-LIB: ObjLib cleanup done.

    2016-09-01T11:09:49.308+02:00| vmx| I120: FileTrack_Exit: done

     

    xubuntu14.04 starts automatically at boot time using Vix .... . But does it have some effekt to Win7?

     

     

    Memory is rare, I kow, but at the moment 4 GB is free and Win7 gets 3072 MB, that was enough so far:

     

    #!/usr/bin/vmware

    .encoding = "ISO-8859-1"

    config.version = "8"

    virtualHW.version = "11"

    numvcpus = "4"

    cpuid.coresPerSocket = "4"

    scsi0.present = "TRUE"

    scsi0.virtualDev = "lsisas1068"

    sata0.present = "TRUE"

    memsize = "3072"

    mem.hotadd = "TRUE"

    scsi0:0.present = "TRUE"

    scsi0:0.fileName = "win7-prof64.vmdk"

    sata0:1.present = "TRUE"

    sata0:1.fileName = "/dev/sr0"

    sata0:1.deviceType = "cdrom-raw"

    ethernet0.present = "TRUE"

    ethernet0.virtualDev = "e1000"

    ethernet0.wakeOnPcktRcv = "FALSE"

    ethernet0.addressType = "generated"

    usb.present = "TRUE"

    usb.generic.autoconnect = "FALSE"

    ehci.pciSlotNumber = "-1"

    mks.enable3d = "TRUE"

    svga.graphicsMemoryKB = "262144"

    pciBridge0.present = "TRUE"

    pciBridge4.present = "TRUE"

    pciBridge4.virtualDev = "pcieRootPort"

    pciBridge4.functions = "8"

    pciBridge5.present = "TRUE"

    pciBridge5.virtualDev = "pcieRootPort"

    pciBridge5.functions = "8"

    pciBridge6.present = "TRUE"

    pciBridge6.virtualDev = "pcieRootPort"

    pciBridge6.functions = "8"

    pciBridge7.present = "TRUE"

    pciBridge7.virtualDev = "pcieRootPort"

    pciBridge7.functions = "8"

    vmci0.present = "TRUE"

    hpet0.present = "TRUE"

    displayName = "win7-prof64"

    guestOS = "windows7-64"

    nvram = "win7-prof64.nvram"

    virtualHW.productCompatibility = "hosted"

    gui.exitOnCLIHLT = "TRUE"

    powerType.powerOff = "soft"

    powerType.powerOn = "soft"

    powerType.suspend = "soft"

    powerType.reset = "soft"

    extendedConfigFile = "win7-prof64.vmxf"

    uuid.bios = "56 4d 93 52 19 f7 8f 23-40 eb 24 cc 2e de bb a2"

    uuid.location = "56 4d 93 52 19 f7 8f 23-40 eb 24 cc 2e de bb a2"

    replay.supported = "FALSE"

    replay.filename = ""

    migrate.hostlog = "./win7-prof64-b295f18f.hlog"

    scsi0:0.redo = ""

    ethernet0.connectionType = "bridged"

    ethernet0.startConnected = "TRUE"

    pciBridge0.pciSlotNumber = "17"

    pciBridge4.pciSlotNumber = "21"

    pciBridge5.pciSlotNumber = "22"

    pciBridge6.pciSlotNumber = "23"

    pciBridge7.pciSlotNumber = "24"

    scsi0.pciSlotNumber = "160"

    usb.pciSlotNumber = "32"

    ethernet0.pciSlotNumber = "33"

    vmci0.pciSlotNumber = "34"

    sata0.pciSlotNumber = "35"

    scsi0.sasWWID = "50 05 05 62 19 f7 8f 20"

    ethernet0.generatedAddress = "00:0C:29:DE:BB:A2"

    ethernet0.generatedAddressOffset = "0"

    vmci0.id = "786348962"

    monitor.phys_bits_used = "42"

    vmotion.checkpointFBSize = "8388608"

    vmotion.checkpointSVGAPrimarySize = "33554432"

    cleanShutdown = "FALSE"

    softPowerOff = "TRUE"

    usb:1.speed = "2"

    usb:1.present = "TRUE"

    usb:1.deviceType = "hub"

    usb:1.port = "1"

    usb:1.parent = "-1"

    sata0:1.autodetect = "FALSE"

    toolsInstallManager.updateCounter = "1"

    tools.syncTime = "TRUE"

    unity.wasCapable = "FALSE"

    svga.guestBackedPrimaryAware = "TRUE"

    checkpoint.vmState = ""

    sound.present = "FALSE"

    serial0.present = "FALSE"

    floppy0.present = "FALSE"

    usb:0.present = "TRUE"

    usb:0.deviceType = "hid"

    usb:0.port = "0"

    usb:0.parent = "-1"

    [...]

     

    tia

    Eckard


    0 0

    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


    0 0

    Using VMware Workstation Player 12.1.1 build-3770994  on Linux Mint 18 to make a Windows 7 VM. The issue is that on the VMware Player menu bar, where you usually see items like "File", "VM", and "Help", only "File" appears. However, once I have the "File" dropdown menu open, I can slide my mouse over to the right and the next (unlabeled) menu opens, and then if I slide my  mouse over a little more, the "Help" menu opens. Or I can click on the unlabeled part of the menu bar where the labels for those menus would be, and the dropdown menus appear.

     

    Not a big thing, pretty much cosmetic since I can get to the unlabeled dropdown menus, but the Player is usually better than this. The menu bar labels and dropdown menus are usually all there, and the problems that I encounter are much more subtle operational problems. I've played around, but I don't see any way to bring the missing menu bar labels back. And I've removed and re-installed this (checked the md5sum after downloading, as well) and have seen the same thing both times.

     

    Any way to get the full menu bar labeling? Am I the only one seeing this?

     

    Thanks!


    0 0

    Thought I would share these with the VMware community.

     

    I was playing around with virtualisation and connecting to legacy hardware via USB and Serial Ports so decided to make a video tutorial and guide.

     

     

    The written guide may be found here:

    http://dellwindowsreinstallationguide.com/installation-of-windows-and-linux-on-a-virtual-machine-using-vmware-player/


    0 0

    Okay, this is really annoying. Using Workstation player 12.1.1, the latest, on a Linux Mint 18 Host OS, with a Windows 7 VM. Occasionally the mouse cursor gets offset somehow, and I have to click somewhere in the vicinity of the item that I'm aiming at. This is really intolerable, so I re-install vmware-tools (which I've had to do several times already because of this) yet again, and it corrects the problem after a VM reboot. Then this same thing happens again.

     

    I'm about ready to throw this thing out, both the player and the VM are more trouble than they're worth at this point...before I did that, thought I'd ask if there's anyone else experiencing this, and if there's some sort of workaround or something that I can do to keep this from happening?

     

    Thanks!


    0 0

    Hi,

    Copy&Paste is not working anymore between host and vm.

    I already re-installed the VM tools. While configuring  the tools I get the attached exception

    Host: Win10, VM: Ubuntu 16.04

     

    Thx for support.

    Peter


    0 0

    Hi,

     

    After having my 2 vm instances run about 16+ hrs on my video game, screen turns black on my instances and becomes unresponsive.

     

    I've only found threads on black screen at startup but haven't had luck with my scenario.

     

    Haven't been around to see it happen.

     

    windows 7, 128 gig hd space, sleep mode off, no screen saver, 4 gigs ram each instance, 3d acceleration gfx disabled,

     

    Host machine:

    i7-6700k overclocked to 4.6ghz

    gtx 1070

    32 gigs ram

    windows 10 home

     

    Anyone else have this problem or have any insight to fix this?

     

    Thanks


    0 0

    Does VMware player (I'm using version 7.1.4) support suspending the running VMs when the host OS (Windows 7) is shut down (or the user logs off)?

     

    I just tried to shutdown the host and Window tells me the VMWare Player processes are holding the process.

     

    I could swear this worked on the other computer, but that might have been VirtualPC and not VMWare Player. So someone please just confirm if VMware has this feature or not.

    Thanks.

     

    David


    0 0

    The difference is dramatic, near the point of unusability.

     

    The laptop has 8GB RAM. The VMWare virtual machine has 2GB.

     

    An Adobe Acrobat PDFmaker task in the VM is more than an order of magnitude slower than it was before the update.

     

    Anybody understand why this might be so, and what can be done about it?


    0 0

    I have a small LAN.

    My main machine as above communicates with the others via samba.

    This machine has an XP guest that communicates the host's folders via samba, not by VMware's shared folders facility which is disabled.

    I have been coerced into installing Windows 10 x32 so that my legacy software will continue to run.

    The problem is that I cannot get Windows 10 to access the shares. I have installed three times so far.

    One is Win 10 x64 which does access the hosts samba shares but I have spent several days trying to achieve the same with x32 without success.

    I've tried every trick that I could find on the www without success.

     

    Does anyone know or know someone who might know how to fix this?

     

    Thanks in advance


    0 0

    Hi

    I have a Surface Pro 4 with Windows 10 and VMWare Workstation 12 (12.1.1), using Mac OS X (10.11.6) as the guest OS

     

    Has anyone solved the scaling issue when using VMWare 12 Player  and Mac OS X as the guest VM. The Mac guest VM text/menus etc. are so small/unreadable on the screen of the Surface Pro 4. The Surface tablet screen is 2736 x 1824 and Windows 10 scaling is set to 225%. I also have 2 x Mac 27" cinema monitors running through a Surface dock at 2560 x 1400.

     

    I have tried amending the VMPlayer exe file compatibility to Win 8 and not to scale

     

    The VM Machine display settings are set to Use Host settings for Monitor. If I adjust it to say 1920 x 1440 it just makes the windows running on the Pro 4 smaller. Does not scape the text etc within the VM machine up

     

    When running the VM Wokrstation and Mac OS guest on the Surface screen natively (no ext monitors) everything is unreadibly small, but when running on one of the ext monitors all is perfectly workable

     

    I have tried a manifest file but VMPlayer refuses to start using the external manifest file.

     

    Ideas anyone???

    Thanks


    0 0
  • 09/08/16--05:08: Failure to access VMDK disk
  • Hi all,

     

    I have a VM for DragonFly BSD. It runs on a laptop on Windows 7 Pro and the virtual machine files, including the disks, are on a NTFS compressed folder.

    After some time the VM stopped working because it can't access the VMDK file:

     

    vmdk_failure.png

     

    I have tried to repair it and even though it reports the problem as fixed the VM still can't start up correctly or right after it does the problem occurs.

     

    Best regards,

    Antonio Huete


    0 0

    So I have tried every possible solution on the web, nothing works...

    Kali version: 4.6.0-kali1-amd64

    VMware version: VMware-Player-12.1.1-3770994.x86_64

    My log file:

    2016-09-12T15:57:55.525-05:00| vthread-4| I125: Log for VMware Workstation pid=6745 version=12.1.1 build=build-3770994 option=Release

    2016-09-12T15:57:55.525-05:00| vthread-4| I125: The process is 64-bit.

    2016-09-12T15:57:55.525-05:00| vthread-4| I125: Host codepage=UTF-8 encoding=UTF-8

    2016-09-12T15:57:55.525-05:00| vthread-4| I125: Host is Linux 4.6.0-kali1-amd64 Kali GNU/Linux Rolling

    2016-09-12T15:57:55.524-05:00| vthread-4| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory.

    2016-09-12T15:57:55.524-05:00| vthread-4| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.

    2016-09-12T15:57:55.525-05:00| vthread-4| I125: DictionaryLoad: Cannot open file "/root/.vmware/config": No such file or directory.

    2016-09-12T15:57:55.525-05:00| vthread-4| I125: PREF Optional preferences file not found at /root/.vmware/config. Using default values.

    2016-09-12T15:57:55.556-05:00| vthread-4| W115: Logging to /tmp/vmware-root/vmware-6745.log

    2016-09-12T15:57:55.560-05:00| vthread-4| I125: Obtaining info using the running kernel.

    2016-09-12T15:57:55.560-05:00| vthread-4| I125: Created new pathsHash.

    2016-09-12T15:57:55.560-05:00| vthread-4| I125: Setting header path for 4.6.0-kali1-amd64 to "/lib/modules/4.6.0-kali1-amd64/build/include".

    2016-09-12T15:57:55.560-05:00| vthread-4| I125: Validating path "/lib/modules/4.6.0-kali1-amd64/build/include" for kernel release "4.6.0-kali1-amd64".

    2016-09-12T15:57:55.560-05:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

    2016-09-12T15:57:55.564-05:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.6.0-kali1-amd64".

    2016-09-12T15:57:55.564-05:00| vthread-4| I125: The header path "/lib/modules/4.6.0-kali1-amd64/build/include" for the kernel "4.6.0-kali1-amd64" is valid.  Whoohoo!

    2016-09-12T15:57:55.650-05:00| vthread-4| I125: found symbol version file /lib/modules/4.6.0-kali1-amd64/build/Module.symvers

    2016-09-12T15:57:55.650-05:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.6.0-kali1-amd64/build/Module.symvers.

    2016-09-12T15:57:55.662-05:00| vthread-4| I125: Read 18158 symbol versions

    2016-09-12T15:57:55.662-05:00| vthread-4| I125: Reading in info for the vmmon module.

    2016-09-12T15:57:55.662-05:00| vthread-4| I125: Reading in info for the vmnet module.

    2016-09-12T15:57:55.662-05:00| vthread-4| I125: Reading in info for the vmblock module.

    2016-09-12T15:57:55.662-05:00| vthread-4| I125: Reading in info for the vmci module.

    2016-09-12T15:57:55.662-05:00| vthread-4| I125: Reading in info for the vsock module.

    2016-09-12T15:57:55.662-05:00| vthread-4| I125: Setting vsock to depend on vmci.

    2016-09-12T15:57:55.662-05:00| vthread-4| I125: Invoking modinfo on "vmmon".

    2016-09-12T15:57:55.664-05:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.

    2016-09-12T15:57:55.664-05:00| vthread-4| I125: Invoking modinfo on "vmnet".

    2016-09-12T15:57:55.665-05:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.

    2016-09-12T15:57:55.665-05:00| vthread-4| I125: Invoking modinfo on "vmblock".

    2016-09-12T15:57:55.665-05:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.

    2016-09-12T15:57:55.665-05:00| vthread-4| I125: Invoking modinfo on "vmci".

    2016-09-12T15:57:55.666-05:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.

    2016-09-12T15:57:55.666-05:00| vthread-4| I125: Invoking modinfo on "vsock".

    2016-09-12T15:57:55.667-05:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.

    2016-09-12T15:57:55.675-05:00| vthread-4| I125: to be installed: vmnet status: 0

    2016-09-12T15:57:55.680-05:00| vthread-4| I125: Obtaining info using the running kernel.

    2016-09-12T15:57:55.680-05:00| vthread-4| I125: Setting header path for 4.6.0-kali1-amd64 to "/lib/modules/4.6.0-kali1-amd64/build/include".

    2016-09-12T15:57:55.680-05:00| vthread-4| I125: Validating path "/lib/modules/4.6.0-kali1-amd64/build/include" for kernel release "4.6.0-kali1-amd64".

    2016-09-12T15:57:55.681-05:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

    2016-09-12T15:57:55.684-05:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.6.0-kali1-amd64".

    2016-09-12T15:57:55.684-05:00| vthread-4| I125: The header path "/lib/modules/4.6.0-kali1-amd64/build/include" for the kernel "4.6.0-kali1-amd64" is valid.  Whoohoo!

    2016-09-12T15:57:55.768-05:00| vthread-4| I125: found symbol version file /lib/modules/4.6.0-kali1-amd64/build/Module.symvers

    2016-09-12T15:57:55.768-05:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.6.0-kali1-amd64/build/Module.symvers.

    2016-09-12T15:57:55.780-05:00| vthread-4| I125: Read 18158 symbol versions

    2016-09-12T15:57:55.780-05:00| vthread-4| I125: Kernel header path retrieved from FileEntry: /lib/modules/4.6.0-kali1-amd64/build/include

    2016-09-12T15:57:55.780-05:00| vthread-4| I125: Update kernel header path to /lib/modules/4.6.0-kali1-amd64/build/include

    2016-09-12T15:57:55.780-05:00| vthread-4| I125: Validating path "/lib/modules/4.6.0-kali1-amd64/build/include" for kernel release "4.6.0-kali1-amd64".

    2016-09-12T15:57:55.780-05:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

    2016-09-12T15:57:55.784-05:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.6.0-kali1-amd64".

    2016-09-12T15:57:55.784-05:00| vthread-4| I125: The header path "/lib/modules/4.6.0-kali1-amd64/build/include" for the kernel "4.6.0-kali1-amd64" is valid.  Whoohoo!

    2016-09-12T15:57:55.785-05:00| vthread-4| I125: Found compiler at "/usr/bin/gcc"

    2016-09-12T15:57:55.786-05:00| vthread-4| I125: Got gcc version "5.4.1".

    2016-09-12T15:57:55.786-05:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.

    2016-09-12T15:57:55.786-05:00| vthread-4| I125: Using user supplied compiler "/usr/bin/gcc".

    2016-09-12T15:57:55.787-05:00| vthread-4| I125: Got gcc version "5.4.1".

    2016-09-12T15:57:55.788-05:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.

    2016-09-12T15:57:55.788-05:00| vthread-4| I125: Trying to find a suitable PBM set for kernel "4.6.0-kali1-amd64".

    2016-09-12T15:57:55.788-05:00| vthread-4| I125: No matching PBM set was found for kernel "4.6.0-kali1-amd64".

    2016-09-12T15:57:55.788-05:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.

    2016-09-12T15:57:55.788-05:00| vthread-4| I125: Validating path "/lib/modules/4.6.0-kali1-amd64/build/include" for kernel release "4.6.0-kali1-amd64".

    2016-09-12T15:57:55.788-05:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

    2016-09-12T15:57:55.792-05:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.6.0-kali1-amd64".

    2016-09-12T15:57:55.792-05:00| vthread-4| I125: The header path "/lib/modules/4.6.0-kali1-amd64/build/include" for the kernel "4.6.0-kali1-amd64" is valid.  Whoohoo!

    2016-09-12T15:57:55.793-05:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.

    2016-09-12T15:57:55.793-05:00| vthread-4| I125: Validating path "/lib/modules/4.6.0-kali1-amd64/build/include" for kernel release "4.6.0-kali1-amd64".

    2016-09-12T15:57:55.793-05:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

    2016-09-12T15:57:55.796-05:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.6.0-kali1-amd64".

    2016-09-12T15:57:55.796-05:00| vthread-4| I125: The header path "/lib/modules/4.6.0-kali1-amd64/build/include" for the kernel "4.6.0-kali1-amd64" is valid.  Whoohoo!

    2016-09-12T15:57:55.796-05:00| vthread-4| I125: Using temp dir "/tmp".

    2016-09-12T15:57:55.797-05:00| vthread-4| I125: Obtaining info using the running kernel.

    2016-09-12T15:57:55.797-05:00| vthread-4| I125: Setting header path for 4.6.0-kali1-amd64 to "/lib/modules/4.6.0-kali1-amd64/build/include".

    2016-09-12T15:57:55.797-05:00| vthread-4| I125: Validating path "/lib/modules/4.6.0-kali1-amd64/build/include" for kernel release "4.6.0-kali1-amd64".

    2016-09-12T15:57:55.797-05:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

    2016-09-12T15:57:55.800-05:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.6.0-kali1-amd64".

    2016-09-12T15:57:55.800-05:00| vthread-4| I125: The header path "/lib/modules/4.6.0-kali1-amd64/build/include" for the kernel "4.6.0-kali1-amd64" is valid.  Whoohoo!

    2016-09-12T15:57:55.883-05:00| vthread-4| I125: found symbol version file /lib/modules/4.6.0-kali1-amd64/build/Module.symvers

    2016-09-12T15:57:55.883-05:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.6.0-kali1-amd64/build/Module.symvers.

    2016-09-12T15:57:55.896-05:00| vthread-4| I125: Read 18158 symbol versions

    2016-09-12T15:57:55.896-05:00| vthread-4| I125: Invoking modinfo on "vmnet".

    2016-09-12T15:57:55.897-05:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.

    2016-09-12T15:57:56.189-05:00| vthread-4| I125: Setting destination path for vmnet to "/lib/modules/4.6.0-kali1-amd64/misc/vmnet.ko".

    2016-09-12T15:57:56.189-05:00| vthread-4| I125: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar".

    2016-09-12T15:57:56.191-05:00| vthread-4| I125: Successfully extracted the vmnet source.

    2016-09-12T15:57:56.191-05:00| vthread-4| I125: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-lb6BCQ/vmnet-only auto-build HEADER_DIR=/lib/modules/4.6.0-kali1-amd64/build/include CC=/usr/bin/gcc IS_GCC_3=no"

    2016-09-12T15:57:57.093-05:00| vthread-4| W115: Failed to build vmnet.  Failed to execute the build command.

     

    My Kernel headers are fine and my GCC is on version 5.4.1 also working, my only problem is "Unable to start services."

     

    PLEASE HELP!


    0 0

    I'm having a problem with my CentOS 7 guest on Windows 7 host, whereby every once in a while (and fairly often), a keypress will just start to repeat so I get a whole string of "s" or "a" or CRs or whatever.  I have to press another key to get it to stop.  The standard fix of adding "keyboard.typematicMinDelay" to the vmx file doesn't seem to be working.

     

    This also happened on my Windows 10 guest on the same Windows 7 host, and I was able to fix it by adding 'keyboard.typematicMinDelay = "2000000"' to its vmx file.  However, adding that same parameter to the CentOS guest's vmx file did nothing... the guest ignores it.

     

    I also tried "xset r rate 1000 10" in the CentOS guest, and all that does is slow the rep rate down, but I still get repeats where I don't want them.

     

    What can I do to make the CentOS guest recognize the changed keyboard.typematicMinDelay parameter?  As I said it just ignores it.

     

    Version of Player is Workstation 12 Player version 12.1.0 build 3272444.

     

    Thanks...

     

    Eric


    0 0

    Distribution

    CentOS6.8 Kernel 2.6.32-642.4.2.el6.x86_64

     

    Until Ws12.1.1 was able to run


older | 1 | .... | 148 | 149 | (Page 150) | 151 | 152 | .... | 252 | newer