Guten Morgen,
kann mir jemand schreiben, wie ich den VMware Player wieder deinstalliere?
Vielen Dank.
Claus
Guten Morgen,
kann mir jemand schreiben, wie ich den VMware Player wieder deinstalliere?
Vielen Dank.
Claus
I'm running Player 12.5.1 on a Linux (Fedora 25) host and the option for echo cancellation does not show up in the Hardware/Sound panel when running a Windows 7 guest. According to the documentation, echo cancellation support was added to Workstation 12 & Player 12 and I should see a checkbox for it. I thought maybe it didn't work for this VM created with an older version of Player, or only worked on a newer version of Windows, but I started creation of a VM for Windows 10 (far enough to get to the 'customize hardware' option before it is actually created) and it still didn't show up.
Perhaps my host is incorrectly configured and that's why it doesn't show up? I did a pretty vanilla install of Fedora 25, and have a fairly generic Kaby Lake based laptop without any funky hardware. Any ideas?
Here is the output of lspci -vv for the sound card. Since it shows up as a 'device 9d71' maybe it isn't fully supported in Linux yet?
00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21)
Subsystem: Hewlett-Packard Company Device 81ff
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 130
Region 0: Memory at b1328000 (64-bit, non-prefetchable) [size=16K]
Region 4: Memory at b1310000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: 00000000fee00338 Data: 0000
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl
uname -a:
Linux XXX 4.8.15-300.fc25.x86_64 #1 SMP Thu Dec 15 23:10:23 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
After installing Vmware Player on a Windows 7 x64 (HP Z440) the hosts NIC disconnects randomly and stays disconnected for about 5-10 minutes, then it comes back online and stays online for just a minute or so Before it disconnects again.
In the event log I see event id 27
Source: e1dexpress
Intel(R) Ethernet Connection (2) I218-LM
Network link is disconnected.
If I disable the VMware Network Adapters It works fine but as soon I enable them again I start getting the disconnects again.
Has anyone seen this before?
Do I need to configure the hosts NIC in some way?
Or the VMware NIC maybe?
I have been using Workstation 12 Player and I want to upgrade it to 12.5
I downloaded VMware-player-12.5.2-4638234.exe and started installation.
I received the following message:
"This product installer does not support downgrades."
What does this mean? Is there a different installer to download? Must I uninstall version 12?
Thanks for any help.
Ken Gash
Hi. Help me please.
Windows 10
can't install VMware Workstation player. "blinks" during the installation.this is the end.
here is the logs from the temp folder:
vminst.log
2017-01-12 06:36:20| BootStrapper-build-3272444| Begin Logging
2017-01-12 06:36:20| BootStrapper-build-3272444| Operating system info:
2017-01-12 06:36:20| BootStrapper-build-3272444| Admin install = TRUE
2017-01-12 06:36:20| BootStrapper-build-3272444| Major version = 6
2017-01-12 06:36:20| BootStrapper-build-3272444| Minor version = 3
2017-01-12 06:36:20| BootStrapper-build-3272444| Service pack = 0
2017-01-12 06:36:20| BootStrapper-build-3272444| Build number = 9600
2017-01-12 06:36:20| BootStrapper-build-3272444| Bitness = 64-bit
2017-01-12 06:36:20| BootStrapper-build-3272444| Platform = NT
2017-01-12 06:36:20| BootStrapper-build-3272444| Running from: "G:\downloads\VMware-player-12.1.0-3272444.exe"
2017-01-12 06:36:20| BootStrapper-build-3272444| [Resource] MINORUPGRADE = 0
2017-01-12 06:36:20| BootStrapper-build-3272444| Performing standard MSI install/major upgrade
2017-01-12 06:36:20| BootStrapper-build-3272444| [Resource] PRODUCT_REG_NAME = <not defined>
2017-01-12 06:36:20| BootStrapper-build-3272444| Silent installation = FALSE
2017-01-12 06:36:20| BootStrapper-build-3272444| Upgrade at shutdown = FALSE
2017-01-12 06:36:20| BootStrapper-build-3272444| [Resource] SKIPADMINCHECK = <not defined>
2017-01-12 06:36:20| BootStrapper-build-3272444| [Resource] OPERATION = INSTALLUPD
2017-01-12 06:36:20| BootStrapper-build-3272444| [Resource] PRODUCTNAME = VMware Player
2017-01-12 06:36:20| BootStrapper-build-3272444| [Resource] UPGRADECODE = {217329DA-42FA-11E2-B26F-FAF46088709B}
2017-01-12 06:36:20| BootStrapper-build-3272444| [Resource] PRODUCTCODE = {57AA4E8A-E2C9-4F1C-B3F1-762C36E34472}
2017-01-12 06:36:20| BootStrapper-build-3272444| [Resource] LANGUAGES = 1041 2052
2017-01-12 06:36:20| BootStrapper-build-3272444| [Resource] VM_DATABASE64 = <not defined>
2017-01-12 06:36:20| BootStrapper-build-3272444| [Resource] VM_DATABASE = VMwarePlayer.msi
2017-01-12 06:36:20| BootStrapper-build-3272444| [Resource] SFXINSERT = 1171456
2017-01-12 06:36:20| BootStrapper-build-3272444| [Resource] VMIOPTION = one
2017-01-12 06:36:20| BootStrapper-build-3272444| [Resource] CACHEMSI = 1
2017-01-12 06:36:20| BootStrapper-build-3272444| Cache MSI set to TRUE
2017-01-12 06:36:20| BootStrapper-build-3272444| [Resource] MINIMUM_9X_MSI = 200
2017-01-12 06:36:20| BootStrapper-build-3272444| [Resource] MINIMUM_NT_MSI = 300
2017-01-12 06:36:20| BootStrapper-build-3272444| [Resource] INSTMSIW = <not defined>
2017-01-12 06:36:20| BootStrapper-build-3272444| [Resource] VCRUNTIME32 = vcredist_x86.exe
2017-01-12 06:36:20| BootStrapper-build-3272444| [Resource] VCRUNTIME64 = vcredist_x64.exe
2017-01-12 06:36:20| BootStrapper-build-3272444| [Resource] PROPERTIES = <not defined>
2017-01-12 06:36:20| BootStrapper-build-3272444| [Resource] OLDCODES =
2017-01-12 06:36:20| BootStrapper-build-3272444| [Resource] HELPER_UI = <not defined>
2017-01-12 06:36:20| BootStrapper-build-3272444| [Info] Loading splash bitmap from resource id 1033.
2017-01-12 06:36:20| BootStrapper-build-3272444| [Info] Loaded splash bitmap from resource 1033.
2017-01-12 06:36:20| BootStrapper-build-3272444| UI thread started successfully
2017-01-12 06:36:20| BootStrapper-build-3272444| The user's default locale is 1049
2017-01-12 06:36:20| BootStrapper-build-3272444| Total unpacked size will be 69 MB (71941808 bytes)
2017-01-12 06:36:20| BootStrapper-build-3272444| [Resource] REQ_MB_SPACE = <not defined>
2017-01-12 06:36:20| BootStrapper-build-3272444| Total space required to unpack is 133 MB (138758969 bytes)
2017-01-12 06:36:20| BootStrapper-build-3272444| Attempting to find best location for unpacking temporary installation files
2017-01-12 06:36:20| BootStrapper-build-3272444| Examining drive for temp folder "C:\Users\Fast10\AppData\Local\Temp\"
2017-01-12 06:36:20| BootStrapper-build-3272444| Local fixed drive C: has 30793 MB (32288542720 bytes) free
2017-01-12 06:36:20| BootStrapper-build-3272444| Local fixed drive D: has 134312 MB (140835962880 bytes) free
2017-01-12 06:36:20| BootStrapper-build-3272444| Local fixed drive F: has 130817 MB (137171116032 bytes) free
2017-01-12 06:36:20| BootStrapper-build-3272444| Local fixed drive G: has 81665 MB (85631729664 bytes) free
2017-01-12 06:36:20| BootStrapper-build-3272444| Local fixed drive H: has 96737 MB (101435367424 bytes) free
2017-01-12 06:36:20| BootStrapper-build-3272444| Local fixed drive I: has 148205 MB (155403649024 bytes) free
2017-01-12 06:36:20| BootStrapper-build-3272444| CurrentLocation "C:\Users\Fast10\AppData\Local\Temp\{57AA4E8A-E2C9-4F1C-B3F1-762C36E34472}~setup\"
2017-01-12 06:36:20| BootStrapper-build-3272444| Deleting [C:\Users\Fast10\AppData\Local\Temp\{57AA4E8A-E2C9-4F1C-B3F1-762C36E34472}~setup\]
2017-01-12 06:36:20| BootStrapper-build-3272444| Creating directory 'C:\Users\Fast10\AppData\Local\Temp\{57AA4E8A-E2C9-4F1C-B3F1-762C36E34472}~setup\'
2017-01-12 06:36:20| BootStrapper-build-3272444| Selecting "C:\Users\Fast10\AppData\Local\Temp\{57AA4E8A-E2C9-4F1C-B3F1-762C36E34472}~setup\" for unpacking temp files
2017-01-12 06:36:20| BootStrapper-build-3272444| Extracting setup files to "C:\Users\Fast10\AppData\Local\Temp\{57AA4E8A-E2C9-4F1C-B3F1-762C36E34472}~setup\"
2017-01-12 06:36:20| BootStrapper-build-3272444| --> VMwarePlayer.msi [62230528]
2017-01-12 06:36:20| BootStrapper-build-3272444| --> vcredist_x86.exe [4485976]
2017-01-12 06:36:20| BootStrapper-build-3272444| --> vcredist_x64.exe [5225304]
2017-01-12 06:36:20| BootStrapper-build-3272444| IsMsiUpgradeNecessary: No upgrade is necessary. Windows Installer version 500 meets minimum requirements
2017-01-12 06:36:20| BootStrapper-build-3272444| [Resource] VCRUNTIME_VER = 9
2017-01-12 06:36:20| BootStrapper-build-3272444| Look for VC 9 x32 runtime libraries.
2017-01-12 06:36:20| BootStrapper-build-3272444| install state for product code {1F1C2DFC-2D24-3E06-BCB8-725134ADF989} = 5
2017-01-12 06:36:20| BootStrapper-build-3272444| VC 9 x32 runtimes are already installed
2017-01-12 06:36:20| BootStrapper-build-3272444| Look for VC 9 x64 runtime libraries.
2017-01-12 06:36:20| BootStrapper-build-3272444| install state for product code {4B6C7001-C7D6-3710-913E-5BC23FCE91E6} = 5
2017-01-12 06:36:20| BootStrapper-build-3272444| VC 9 x64 runtimes are already installed
2017-01-12 06:36:20| BootStrapper-build-3272444| Caching installer in: C:\Program Files (x86)\Common Files\VMware\InstallerCache
2017-01-12 06:36:20| BootStrapper-build-3272444| Found "C:\Users\Fast10\AppData\Local\Temp\{57AA4E8A-E2C9-4F1C-B3F1-762C36E34472}~setup\VMwarePlayer.msi"
2017-01-12 06:36:20| BootStrapper-build-3272444| Found "C:\Program Files (x86)\Common Files\VMware\InstallerCache"
2017-01-12 06:36:20| BootStrapper-build-3272444| Copy 'C:\Users\Fast10\AppData\Local\Temp\{57AA4E8A-E2C9-4F1C-B3F1-762C36E34472}~setup\VMwarePlayer.msi' to 'C:\Program Files (x86)\Common Files\VMware\InstallerCache\{57AA4E8A-E2C9-4F1C-B3F1-762C36E34472}.msi'
vminst_log_20170112_063616_Failed.log
2017-01-12 06:36:15| BootStrapper-build-3272444| Begin Logging
2017-01-12 06:36:15| BootStrapper-build-3272444| Operating system info:
2017-01-12 06:36:15| BootStrapper-build-3272444| Admin install = TRUE
2017-01-12 06:36:15| BootStrapper-build-3272444| Major version = 6
2017-01-12 06:36:15| BootStrapper-build-3272444| Minor version = 3
2017-01-12 06:36:15| BootStrapper-build-3272444| Service pack = 0
2017-01-12 06:36:15| BootStrapper-build-3272444| Build number = 9600
2017-01-12 06:36:15| BootStrapper-build-3272444| Bitness = 64-bit
2017-01-12 06:36:15| BootStrapper-build-3272444| Platform = NT
2017-01-12 06:36:15| BootStrapper-build-3272444| Running from: "G:\downloads\VMware-player-12.1.0-3272444.exe"
2017-01-12 06:36:15| BootStrapper-build-3272444| [Resource] MINORUPGRADE = 0
2017-01-12 06:36:15| BootStrapper-build-3272444| Performing standard MSI install/major upgrade
2017-01-12 06:36:15| BootStrapper-build-3272444| [Resource] PRODUCT_REG_NAME = <not defined>
2017-01-12 06:36:15| BootStrapper-build-3272444| Silent installation = FALSE
2017-01-12 06:36:15| BootStrapper-build-3272444| Upgrade at shutdown = FALSE
2017-01-12 06:36:15| BootStrapper-build-3272444| [Resource] SKIPADMINCHECK = <not defined>
2017-01-12 06:36:15| BootStrapper-build-3272444| [Resource] OPERATION = INSTALLUPD
2017-01-12 06:36:15| BootStrapper-build-3272444| [Resource] PRODUCTNAME = VMware Player
2017-01-12 06:36:15| BootStrapper-build-3272444| [Resource] UPGRADECODE = {217329DA-42FA-11E2-B26F-FAF46088709B}
2017-01-12 06:36:15| BootStrapper-build-3272444| [Resource] PRODUCTCODE = {57AA4E8A-E2C9-4F1C-B3F1-762C36E34472}
2017-01-12 06:36:15| BootStrapper-build-3272444| [Resource] LANGUAGES = 1041 2052
2017-01-12 06:36:15| BootStrapper-build-3272444| [Resource] VM_DATABASE64 = <not defined>
2017-01-12 06:36:15| BootStrapper-build-3272444| [Resource] VM_DATABASE = VMwarePlayer.msi
2017-01-12 06:36:15| BootStrapper-build-3272444| [Resource] SFXINSERT = 1171456
2017-01-12 06:36:15| BootStrapper-build-3272444| [Resource] VMIOPTION = one
2017-01-12 06:36:15| BootStrapper-build-3272444| [Resource] CACHEMSI = 1
2017-01-12 06:36:15| BootStrapper-build-3272444| Cache MSI set to TRUE
2017-01-12 06:36:15| BootStrapper-build-3272444| [Resource] MINIMUM_9X_MSI = 200
2017-01-12 06:36:15| BootStrapper-build-3272444| [Resource] MINIMUM_NT_MSI = 300
2017-01-12 06:36:15| BootStrapper-build-3272444| [Resource] INSTMSIW = <not defined>
2017-01-12 06:36:15| BootStrapper-build-3272444| [Resource] VCRUNTIME32 = vcredist_x86.exe
2017-01-12 06:36:15| BootStrapper-build-3272444| [Resource] VCRUNTIME64 = vcredist_x64.exe
2017-01-12 06:36:15| BootStrapper-build-3272444| [Resource] PROPERTIES = <not defined>
2017-01-12 06:36:15| BootStrapper-build-3272444| [Resource] OLDCODES =
2017-01-12 06:36:15| BootStrapper-build-3272444| [Resource] HELPER_UI = <not defined>
2017-01-12 06:36:15| BootStrapper-build-3272444| [Info] Loading splash bitmap from resource id 1033.
2017-01-12 06:36:15| BootStrapper-build-3272444| [Info] Loaded splash bitmap from resource 1033.
2017-01-12 06:36:15| BootStrapper-build-3272444| UI thread started successfully
2017-01-12 06:36:15| BootStrapper-build-3272444| The user's default locale is 1049
2017-01-12 06:36:15| BootStrapper-build-3272444| Total unpacked size will be 69 MB (71941808 bytes)
2017-01-12 06:36:15| BootStrapper-build-3272444| [Resource] REQ_MB_SPACE = <not defined>
2017-01-12 06:36:15| BootStrapper-build-3272444| Total space required to unpack is 133 MB (138758969 bytes)
2017-01-12 06:36:15| BootStrapper-build-3272444| Attempting to find best location for unpacking temporary installation files
2017-01-12 06:36:15| BootStrapper-build-3272444| Examining drive for temp folder "C:\Users\Fast10\AppData\Local\Temp\"
2017-01-12 06:36:15| BootStrapper-build-3272444| Local fixed drive C: has 30793 MB (32288559104 bytes) free
2017-01-12 06:36:15| BootStrapper-build-3272444| Local fixed drive D: has 134312 MB (140835962880 bytes) free
2017-01-12 06:36:15| BootStrapper-build-3272444| Local fixed drive F: has 130817 MB (137171116032 bytes) free
2017-01-12 06:36:15| BootStrapper-build-3272444| Local fixed drive G: has 81665 MB (85631729664 bytes) free
2017-01-12 06:36:15| BootStrapper-build-3272444| Local fixed drive H: has 96737 MB (101435367424 bytes) free
2017-01-12 06:36:15| BootStrapper-build-3272444| Local fixed drive I: has 148205 MB (155403649024 bytes) free
2017-01-12 06:36:15| BootStrapper-build-3272444| CurrentLocation "C:\Users\Fast10\AppData\Local\Temp\{57AA4E8A-E2C9-4F1C-B3F1-762C36E34472}~setup\"
2017-01-12 06:36:15| BootStrapper-build-3272444| Deleting [C:\Users\Fast10\AppData\Local\Temp\{57AA4E8A-E2C9-4F1C-B3F1-762C36E34472}~setup\]
2017-01-12 06:36:15| BootStrapper-build-3272444| Creating directory 'C:\Users\Fast10\AppData\Local\Temp\{57AA4E8A-E2C9-4F1C-B3F1-762C36E34472}~setup\'
2017-01-12 06:36:15| BootStrapper-build-3272444| Selecting "C:\Users\Fast10\AppData\Local\Temp\{57AA4E8A-E2C9-4F1C-B3F1-762C36E34472}~setup\" for unpacking temp files
2017-01-12 06:36:15| BootStrapper-build-3272444| Extracting setup files to "C:\Users\Fast10\AppData\Local\Temp\{57AA4E8A-E2C9-4F1C-B3F1-762C36E34472}~setup\"
2017-01-12 06:36:15| BootStrapper-build-3272444| --> VMwarePlayer.msi [62230528]
2017-01-12 06:36:16| BootStrapper-build-3272444| --> vcredist_x86.exe [4485976]
2017-01-12 06:36:16| BootStrapper-build-3272444| --> vcredist_x64.exe [5225304]
2017-01-12 06:36:16| BootStrapper-build-3272444| IsMsiUpgradeNecessary: No upgrade is necessary. Windows Installer version 500 meets minimum requirements
2017-01-12 06:36:16| BootStrapper-build-3272444| [Resource] VCRUNTIME_VER = 9
2017-01-12 06:36:16| BootStrapper-build-3272444| Look for VC 9 x32 runtime libraries.
2017-01-12 06:36:16| BootStrapper-build-3272444| install state for product code {1F1C2DFC-2D24-3E06-BCB8-725134ADF989} = 5
2017-01-12 06:36:16| BootStrapper-build-3272444| VC 9 x32 runtimes are already installed
2017-01-12 06:36:16| BootStrapper-build-3272444| Look for VC 9 x64 runtime libraries.
2017-01-12 06:36:16| BootStrapper-build-3272444| install state for product code {4B6C7001-C7D6-3710-913E-5BC23FCE91E6} = 5
2017-01-12 06:36:16| BootStrapper-build-3272444| VC 9 x64 runtimes are already installed
2017-01-12 06:36:16| BootStrapper-build-3272444| Caching installer in: C:\Program Files (x86)\Common Files\VMware\InstallerCache
2017-01-12 06:36:16| BootStrapper-build-3272444| Found "C:\Users\Fast10\AppData\Local\Temp\{57AA4E8A-E2C9-4F1C-B3F1-762C36E34472}~setup\VMwarePlayer.msi"
2017-01-12 06:36:16| BootStrapper-build-3272444| Found "C:\Program Files (x86)\Common Files\VMware\InstallerCache"
2017-01-12 06:36:16| BootStrapper-build-3272444| Copy 'C:\Users\Fast10\AppData\Local\Temp\{57AA4E8A-E2C9-4F1C-B3F1-762C36E34472}~setup\VMwarePlayer.msi' to 'C:\Program Files (x86)\Common Files\VMware\InstallerCache\{57AA4E8A-E2C9-4F1C-B3F1-762C36E34472}.msi'
2017-01-12 06:36:16| BootStrapper-build-3272444| MSI cached as: C:\Program Files (x86)\Common Files\VMware\InstallerCache\{57AA4E8A-E2C9-4F1C-B3F1-762C36E34472}.msi
I am using Windows 10 and recently installed vmware player 12.5 to run Linux on my system and I am constantly getting errors when i try to play any distro of Linux stating the following:
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.
I have hyper-v activated in Windows and have verified I am, in fact, running a 64-bit OS and processor so the 64 bit guest OS should be able to run just fine. I use Mcafee Internet Security as my AV and can't think of anything that would interfere with the guest OS from that particular AV. I am doing this at home so that I can practice with Linux for my online college classes. Any information that can be offered on solving this issue would be greatly appreciated. I have attached the vmware.log file from my Ubuntu 64-bit 16.04.1 VM.
Hello,
I am trying to find a way (preferably through the GUI so that it's quick to toggle on and off) to disable the clipboard sharing between Host and Guest. I have checked under both Player > File > Preferences and under the VM's Settings > Options tab. I can find references to "Guest Isolation" under documentation for Workstation Pro but nothing for Workstation Player. I couldn't find any reference to Guest Isolation in the Workstation Player Help doc.
Is clipboard sharing disabling simply not supported in Player? If so, it just seems so strange since one of the reasons for running a VM is security. I would like to keep VMware Tools installed.
Guys,
My testenvironment in Vmware Player, receives dhcp leases from my mainnetwork, although the networkcardsettings in player are local only.
Anyone who can help me with this?
Thanks.
Folk,
Hello. I am using VMware Workstation Player 12.5.
My host machine is Windows 10 with hard disk 1TB (1000GB).
My guest machine is Oracle Linux 5 with virtual hard disk 100GB currently.
I need to expand my virtual hard disk 100GB to the maximum size. I have checked the 2 links below:
1)https://technet.microsoft.com/en-us/library/cc708315(v=ws.10).aspx indicates:
The maximum size for a virtual hard disk is 2,040 gigabytes (GB). However, any virtual hard disk attached to the IDE controller cannot exceed 127 gigabytes (GB). To support a larger virtual hard disk size, attach the virtual hard disk to a SCSI adapter.
2)https://www.vmware.com/support/ws45/doc/disks_config_ws.html indicates:
IDE virtual disks can be as large as 128GB. SCSI virtual disks can be as large as 256GB. Depending on the size of the virtual disk and the host operating system, VMware Workstation creates one or more files to hold each virtual disk.
The first link indicates max size 2040GB.
The second link indicates max size 256GB.
My questions are:
1) What's the max size of a Virtual Hard Disk ?
2) Either 2040GB or 256GB is not enough for my Virtual Machine as a Server. Can we migrate the Virtual Hard Disk to a large hard disk of physical machine ?
Thanks in advance.
I have some problems:
I look forward for any response or suggestion. Any suggestion would be appreciated. Thanks.
I have encountered a major problem with an old version of VMWare Player (VMware-player-6.0.1-1379776):
The machine that I have this on has been successfully upgraded through various Windows versions from Windows 7 to the current Windows 10 "Anniversary" 1607. At no time did any messages appear about incompatibility.
It is now impossible to upgrade the VMWare Player as the original VMware-player-6.0.1-1379776 will not uninstall, giving the dreaded MSI error. Furthermore, when attempting to use the original exe to achieve a re-install one receives the message that the program will not run under this versions of windows. Any attempt to tell Windows 10 to run it in compatibility mode for either Windows 7 or 8 fails with the same message.
I have followed the instructions for manual removal as detailed in:
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1308
to the letter.
This results in a host system that has no keyboard or touchpad, and is not repairable with either SFC or DISM.
I have also tried third party uninstallers, (both Microsoft and Revo), the result is the same, no keyboard or mouse.
Fortunately I have multiple working partitions on this machine so I can always copy back the original partition the Windows 10 with a working keyboard and mouse.
The crazy thing is that the VMware-player-6.0.1 still loads and works fine with no need to set any compatibility settings at all!!
I am thus stuck in a mortal embrace that is only resolvable by a clean install of Windows 10. Having spent over a day of my life so far on this then thought of having to re-install and register another 50 or so programs fills me with dread!
I suspect the problem is to do with driver signing in newer versions of Windows 10. I have tried turning this off in Windows 10 and it made no difference, but I suspect that is where the problem lies.
Any ideas anyone??
I have VMWare Player 7.1.4 build-3848939 on Windows 8.1 Pro 64 bit.
I created a VM running Ubuntu 16.10 32 bit (with all updates and vmware tools).
Then I dragdropped a large file (7GB) into the Documents folder. Everything seemed fine, but then I noticed the destination file was only 184320 bytes big.
There was a correct copy of the file in ~/.cache/vmware/drag_and_drop/525ed2c1-c8b1-d3e2-e8d6-628905d57fed/
Versions of the vmtools:
Mware Tools daemon, version 9.9.5.55150 (build-3735633)
See attached manifest.txt
Regards,
David
Hello,
In the virtual machine settings, there is an option to set the number of process cores for the VM. Now assume I have a 4 core proc with HT, so 8 threads, can I set the vm to "have" 6 cores? Is there any actual benefit to doing so, and how are the host's resources actually allocated? Would the VM have effectively 6 threads on the host to work with?
Thanks
Hello everyone,
I recently installed VMWare Workstation Player in my personal laptop, the problem is that the 1920x1080 resolution isn't available, after looking for information I installed the VMWare Tools, systemctl is telling me that it works fine, yet there is no way of changing the resolution to 1920x1080.
I tried several things using xrandr but it doesn't work at all.
I'm new to VMWare, do you know a way to make it works?
$ xrandr
Screen 0: minimum 320 x 200, current 1280 x 768, maximum 8192 x 8192
XWAYLAND0 connected
1280x768 59.87 +
$ uname -r 4.8.6-300.fc25.x86_64 # systemctl status vmware-tools ● vmware-tools.service - SYSV: Manages the services needed to run VMware softwar Loaded: loaded (/etc/rc.d/init.d/vmware-tools; generated; vendor preset: disa Active: active (running) since lun. 2017-01-30 22:49:41 CET; 25min ago Docs: man:systemd-sysv-generator(8)
Might be a newbie question but after spending several hours on it I couldn't find a solution :s
Help me dear VMWare lords
Hi, I just installed archlinux but have this problem and don't know how to solve it. Can anyone help?
This is the log file
Log for VMware Workstation pid=501 version=12.5.2 build=build-4638234 option=Release
2017-02-04T11:18:04.802+07:00| vthread-4| I125: The process is 64-bit.
2017-02-04T11:18:04.802+07:00| vthread-4| I125: Host codepage=UTF-8 encoding=UTF-8
2017-02-04T11:18:04.802+07:00| vthread-4| I125: Host is unknown
2017-02-04T11:18:04.791+07:00| vthread-4| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory.
2017-02-04T11:18:04.791+07:00| vthread-4| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.
2017-02-04T11:18:04.801+07:00| vthread-4| I125: DictionaryLoad: Cannot open file "/root/.vmware/config": No such file or directory.
2017-02-04T11:18:04.801+07:00| vthread-4| I125: PREF Optional preferences file not found at /root/.vmware/config. Using default values.
2017-02-04T11:18:04.801+07:00| vthread-4| I125: PREF Unable to check permissions for preferences file.
2017-02-04T11:18:04.801+07:00| vthread-4| I125: DictionaryLoad: Cannot open file "/root/.vmware/preferences": No such file or directory.
2017-02-04T11:18:04.801+07:00| vthread-4| I125: PREF Failed to load user preferences.
2017-02-04T11:18:04.808+07:00| vthread-4| W115: HostinfoReadDistroFile: Cannot work with empty file.
2017-02-04T11:18:04.808+07:00| vthread-4| W115: HostinfoOSData: Error: no distro file found
2017-02-04T11:18:04.808+07:00| vthread-4| W115: Logging to /tmp/vmware-root/vmware-501.log
2017-02-04T11:18:04.817+07:00| vthread-4| I125: Obtaining info using the running kernel.
2017-02-04T11:18:04.817+07:00| vthread-4| I125: Created new pathsHash.
2017-02-04T11:18:04.817+07:00| vthread-4| I125: Setting header path for 4.9.6-1-ARCH to "/lib/modules/4.9.6-1-ARCH/build/include".
2017-02-04T11:18:04.817+07:00| vthread-4| I125: Validating path "/lib/modules/4.9.6-1-ARCH/build/include" for kernel release "4.9.6-1-ARCH".
2017-02-04T11:18:04.817+07:00| vthread-4| I125: Failed to find /lib/modules/4.9.6-1-ARCH/build/include/linux/version.h
2017-02-04T11:18:04.817+07:00| vthread-4| I125: /lib/modules/4.9.6-1-ARCH/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2017-02-04T11:18:04.817+07:00| vthread-4| I125: using /sbin/gcc for preprocess check
2017-02-04T11:18:04.829+07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.9.6-1-ARCH".
2017-02-04T11:18:04.829+07:00| vthread-4| I125: The header path "/lib/modules/4.9.6-1-ARCH/build/include" for the kernel "4.9.6-1-ARCH" is valid. Whoohoo!
2017-02-04T11:18:04.920+07:00| vthread-4| I125: found symbol version file /lib/modules/4.9.6-1-ARCH/build/Module.symvers
2017-02-04T11:18:04.920+07:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.9.6-1-ARCH/build/Module.symvers.
2017-02-04T11:18:04.943+07:00| vthread-4| I125: Read 19221 symbol versions
2017-02-04T11:18:04.943+07:00| vthread-4| I125: Reading in info for the vmmon module.
2017-02-04T11:18:04.943+07:00| vthread-4| I125: Reading in info for the vmnet module.
2017-02-04T11:18:04.943+07:00| vthread-4| I125: Reading in info for the vmblock module.
2017-02-04T11:18:04.943+07:00| vthread-4| I125: Reading in info for the vmci module.
2017-02-04T11:18:04.943+07:00| vthread-4| I125: Reading in info for the vsock module.
2017-02-04T11:18:04.943+07:00| vthread-4| I125: Setting vsock to depend on vmci.
2017-02-04T11:18:04.943+07:00| vthread-4| I125: Invoking modinfo on "vmmon".
2017-02-04T11:18:04.945+07:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.
2017-02-04T11:18:04.945+07:00| vthread-4| I125: Invoking modinfo on "vmnet".
2017-02-04T11:18:04.947+07:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.
2017-02-04T11:18:04.947+07:00| vthread-4| I125: Invoking modinfo on "vmblock".
2017-02-04T11:18:04.948+07:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.
2017-02-04T11:18:04.948+07:00| vthread-4| I125: Invoking modinfo on "vmci".
2017-02-04T11:18:04.950+07:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.
2017-02-04T11:18:04.950+07:00| vthread-4| I125: Invoking modinfo on "vsock".
2017-02-04T11:18:04.952+07:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.
2017-02-04T11:18:04.967+07:00| vthread-4| I125: to be installed: vmmon status: 0
2017-02-04T11:18:04.967+07:00| vthread-4| I125: to be installed: vmnet status: 0
2017-02-04T11:18:04.977+07:00| vthread-4| I125: Obtaining info using the running kernel.
2017-02-04T11:18:04.977+07:00| vthread-4| I125: Setting header path for 4.9.6-1-ARCH to "/lib/modules/4.9.6-1-ARCH/build/include".
2017-02-04T11:18:04.977+07:00| vthread-4| I125: Validating path "/lib/modules/4.9.6-1-ARCH/build/include" for kernel release "4.9.6-1-ARCH".
2017-02-04T11:18:04.977+07:00| vthread-4| I125: Failed to find /lib/modules/4.9.6-1-ARCH/build/include/linux/version.h
2017-02-04T11:18:04.977+07:00| vthread-4| I125: /lib/modules/4.9.6-1-ARCH/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2017-02-04T11:18:04.977+07:00| vthread-4| I125: using /sbin/gcc for preprocess check
2017-02-04T11:18:04.987+07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.9.6-1-ARCH".
2017-02-04T11:18:04.987+07:00| vthread-4| I125: The header path "/lib/modules/4.9.6-1-ARCH/build/include" for the kernel "4.9.6-1-ARCH" is valid. Whoohoo!
2017-02-04T11:18:05.078+07:00| vthread-4| I125: found symbol version file /lib/modules/4.9.6-1-ARCH/build/Module.symvers
2017-02-04T11:18:05.078+07:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.9.6-1-ARCH/build/Module.symvers.
2017-02-04T11:18:05.100+07:00| vthread-4| I125: Read 19221 symbol versions
2017-02-04T11:18:05.100+07:00| vthread-4| I125: Kernel header path retrieved from FileEntry: /lib/modules/4.9.6-1-ARCH/build/include
2017-02-04T11:18:05.100+07:00| vthread-4| I125: Update kernel header path to /lib/modules/4.9.6-1-ARCH/build/include
2017-02-04T11:18:05.100+07:00| vthread-4| I125: Validating path "/lib/modules/4.9.6-1-ARCH/build/include" for kernel release "4.9.6-1-ARCH".
2017-02-04T11:18:05.100+07:00| vthread-4| I125: Failed to find /lib/modules/4.9.6-1-ARCH/build/include/linux/version.h
2017-02-04T11:18:05.100+07:00| vthread-4| I125: /lib/modules/4.9.6-1-ARCH/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2017-02-04T11:18:05.100+07:00| vthread-4| I125: using /sbin/gcc for preprocess check
2017-02-04T11:18:05.110+07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.9.6-1-ARCH".
2017-02-04T11:18:05.110+07:00| vthread-4| I125: The header path "/lib/modules/4.9.6-1-ARCH/build/include" for the kernel "4.9.6-1-ARCH" is valid. Whoohoo!
2017-02-04T11:18:05.111+07:00| vthread-4| I125: Found compiler at "/sbin/gcc"
2017-02-04T11:18:05.116+07:00| vthread-4| I125: Got gcc version "6.3.1".
2017-02-04T11:18:05.116+07:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.
2017-02-04T11:18:05.117+07:00| vthread-4| I125: Using user supplied compiler "/sbin/gcc".
2017-02-04T11:18:05.122+07:00| vthread-4| I125: Got gcc version "6.3.1".
2017-02-04T11:18:05.122+07:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.
2017-02-04T11:18:05.123+07:00| vthread-4| I125: Trying to find a suitable PBM set for kernel "4.9.6-1-ARCH".
2017-02-04T11:18:05.123+07:00| vthread-4| I125: No matching PBM set was found for kernel "4.9.6-1-ARCH".
2017-02-04T11:18:05.123+07:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.
2017-02-04T11:18:05.123+07:00| vthread-4| I125: Validating path "/lib/modules/4.9.6-1-ARCH/build/include" for kernel release "4.9.6-1-ARCH".
2017-02-04T11:18:05.123+07:00| vthread-4| I125: Failed to find /lib/modules/4.9.6-1-ARCH/build/include/linux/version.h
2017-02-04T11:18:05.123+07:00| vthread-4| I125: /lib/modules/4.9.6-1-ARCH/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2017-02-04T11:18:05.123+07:00| vthread-4| I125: using /sbin/gcc for preprocess check
2017-02-04T11:18:05.133+07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.9.6-1-ARCH".
2017-02-04T11:18:05.133+07:00| vthread-4| I125: The header path "/lib/modules/4.9.6-1-ARCH/build/include" for the kernel "4.9.6-1-ARCH" is valid. Whoohoo!
2017-02-04T11:18:05.134+07:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.
2017-02-04T11:18:05.134+07:00| vthread-4| I125: Validating path "/lib/modules/4.9.6-1-ARCH/build/include" for kernel release "4.9.6-1-ARCH".
2017-02-04T11:18:05.134+07:00| vthread-4| I125: Failed to find /lib/modules/4.9.6-1-ARCH/build/include/linux/version.h
2017-02-04T11:18:05.134+07:00| vthread-4| I125: /lib/modules/4.9.6-1-ARCH/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2017-02-04T11:18:05.134+07:00| vthread-4| I125: using /sbin/gcc for preprocess check
2017-02-04T11:18:05.143+07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.9.6-1-ARCH".
2017-02-04T11:18:05.143+07:00| vthread-4| I125: The header path "/lib/modules/4.9.6-1-ARCH/build/include" for the kernel "4.9.6-1-ARCH" is valid. Whoohoo!
2017-02-04T11:18:05.143+07:00| vthread-4| I125: Using temp dir "/tmp".
2017-02-04T11:18:05.145+07:00| vthread-4| I125: Obtaining info using the running kernel.
2017-02-04T11:18:05.145+07:00| vthread-4| I125: Setting header path for 4.9.6-1-ARCH to "/lib/modules/4.9.6-1-ARCH/build/include".
2017-02-04T11:18:05.145+07:00| vthread-4| I125: Validating path "/lib/modules/4.9.6-1-ARCH/build/include" for kernel release "4.9.6-1-ARCH".
2017-02-04T11:18:05.145+07:00| vthread-4| I125: Failed to find /lib/modules/4.9.6-1-ARCH/build/include/linux/version.h
2017-02-04T11:18:05.145+07:00| vthread-4| I125: /lib/modules/4.9.6-1-ARCH/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2017-02-04T11:18:05.145+07:00| vthread-4| I125: using /sbin/gcc for preprocess check
2017-02-04T11:18:05.154+07:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.9.6-1-ARCH".
2017-02-04T11:18:05.154+07:00| vthread-4| I125: The header path "/lib/modules/4.9.6-1-ARCH/build/include" for the kernel "4.9.6-1-ARCH" is valid. Whoohoo!
2017-02-04T11:18:05.233+07:00| vthread-4| I125: found symbol version file /lib/modules/4.9.6-1-ARCH/build/Module.symvers
2017-02-04T11:18:05.233+07:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.9.6-1-ARCH/build/Module.symvers.
2017-02-04T11:18:05.255+07:00| vthread-4| I125: Read 19221 symbol versions
2017-02-04T11:18:05.255+07:00| vthread-4| I125: Invoking modinfo on "vmmon".
2017-02-04T11:18:05.257+07:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.
2017-02-04T11:18:05.257+07:00| vthread-4| I125: Invoking modinfo on "vmnet".
2017-02-04T11:18:05.259+07:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.
2017-02-04T11:18:05.641+07:00| vthread-4| I125: Setting destination path for vmmon to "/lib/modules/4.9.6-1-ARCH/misc/vmmon.ko".
2017-02-04T11:18:05.651+07:00| vthread-4| I125: Extracting the vmmon source from "/usr/lib/vmware/modules/source/vmmon.tar".
2017-02-04T11:18:05.734+07:00| vthread-4| I125: Successfully extracted the vmmon source.
2017-02-04T11:18:05.734+07:00| vthread-4| I125: Building module with command "/sbin/make -j2 -C /tmp/modconfig-adeoqk/vmmon-only auto-build HEADER_DIR=/lib/modules/4.9.6-1-ARCH/build/include CC=/sbin/gcc IS_GCC_3=no"
2017-02-04T11:18:12.720+07:00| vthread-4| W115: Failed to build vmmon. Failed to execute the build command.
2017-02-04T11:18:12.726+07:00| vthread-4| I125: Setting destination path for vmnet to "/lib/modules/4.9.6-1-ARCH/misc/vmnet.ko".
2017-02-04T11:18:12.726+07:00| vthread-4| I125: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar".
2017-02-04T11:18:12.766+07:00| vthread-4| I125: Successfully extracted the vmnet source.
2017-02-04T11:18:12.766+07:00| vthread-4| I125: Building module with command "/sbin/make -j2 -C /tmp/modconfig-adeoqk/vmnet-only auto-build HEADER_DIR=/lib/modules/4.9.6-1-ARCH/build/include CC=/sbin/gcc IS_GCC_3=no"
2017-02-04T11:18:16.840+07:00| vthread-4| W115: Failed to build vmnet. Failed to execute the build command.
I've just installed the latest version of the VMware Player in a Debian (Jessie) environment.
When I try to open an existing virtual machine (VMware) 2 errors occur:
(Before posting a question in this forum I looked for solutions using google and found several possible solutions.)
Could not open /dev/vmmon: No such file or directory.
Please make sure that the kernel module `vmmon' is loaded
Solution: mknod /dev/vmmon c 10 165 > /dev/null 2>&1
Too many virtual machines are running.
The maximum number of running virtual machines is 64.
(No other virtual machines are running ....)
Thank you in advance for any advice or suggestions.
Chameleon
VMware Player 12.5.1 on Windows 7 64 bit Host
Windows 7 64bit as guest (don't ask..... need to run all 'my' software separate to the work)
I have a USB Edimax 7811 USB dongle which I pass through to the guest to allow it network access (as work will not allow it to use the corporate network - it logs on to a 'public' wifi)
All works great. However when I resume the laptop (Dell e5470) the USB wifi in the guest is not working. It is listed in 'device manager' but does not get detected in 'Network Status and tasks'.
The only way to get it functioning again is to disconnect it from the Virtual Machine and then reconnect it..... then it works fine again. Also physically unplugging it and re-inserting also works.
Does anyone have any idea how to stop this from happening?
I also thought of automate running a command line program to disconnect and reconnect the USB device upon resuming the computer...... but none of the versions of VMware seem to support this from the command line.
I could leave the USB Wifi network in the host.... but every time I run the Cisco VPN it disables all other network traffic....
In the SECOND image, you can see at the top, I have a panic... I don't know why as this is my first attempt trying to install a VirtualMachine.
I used a youtube tutorial, and followed EVERY step (except the Processors I could only use 2)... Youtube Tutorial Link
And in the THIRD image, you can see that is says, "Mac OS version: Not yet set .... WHAT..?
It points to the file inside the folder... file name is: macOS 10.12 Sierra Final.vmdk
So why is it not recognizing it..?
Here is the vmware.log:fqrwstg3qredgvqewrdfgv3qr - Pastebin.com
And here is the macOS 10.12 Sierra Final.vmx:dcgbwtru57er7ytbg54wyh6r - Pastebin.com
Any and all help from those who might know how I can solve this please..? I really need to get MACOS on my Windows10 laptop for school...
It's cheaper than buying a MAC. Thanks.
Hi,
I am using VM ware workstation 12 player and i am installing an Ubuntu server as a guest OS.
When I start the VM i am getting the "Intel VT-X not found" message
My CPU is an Intel E6550 and it support VT-X virtualization.
I ve checked both the BIOS and VM setting that Intel VT-X is enabled.
Any idea please ?
Hi,
will there be a blackberry 10 app? If yes, when is the release planned?
Regards,
Benjamin