You're right to act as soon as it starts, but don't just hit a key. You have to mouse click to enter the VM, and then hit the key (F2 for BIOS or ESC for boot menu) F12 for network boot though I haven't used network boot.
When the virtual machine starts, the mouse cursor changes from an arrow to a hand cursor, but you are not in the virtual machine unless you click, and then the cursor will disappear. Then, it will respond to key presses.
You can also edit the vmx file of the virtual machine, and add the line bios.bootDelay = "15000" (15000 milliseconds is 15 seconds but you can change it to whatever) and you get another screen that offers the same keys and a 15 second delay to hit them. Of course, you have to click first. You might want to shorten it from 15 seconds. But if you've been missing it you might appreciate the screen being there for 15 seconds, then change it once you've figured out how to do it.
Another option is "power on to firmware", try it, it goes to the BIOS. It's in the menu when right clicking a VM, or in the VM menu at the top. And in some versions of vmware workstation it's "power on to BIOS". In my version it's "power on to firmware" but it goes to the BIOS
This adds a delay to the initial POST screen, showing it for longer and giving you more time to access the BIOS setup, where xxxx is the number of milliseconds to show the POST screen. (There are 1000 milliseconds in a second.) The maximum value for the boot delay is 10000 milliseconds or 10 seconds.
Multiple versions of the same packages.
Out of date packages.
Broken or only partially working packages.
Improperly configured packages which download unnecessary dependencies, or do not download necessary dependencies, or both.
Malicious packages (although extremely rare).
If you do do it manually try you will most likely run into library incompatibilities and you will need to compile the kernel modules by hand and this you will have to do it on every subsequent kernel update.
Due to my job and the professional aspect I have used licensed versions but I stopped at v12.5 - and I have not yet met any member on this forum who can clearly explain to me the benefits of VMware over VirtualBox.
here Best way to install vmware workstation - #12 by linux-aarhus
you told me to run sudo pacman -Syu linux511-headers without the dkms
should i do it now?
looking in pamac,i see i have dkms 2.8.4-1 installed;is it the same?
It is not support by Aruba officially but you can install it on vmware workstation. After installation, before powering up the VM, edit the VM and just add another hard drive with 80Gb or more capacity. You are good to go!
I imported the vmdk file to Workstation and then mounted the ISO to the machine. However, it keeps asking me the installation file. Can you ellaborate a little on what you mean by Importing the VM. I don't believe there's an option for that in Workstation. Not that proficient in it though.
Hello everyone,
I am so glad to be a part of this great community and project.
I recently installed vmware workstation via nix config file, it was successful, but when i launched it, it is not opening. I tried to launch from cmd and got the message in the attached screenshot. I was trying to follow some solution i saw but the vmware config files are read-only and i am not able to edit it. I will be so glad to receive help on this. Thank you.
vmware-error121976 11 KB
Thank you all, the above issue has been fixed. I got help from @NobbZ.
Apparently, using this link NixOS Search
I added the virtualisation.vmware.host.enable to my configuration.nix file and set it to true, then i rebuild. I hope this helps someone who might need it as well. Thank you.
Hello, I've read all available information I can find online about this problem. I have two Workstation Pro licenses, each on its own separate laptop with top of the line specs. Lots of processors, ram, storage.
But: on the newest laptop where I just installed workstation pro, I get extreme 'lag' on any of the Guest operating systems. The Host works very quickly.
By lag, I mean there is a lag between any mouse or keyboard input and the output. For example, when I type, the text is nearly a word slower than my typing. When I click on something, I don't see the operation executed for at least 1-2 seconds. It's basically unusable at this point.
From reading online and some tinkering, I think it has to do with resolution settings because when I changed the host's resolution settings as well as the guest's, I got an 80% improvement (host at 1920x1080, 100% and guest at 1718x948, 100%), the same as I have on my well functioning VMWare Workstation. But I'm just not quite there yet. The host isn't running anything else on it and I haven't installed anything besides Windows 10 on the guests, so basic operations like typing shouldn't be taxing it so much. On my functioning Workstation Pro I can run 20+ guests easily.
As far as I can tell all my settings match across PCs, so I'm completely baffled. But again I think it's something related to resolution because I have the appearance of lag but I don't think the PC is itself struggling with processing.
In fusion (not workstation) you can get to the config file directly by right-clicking on the VM while holding down the option key and selecting Open Configure file in Editor in the menu. In workstation I think it's control instead of option. Should work the same.
b1e95dc632