- Vmware workstation player 12 vs 14 full size#
- Vmware workstation player 12 vs 14 update#
- Vmware workstation player 12 vs 14 license#
- Vmware workstation player 12 vs 14 windows#
VMware vSphere is very stable and very scalable. The command-line tools integrate well with Microsoft products, so it’s easy to manipulate them. VMware vSphere is very good with memory sharing between VMs and CPU scheduling between VMs.
VMware vSphere is very good from a recoverability point of view everything can be stored much easier on a virtual server than a physical one. Visio stencil for technical documentation would be a nice improvement. There is a lot of resource consumption and the overall performance could be a bit more effective. VM Workstation can be a bit clunky, though. This solution is also great at creating labs for our team when working on certifications. VM Workstation can also give us an idea of the issues we can anticipate and how best to address them. We like VM Workstation primarily to test environments to determine how well a solution will work before we put it into production.
Vmware workstation player 12 vs 14 windows#
VM Workstation’s setup is so easy, you can use it almost instantly, it works well with Windows and Linux.
Vmware workstation player 12 vs 14 update#
The upgrades could be set in an automated way so that the newer features don't require you to manually update, or you get an option to update automatically.
Vmware workstation player 12 vs 14 license#
So if you give us the license for free, we would be thrilled." "An improvement could be in terms of keeping up with the upgrades.
It would be better to integrate it into one solution, especially for small business companies." "The initial setup is quite complex." "It would be useful to have features like micro-segmentation, changing the mix as well as part of vSphere" "Here in Egypt, we would like everything free. I don't fully understand why this is the case." "They have multiple components required for the setup. It would be great to have the flexibility." "Sometimes you can't find items and you need to log onto different physical servers to do technical tasks. At present, a fluid pool is not available to us. It is very expensive as compared to other solutions." "It could be more composable. So I am going to use the non-UEK 3.10 kernel where resizing works fine."Its cost needs to be improved. support for KMS), or there is some misconfiguration (whose patching or repair is beyond my skills). In my opinion, either the UEK 4.1 kernel does not contain some features required by VMware Tools (e.g. I am not experienced in Linux much, so I cannot dig deeper.
Vmware workstation player 12 vs 14 full size#
In this case the "Resolution" combobox in "System -> Control Center -> Displays" contains resolutions up to 2560x1600 and the display is able to resize to the full size of my monitor (1900x1200). Plugin 'resolutionKMS' initialized.Īnd the 'resolutionKMS' plugin starts and then resizing works fine. resolutionCheckForKMS: System support available for resolutionKMS. When running the non-UEK kernel, the log contains the following lines: Maximizing the VMware Player's host window (to 1900x1200) exceeds this resolution and the guest display is not resized as a consequence. Then the "Resolution" combobox in "System -> Control Center -> Displays" contains resolutions up to 1380x768 only and then resizing works in limited fashion (up to such resolution). resolutionCheckForKMS: No system support for resolutionKMS.Īnd the VMware's resolutionKMS plugin does not start.
When running the UEK 4.1 kernel, the following is added to /var/log/vmware-vmsvc.log: Unfortunately, this did not solve the problem either. I tried with this option on or off, but there was no difference in behavior.Īt the end I upgraded my VMware Workstation Player from version 12.5.9 to the latest version 14.1.1 (which comes with a new version of VMware Tools - 10.2.0). My VMware Tools are configured with "Automatic kernel modules = " (AFAIK this means that the necessary VMware modules will be compiled and added automatically at boot time if they are missing in the corresponding kernel). the problem continued to happen when running the UEK kernel). Unfortunately, this did not change anything (i.e. I installed and configured VMware Tools in a session running under the UEK kernel. one and same modules appeared in the output of the command). There was no difference between outputs with UEK and non-UEK kernel (e.g. I compared the kernel modules with the lsmod command as you suggested: However, maximizing the host window resizes the guest display properly when running the non-UEK kernel. It works when manually resizing the VMware Player's host window but it DOES NOT work when the host window gets maximized (then the guest display does not get resized). I found that resizing DOES work in fact with the UEK 4.1 kernel.