VMware Workstation Player 14 Crack + License
Janet Denzel
I've been using a local VMware workstation player VM for personal computing but I decided to switch over to Windows Hyper-V for speed and potentially GPU passthrough. I got Hyper-V running but I'm not able to connect to any VM I create in it. My VMware VM has also started having weird problems, though it still mostly works. I thought I'd just misconfigured Hyper-V somehow but none of the solutions online have worked or even seemed very applicable to my problems.
I read though that different hypervisors could conflict with each other and that VMware actually made you disable Hyper-V if you want to install it with Hyper-V active. It doesn't seem like Windows makes you do the same in the opposite direction though.
For GPU use in Windows applications, you do not need any hypervisor.
For GPU use in Linux applications, you could go for dual boot.
For hosting multiple windows and linux distros on the same laptop/workstation, use the type-2 hypervisor of your choice.
VMware Workstation offers many useful developer features e.g. snapshots, time sync to guest os, battery usage, etc. Workstation Pro 17.5 works flawlessly on Windows 11 Pro. The only "conflict" identified so far with WSL distributions concerns connecting/disconnecting USB peripherals (USB camera, USB network adapter, etc.) when concurrent access occurs.
I know there are other tutorials for VMWare Workstation Pro and the procedure is quite similar. Following on of these tutorials ( -tutorial-vmware-workstation-dsm-62-install-esxi-compatible) brought me very close to my goal but still I had to do some try and error, therefore I am sharing my piece of the cake here.
1. XPE will not recognize more than the SATA boot drive and 1 other SCSI disk. No matter what other port I choose for the SCSI disks, they are not visible in XPE. I think I recreated this VM about 20 times trying different configurations. I tried adding up to 12 drives in the initial creation of the VM, no luck. I tried with just the boot drive and adding data drives one by one, and all at once, after booting XPE, no luck. No matter what I do, it will only see one data drive. Other than that, I can create a volume and pool with that single drive, share it to my home network, and add packages with no problems.
2. XPE will reset whenever I reboot the VM. It boots right up, but goes to the initial menu of setting up a new Synology, including reinstalling DSM. All settings, drives are gone. I checked and the VM sees the boot drive as persistent, and the data drive is also listed as persistent. I can create and revert to a snapshot no problem, but weird that I cannot reboot the VM.
Well apparently now I can add/remove drives if I use SATA drives during a live VM session, so that is good. The system just will not see SCSI drives other than the first one. I still have the problem that the VM resets if rebooted. I will keep looking into it and post back.
I've tried sudo vmware-installer -u vmware-player before, but the app is still there. It can be seen in App Menu, and can EVEN be launched and used, but it is not listed in vmware-installer -l - it only shows VMWare Workstation PRO (i installed it right away after presumably uninstalling Workstation Player). I couldn't find any relevant folders in usr/bin as well. What can i do? I don't want to reinstall Ubuntu just for that.
Turns out Player is a vital component for Workstation - it is considered a component that can not be removed. That is utterly stupid, but what can i do. I deleted the shortcut from App Menu from /usr/share/applications/ and /usr/local/share/applications/, that's better than nothing, I guess.
bcf7231420