I am seeing that shared VMs were lost in the new version. It is generally too soon to consider updating, since the release is too new and needs updates.
I am curious of the general opinion of this version when compared to 15.5.6 build-16341506. The latest Worksation 15 does everything perfectly right now and supports all operating systems I run. Other than losing features, what is the benefit of even considering an update?
Thanks.
Hello,
Workstation 14 on Windows 10 - All VMs have a red X. I just loaded Windows update:
Now none of my virtual machines will even load. Red X over each one.
Any one else see this?
Good morning, I have updated Workstation to version 16. Being a web programmer, I also run a local Web Server on my PC to test PHP pages.
Reading the Release Notes of this new version I noticed that the Shared VMs feature has been removed.
The problem lies in the vmware-hostd.exe process, which uses port 443, not allowing me to run XAMPP. I tried to look in VMware settings, but the ability to change port has been removed.
Try to fix it as fast as possible.
Thanks
One of the primary items I am looking for in virtualization software is to be able to run games in VM's. Up to now this has really been limited to just older games (DX9 basically as the 10.1 support in WS 15.5 was not complete when I tested and thus skipped WS15 for upgrade). I am hoping that there are others here that can share their experience with Workstation 16 and DX11 games. Any issues? Performance hits? What about higher resolutions (1k, 2k, 4k gaming)?
I know DX11 is still not the best (seems vmware is about 10+ years behind technology) but it's a far cry better than DX9.
I have just installed Vmware Workstation 14 for testing.
When I try to load (start) a guest I get the following message:
This host does not support
virtualizing real mode. The Intel
"VMX Unrestricted Guest" feature is
necessery to run this virtual machine
on an Intel Processor.
Module 'CPUIDEarly' power on failed.
Failed to start the virtual mashine.
I'm runing a ThinkPad W701 with i7 CPU and Nvidia Quadro FX2800M graphiccard.
OS is Linux Mageia 6 with kernel 4.9.50
What to do?
I guess this is due to a kernel upgrade, but the suggested solutions do not help, because I do not have a vmware-config.pl anyware, and vmware-modconfig --console --install-all segfaults itself.
Hello,
Edit:
I did install Valorant before having the problem.
So I have been trying to create virtual machine with VMware workstation 15 pro and was not able to power it on.
Here is the message I get when i use "power on this virtual machine":
This virtual machine failed to switch to 64 bit mode. This failure might be due to a lack of available memory on the host.
Module 'Monitor' power on failed.
Failed to start the virtual machine.
I am using:
- Ubuntu LTS 18.04 iso
My computer has:
- Windows 10 Education
- 16Gb RAM
- More than 100Gb of free space (hard disk)
- Motherboard: an asrock phantom
- CPU: amd ryzen 5 3600x
- Antivirus: Windows defender
I have tried:
- Rebooting
- Updating windows (normal updates)
- Keeping the default parameters while creating the vm
- Limiting the RAM to 250mb
- limiting the hard disk to 1Gb
- Checking that SVM and SMT are enabled for virtualization in the Bios
- Using VMware workstation Player 15, same issue
- Using virtualbox with the same configuration, it is working
- enabling/disablings Windows Hyper-V
- Disabling windows defender my firewalls
Here is my vmware.log file:
Here are the last lines if you do not wish to dl the entire file:
2020-04-19T19:23:13.805+02:00| vmx| I125: Host AMD-V Capabilities:
2020-04-19T19:23:13.805+02:00| vmx| I125: SVM Revision: 1
2020-04-19T19:23:13.805+02:00| vmx| I125: ASIDs Supported: 32768
2020-04-19T19:23:13.805+02:00| vmx| I125: Nested Paging: yes
2020-04-19T19:23:13.805+02:00| vmx| I125: SVM GMET: yes
2020-04-19T19:23:13.805+02:00| vmx| I125: LBR Virtualization: yes
2020-04-19T19:23:13.805+02:00| vmx| I125: SVM Lock: yes
2020-04-19T19:23:13.805+02:00| vmx| I125: NRIP Save: yes
2020-04-19T19:23:13.805+02:00| vmx| I125: TSC Rate MSR: yes
2020-04-19T19:23:13.805+02:00| vmx| I125: VMCB Clean Bits: yes
2020-04-19T19:23:13.805+02:00| vmx| I125: Flush by ASID: yes
2020-04-19T19:23:13.805+02:00| vmx| I125: Decode Assists: yes
2020-04-19T19:23:13.805+02:00| vmx| I125: Pause Filter: yes
2020-04-19T19:23:13.805+02:00| vmx| I125: Pause Filter Threshold: yes
2020-04-19T19:23:13.805+02:00| vmx| I125: Monitor_PowerOn: HostedVSMP skew tracking is disabled
2020-04-19T19:23:13.805+02:00| vmx| I125: Loaded crosspage: .crosspage. Size = 4096 bytes.
2020-04-19T19:23:13.805+02:00| vmx| I125: vmm64-modules: [vmm.vmm64, vmce-vmce.vmm64, viommu-none.vmm64, vprobe-none.vmm64, hv-svm.vmm64, gphys-npt.vmm64, callstack-none.vmm64, swstats-none.vmm64, gi-none.vmm64, gmm-none.vmm64, ahci-ahci.vmm64, !ahciRegs=0x0, !ahciShared=0x1000, !e1000Shared=0x1c00, !vmSamples=0x2480, !theIOSpace=0x24c0, !ttGPPerVcpu=0x8800, {UseUnwind}=0x0, numVCPUsAsAddr=0x1, {SharedAreaReservations}=0x8840, {rodataSize}=0x20915, {textAddr}=0xfffffffffc000000, {textSize}=0x8b65e, <MonSrcFile>]
2020-04-19T19:23:13.805+02:00| vmx| I125: vmm64-vcpus: 1
2020-04-19T19:23:13.818+02:00| vmx| I125: Module 'Monitor' power on failed.
2020-04-19T19:23:13.818+02:00| vmx| I125: VMX_PowerOn: ModuleTable_PowerOn = 0
2020-04-19T19:23:13.818+02:00| vmx| I125: Vix: [mainDispatch.c:1163]: VMAutomationPowerOff: Powering off.
2020-04-19T19:23:13.819+02:00| vmx| I125: Win32U_GetFileAttributes: GetFileAttributesExW("C:\Users\X\Documents\Virtual Machines\Ubuntu 64-bit\Ubuntu 64-bit.vmpl", ...) failed, error: 2
2020-04-19T19:23:13.819+02:00| vmx| I125: Policy_SavePolicyFile: invalid arguments to function.
2020-04-19T19:23:13.819+02:00| vmx| I125: PolicyVMX_Exit: Could not write out policies: 15.
2020-04-19T19:23:13.819+02:00| vmx| I125: WORKER: asyncOps=0 maxActiveOps=0 maxPending=0 maxCompleted=0
2020-04-19T19:23:13.819+02:00| WinNotifyThread| I125: WinNotify thread exiting
2020-04-19T19:23:13.822+02:00| vmx| I125: Vix: [mainDispatch.c:4215]: VMAutomation_ReportPowerOpFinished: statevar=1, newAppState=1873, success=1 additionalError=0
2020-04-19T19:23:13.822+02:00| vmx| I125:
2020-04-19T19:23:13.822+02:00| vmx| I125+ Power on failure messages: This virtual machine failed to switch to 64 bit mode. This failure might be due to a lack of available memory on the host.
2020-04-19T19:23:13.822+02:00| vmx| I125+ Module 'Monitor' power on failed.
2020-04-19T19:23:13.822+02:00| vmx| I125+ Failed to start the virtual machine.
I cannot seem to find any related issues or solutions that fits my problem.
Thank you in advance for any help provided.
when reinstalled Windows 10 2004 due to problems with updates
C:/ SSD System disk
D:/ Data Disk // same as F:/ before reinstalled - untouched
Before Reinstall I created VM from PC with Star Wind V2V Converter but only C:/ disk 0 did as VM
This I want is while running this VM in Workstation 15.x - latest as of today
Insert a USB stick and this seen by VM as F:/ disk
How in other words
USB stick seen by VM Win 10 Pro
and how seen as letter F:/ ...? i have to change from Disk management?
Hello,
I have a Windows 10 x64 virtual machine to test USB booting. So the first disk is a physical USB disk (disk 2).
Just after Windows boot, I plug the USB disk and I am able to boot the virtual machine.
But after a while (maybe one day), I can no longer boot it, a error message pop ups: "Physical disk is already in use".
What is strange is that I can unplug correctly the USB disk from Windows, and even replug it, but VMware refuses to boot the virtual machine.
My understanding is that when there are programs using the disk, Windows won't let you unplug the USB disk.
So in my case, no programs are still using the disk, so why VMware workstation still says "Physical disk is already in use" ?
I run Debian testing on most of my systems. I recently upgraded my laptop to the latest patches including Linux Kernel 5.8.0.1. This broke VMware player 15.5.6 (run workstation pro on my main machine). I've been waiting for VMWare 16 since. Now that it's out it won't compile the kernel modules citing it can't find a compatible gcc, but gives a null on which one it is looking for. I know player/workstation is only designed to work with Debian 10, but I'm more than happy to find a workaround assuming I can figure out what it needs.
I have been using VMWare for years, and I have noticed a huge degradation in performance recently.
I run an operating system called SCO Unix Openserver inside of VMWare Workstation and recently noticed that the amount of time it takes to boot the guest OS has increased dramatically.
In the past the boot prompt for the OS would appear almost instantly after starting the guest OS, but is now taking many minutes to get to the boot prompt, and after initiating the boot sequence, the OS takes many more minutes to boot.
Once it boots, it runs as fast as it every did.
The system uses the blc scsi driver. The amount of RAM is very modest, just 768 MB. It runs with one processor / one core. I have tried disabling 3D graphics acceleration, but that had not effect.
This behaviour is noticeable on two different Dell laptops. I tried using vmware player on one of the laptops but the behaviour is the same.
Other guest OSes, such as Ubuntu, centos, etc. all boot normally.
I installed VMWare player on another computer, also a windows 10 computer, and after copying the VM from the laptops to the new computer, vmware player was able to boot the guest os quickly.
So, something in the how vmware workstation is configured or how Windows is configured is resulting in this new slow behaviour, but I don't know where to start looking.
Can someone suggest how to troubleshoot this?
I have a lab that I have been working on for the passed couple days and when I went to add a new NIC I seen all the default vmnet networks were gone. Does anyone know why this happened? I am using the free version. I've tried reinstalling multiple times but haven't had any luck.
Hello all, we have CentOS host by windows 2019 with NIC teaming, but found network isolated. Please kindly advise what should we need to do.
The workstation pro is 15.6 & windows 2019 are most updated. Anything i'm missing?
Thank you very much,
Jonathan Ng
Hello, I'm getting a new laptop with the following specs below:
10th Generation Intel® Core™ i7-10710U Processor (12MB Cache, up to 4.7 GHz, 6 cores)
16 GB, LPDDR3, 2133 MHz, Integrated
512 GB M.2 PCIe NVMe Solid-State Drive
Trying to see if this is sufficient to run VMWare Workstation 16 Pro with Windows 10 Pro in it. I use the VM to connect to customer network to do work and use the main laptop OS (Windows 10 Home) for emails and internet surfing. From what I understand, VMWare Workstation doesn't utilize the the turbo boost capability and from what I could find online it says the processor type I have starts at 1.1Ghz which I think is below the minimum requirements for VMWare Workstation 16 Pro. However, not sure if having the multi-core will compensate for this.
Would like to know if this laptop spec is under-spec'd for what I need to run VMWare or not. Any feedback would be greatly appreciated! TIA
Environment:
Application: VMWare Workstation Pro 16
Host: Windows 10 x64 (19041.508)
Guest: Windows 7 x64
Problem:
When installing VMWare tools this error is displayed and "Shared Folders" do not work.
"Setup failed to install the VSock Virtual Machine Communication Interface Sockets driver automatically. This driver will have to be installed manually."
Notes:
- The problem did not exist with VMWare Workstation Pro 15.5.6
- The problem does not exist with Windows 10 x64 guest
- The problem does not exist when installing VMWare tools extracted from VMWare Workstation Pro 15.5.6 on Windows 7 x64 virtual machine created in VMWare Workstation Pro 16
I am trying to get the latest Intel driver package installed on a Win10 VM to do some testing with the VLAN feature. However, the installer reports that there is no Intel NIC installed, despite it the vNIC being identified as an 82574L. Anyone know of a workaround?
When attempting to install Pro Workstation version 15.5 or 16.0, I get an error on a week old Win10/64 Pro system: An error occurred while attempting to create the directory "C:\programdata\Microsoft\Windows\Start Menu\Programs\VMware"
Ran the installer using "run as administrator" but got he same result.
The permissions for my login and Administrators allow full control of that directory. I even created the directory and still get the same error.
What's happening?
Thank you!
mp
I am using VMware® Workstation 15 Pro and everytime I try to use it I always get this error msg. : VMware Workstation and Device/Credential Guard are not compatible. VMware Workstation can be run after disabling Device/Credential Guard......." Can someomne please help me with this?
Licenses tracker shows WS 15 pro license as not upgradeable. We were able to upgrade for 14 to 15 but upgrading to version 16 is not available in upgrade tool?
Let's say that I have a USB device, and a guest OS. I can connect the USB device and connect it to the guest OS. But if the guest OS is shut down for whatever reason, the USB device is automatically redirected to the host OS, and the host OS connects the device to itself and does its things.
My question is, is it possible to prevent that and designate specific USB devices to be available only to a certain guest OS, never the host, even if the guest OS is not running. If the device is something that requires a driver to run, I could simply not install the driver on the host OS so that it would not recognise the device. But there are many USB devices that the host OS can recognise with in-built drivers, or automatically install drivers for from the Internet, so that method is not helpful.