For a new VMware desktop lab, evaluate a current supported Workstation Pro release for a Windows or Linux host, or Fusion for a supported Mac. Check the guest image’s CPU architecture before choosing. The old Player-versus-paid-Pro price comparison is no longer a useful starting point.
This is a documentation-based selection guide for authorized training environments. It reports no personal lab results, performance benchmark or exam-readiness guarantee. Licensing and technical sources checked: October 16, 2026. Exact support depends on the product release and host/guest combination.
Start with the image and exercise
Record the image architecture, virtual hardware, required services and concurrent guests. A small Linux target and a directory-services scenario have different needs. Choose a compatible platform before planning performance adjustments. A working installation is only the beginning of validating a lab.
1. Match the product to the host
| Situation | Evaluate | Check first |
|---|---|---|
| Windows or Linux | Workstation Pro | Host OS, CPU and guest support. |
| Mac | Fusion | Intel versus Apple Silicon and guest architecture. |
| Older Player instructions | Current Pro downloads | Backup and migration requirements. |
| Apple Silicon with x86-only target | Compatible x86 host or separately assessed emulation | Fusion does not convert x86 guests into Arm guests. |
Broadcom’s Workstation installation guide links host requirements and release documentation. The VMware Packer plugin maintainer’s January 2026 update identifies Player as having reached end of availability. Keep legacy product instructions separate from the current choice.
2. Separate free use from support and other costs
Broadcom announced free Workstation Pro and Fusion Pro use for commercial, educational and personal users on November 11, 2024. Its download and licensing guidance identifies Workstation Pro 17.5.2 and Fusion 13.5.2 onward for that option, without a license key. These historical versions establish eligibility, not the recommended current installation.
The official announcement distinguishes free online resources from support under an active contract. Free use does not automatically include troubleshooting tickets. Follow applicable terms and organizational rules. Guest OS and application licenses remain separate; include hardware, backup storage and maintenance in your budget.
3. Plan memory from the concurrent workload
The old uniform per-VM estimator is removed. Record each guest’s purpose, application requirements, allocated memory and observed pressure under the intended task. Reserve room for host applications. No equal split or fixed reserve percentage proves that a guest has enough memory.
Hypothetical example: 16 GiB available − 6 GiB reserved for host tasks − 4 GiB for a practice guest − 4 GiB for a target = 2 GiB unassigned. These are arbitrary planning inputs, not official guest requirements or measured consumption. Check actual usable memory and peaks before deciding whether the workload fits.
When performance is poor, observe memory pressure, CPU contention, storage activity and guest responsiveness. Change one justified setting and compare the same task. More vCPUs, more guest RAM or a new disk cannot be assumed to fix an unidentified bottleneck.
4. Verify the network rather than its label
Broadcom’s hosted-product network reference describes Bridged as attaching guests to the host’s LAN, Host-Only as a private network including the host and attached guests, and NAT as outbound access using the host’s address. Guests on the same VMware NAT network can communicate. Do not apply VirtualBox’s separate per-VM NAT assumption to VMware.
NAT is not complete isolation; Host-Only does not remove the host from the segment. Record every adapter, virtual network, forwarding rule and permitted path. Keep vulnerable targets off household and workplace networks. A second adapter can change the boundary. Verify intended allowed and denied paths using approved benign tests before active exercises.
The related network-mode guide explains connectivity questions across a lab. Its VirtualBox controls are not VMware configuration instructions; follow the documentation for the actual product.
5. Keep rollback and independent recovery separate
The Fusion snapshot explanation describes dependency on the original disk. A snapshot is a rollback point, not an independent backup. Preserve the files needed for the complete guest and record external disk or clone dependencies.
Broadcom’s Workstation backup guidance describes copying the VM folder while the guest is powered off, not running or suspended. Check release-specific instructions and your storage arrangement. Test a restored disposable copy in a controlled network before replacing a known usable backup.
Label rollback points by purpose and date. Review capacity and dependencies before removal and use supported product operations rather than deleting snapshot files. A rollback of one guest does not prove that a related multi-VM service is consistent.
6. Check architecture and host hypervisor conditions
Broadcom’s Apple Silicon compatibility guidance states that Fusion runs 64-bit Arm guests there, not x86 operating systems. An Arm guest running some x86 user applications is a separate capability. Copying an x86 lab image from another computer does not make it bootable as an Arm guest.
The Workstation Hyper-V/VBS article explains Windows Hypervisor Platform use when the required host conditions are met. Record the exact host build, hardware, Workstation release and needed guest features. Ordinary guest operation and nested virtualization are different questions. Do not disable host security protections as a routine performance adjustment.
7. Limit guest access to host resources
Review shared folders, clipboard integration, drag-and-drop, USB passthrough and management access for the exercise. Keep personal data and reusable credentials out of lab images. Maintain the host and supported software, and stop if testing leaves the authorized targets. Snapshots do not undo disclosure of host data.
Save a decision and acceptance record
Host OS / build / CPU architecture:
Product / release / compatibility evidence:
Guest architecture and required services:
Concurrent guests and memory assumptions:
All adapters / networks / forwarding review:
Allowed and denied path checks:
Host integrations and data exposure:
Rollback point and disk dependencies:
Independent backup / restore test result:
Unresolved requirements and next action:Use a short planning session to identify missing information, not certify an exam-ready lab. Preserve a working backup before software or virtual-hardware changes. If a dedicated host better fits the scenario, the Proxmox planning guide covers the added management and recovery work.
Questions that change the choice
Does paid pentesting require a paid Pro license? The current free-use policy includes commercial use. Check applicable terms and support arrangements separately. It does not license guest software or authorize testing unrelated systems.
Must every host use one hypervisor forever? Choose tools by verified requirements and test compatibility before switching. This guide supplies no benchmark for a universal winner and no evidence that multiple installed products always conflict.