I found a workaround. Context: (I also have this problem, running Worstation 17 Pro on ArchLinux, so this is not happening only when host is Windows) When installing an Ubuntu system from creating...
See more...
I found a workaround. Context: (I also have this problem, running Worstation 17 Pro on ArchLinux, so this is not happening only when host is Windows) When installing an Ubuntu system from creating a VM (not duplicating one), Workstation auto-detects it and automatically sets up the Guest OS to "Linux" and Version to "Ubuntu 64-bits". Action: I changed that detected Version, and manually set it "Other Linux 6.x kernel 64-bit", then continue the installation. Result: Nothing no longer freeze. PS: how to send that information to VMWare devs?
AFAIK, VMWare workstation is known to work well with a set of supported Linux distribution https://kb.vmware.com/s/article/80807 VMware engineers will fix for those
@agun76, dont copy individual files from https://github.com/mkubecek/vmware-host-modules Clone the repo, checkout the right branch and pull, then "make ; sudo make install".
I reainstalled my OS and then had to reinstall Workstation BTW: when prompted to enter the licence, I get a "Invalid licence". Note that the first time I installed 17 it accepted my licence! But thi...
See more...
I reainstalled my OS and then had to reinstall Workstation BTW: when prompted to enter the licence, I get a "Invalid licence". Note that the first time I installed 17 it accepted my licence! But this second time, it refuses!
I want to raise a ticket to the support, but before that, I have to register my Workstation 17 Pro License Key with the message: Unsuccessful Registration The following key(s) were not registered ...
See more...
I want to raise a ticket to the support, but before that, I have to register my Workstation 17 Pro License Key with the message: Unsuccessful Registration The following key(s) were not registered due to errors. Please correct them or click the Skip Invalid Keys button to bypass their registration. My Workstation 17 Pro is correctly installed on my system and when I entered my Licence, is has been accepted by the Workstation 17 Pro Where is the link to inquire about that?
Hi all, Running workstation 17 on Archlinux with kernel 5.15.79 (LTS) When launching an existing VM: Could not connect 'Ethernet0' to virtual network '/dev/vmnet8'. More information can be found...
See more...
Hi all, Running workstation 17 on Archlinux with kernel 5.15.79 (LTS) When launching an existing VM: Could not connect 'Ethernet0' to virtual network '/dev/vmnet8'. More information can be found in the vmware.log file. Failed to connect virtual device 'Ethernet0'. When I go to the "network settings" and remove then create '/dev/vmnet8', things go right... Nothing about "vmnet" in the logs when greping "vmnet"
Hi all, When I launch Workstation and check updates, Workstation tells me 16.2.4 is available. But when I go to https://www.vmware.com/products/workstation-pro/workstation-pro-evaluation.html it st...
See more...
Hi all, When I launch Workstation and check updates, Workstation tells me 16.2.4 is available. But when I go to https://www.vmware.com/products/workstation-pro/workstation-pro-evaluation.html it still issues 16.2.3
Hi all, I expect to get an i9 Alder Lake machine, running Linux, and I wonder how will Workstation behave with those Performance-cores (or P-cores) and Efficient-cores (or E-cores). My usage is mos...
See more...
Hi all, I expect to get an i9 Alder Lake machine, running Linux, and I wonder how will Workstation behave with those Performance-cores (or P-cores) and Efficient-cores (or E-cores). My usage is mostly running at least 4 VMs and I set VMWare workstation to give priority to the VM having focus. Will VMware Workstation switch the focused VM to the P-core, and move it back to an E-Core when loosing focus? Cf. https://docs.vmware.com/en/VMware-Workstation-Pro/16.0/com.vmware.ws.using.doc/GUID-5B898B52-34BF-45C7-B107-65BD5315E97F.html
6 years later... My setup has evolved and I made some search in order to see if there are more ways to tune it. My current setting is now: https://mihamina.rktmb.org/2021/04/vmware-workstation-t...
See more...
6 years later... My setup has evolved and I made some search in order to see if there are more ways to tune it. My current setting is now: https://mihamina.rktmb.org/2021/04/vmware-workstation-tunning.html mainmem.backing = "unnamed"
sched.mem.pshare.enable = "FALSE"
mainMem.useNamedFile = "FALSE"
prefvmx.minVmMemPct = "100"
prefvmx.useRecommendedLockedMemSize = "TRUE"
mainMem.partialLazySave = "FALSE"
mainMem.partialLazyRestore = "FALSE"
priority.grabbed = "high"
priority.ungrabbed = "normal"
Hi all, I host 3 Linux (Archlinux) guests on a Linux (Archlinux, from kernels arround 5.8 to current 5.11) host. Guests have open-vm-tools installed. Host has a nVidia card, and dirvers are instal...
See more...
Hi all, I host 3 Linux (Archlinux) guests on a Linux (Archlinux, from kernels arround 5.8 to current 5.11) host. Guests have open-vm-tools installed. Host has a nVidia card, and dirvers are installed. When I plug my 4K screen and open the guest window to the maximum, it really eats much CPU... Would you know a tip or trick in order to make it use less CPU?
Hi all, Product: VMware Workstation 14 Pro 14.1.1 build-7528167 OS: ArchLinux 4.15.12-1-ARCH I just upgraded my system and the kernel was upgraded to 4.15.12 I ran vmware-modconfig --cons...
See more...
Hi all, Product: VMware Workstation 14 Pro 14.1.1 build-7528167 OS: ArchLinux 4.15.12-1-ARCH I just upgraded my system and the kernel was upgraded to 4.15.12 I ran vmware-modconfig --console --install-all" as usual and got error: "Unable to install all modules. See log for details." Getting into the logs, I found: 2018-03-26T08:38:25.803+03:00| modconfig| W115: Failed to install vmmon to /lib/modules/4.15.12-1-ARCH/misc/vmmon.ko. 2018-03-26T08:38:28.030+03:00| modconfig| W115: Failed to install vmnet to /lib/modules/4.15.12-1-ARCH/misc/vmnet.ko. I then tried to launch VMware Workstation GUI, and obvously got the prompt to compile modules. I let it compile and there was no errors, and the GUI launched without problems. My conclusion is: the GUI doenst directly call "vmware-modconfig" and there is a difference in the behaviour of what is called by the GUI and "vmware-modconfig"
