Creating a VMware virtual machine means defining a new workload shell on a host or cluster and assigning compute, memory, storage, network, and guest operating system settings to it. The short answer is this: choose the right parent object in vSphere Client, launch the New Virtual Machine workflow, define compute and datastore placement, select the guest OS, customize hardware, and add security devices such as vTPM when required. This guide is written for administrators working in the September 1, 2025 context.
Quick Summary
- Broadcom KB 313843 shows that a valid parent object for new VM creation can be an ESXi host or a cluster, and that the process begins through New Virtual Machine.
- The same KB shows that in the
Customize hardwarestep, you can set firmware to EFI under VM Options > Boot Options and then add a Trusted Platform Module device. - Broadcom KB 394956 states that Windows 11 requires TPM 2.0, and that vSphere must have a configured Key Provider before a vTPM-backed VM can be created successfully.
- Broadcom KB 313843 also highlights example Windows 11-related baseline requirements such as 4 GB memory and 64 GB storage.
- Broadcom KB 340172 explains that if the ESXi scratch location is incorrectly configured at the datastore root, new VM creation can fail with Invalid operation for device 'X'.
- In the September 1, 2025 context, Broadcom KB 326316 lists vCenter Server 8.0 Update 3g / 8.0.3.00600 / Build 24853646 as one visible current vCenter 8 baseline.
Table of Contents
- What Should Be Ready Before Creating a VM?
- Which vCenter Baseline Makes Sense for September 1, 2025?
- What Is the Logic Behind the New Virtual Machine Workflow?
- How to Create a VMware Virtual Machine Step by Step
- Most Common VM Creation Errors and Fixes
- First 15-Minute Checklist
- Frequently Asked Questions
Image: Wikimedia Commons - Global Switch Data Centre.
What Should Be Ready Before Creating a VM?
This guide is for teams provisioning a new application server, test machine, or business workload on vSphere. The wizard looks simple, but the operating system, security, and datastore prerequisites still need to be right before the first boot.
Before you begin, make sure these items are clear:
- which host or cluster will own the VM
- which datastore will store the virtual disks
- which guest OS will be installed
- how much CPU, memory, and storage should be assigned
- whether UEFI, Secure Boot, or vTPM is required
- which network and port group the VM NIC should use
In multi-site or branch-connected environments, naming and placement standards should be defined before the first VM is created so production and test workloads do not drift into the same placement model.
Which vCenter Baseline Makes Sense for September 1, 2025?
VM wizard behavior and compatibility should still be considered in the context of the managing vCenter version. According to the build table in Broadcom KB 326316, one visible vCenter 8 baseline in the September 1, 2025 context is:
- Product: vCenter Server 8.0 Update 3g
- Version: 8.0.3.00600
- Release date: 2025-07-29
- Build: 24853646
This guide uses vCenter Server 8.0 Update 3g / Build 24853646 as the management baseline.
What Is the Logic Behind the New Virtual Machine Workflow?
Broadcom KB 313843 shows the core structure of the workflow:
- choose a valid parent object in inventory
- start New Virtual Machine
- customize hardware and boot options during the wizard
The correct parent object matters because it shapes placement and resource behavior. A VM created from a cluster object will usually fit production standards better than a one-off host-only placement.
How to Create a VMware Virtual Machine Step by Step
1. Choose the Correct Parent Object
Broadcom KB 313843 explicitly shows that the parent object can be an ESXi host or a cluster. In most production environments, creating the VM from the cluster is the cleaner starting point because placement and scheduling are already cluster-aware.
2. Start the New Virtual Machine Wizard
Right-click the chosen inventory object and launch New Virtual Machine. At this point, the naming and placement logic should already be clear.
For a cleaner operating model, define:
- VM name
- workload type
- production or test classification
- owning team or service
3. Choose Guest OS and Hardware Deliberately
The guest OS choice affects compatibility and security behavior. CPU, RAM, and disk sizing should reflect the selected guest OS and the real workload.
For example, Broadcom KB 313843 uses Windows 11-related baseline requirements such as:
- 4 GB memory
- 64 GB storage
- UEFI and Secure Boot capability
- TPM 2.0 expectation
That means selecting the wrong guest OS or leaving hardware sizing incomplete often creates problems only after the installer boots.
4. Do Not Treat Datastore Selection as a Minor Detail
The target datastore must already be healthy and visible where the VM will run. If datastore readiness is wrong, disk creation or the first power-on flow can fail later.
For datastore planning, the related guide is:
5. Manage the Customize hardware Step Carefully
Broadcom KB 313843 explicitly shows that in Customize hardware, you can go to VM Options > Boot Options and set the firmware to EFI. This is important for modern guest operating systems and secure boot paths.
At this stage, confirm:
- vCPU count
- RAM size
- virtual disk capacity
- NIC placement
- boot firmware mode
6. Add vTPM for Windows 11 and Similar Guest OS Requirements
Broadcom KB 394956 states that Windows 11 requires TPM 2.0. In vSphere, that means the VM needs a vTPM device. The same KB clearly says that a Key Provider must be configured first.
Broadcom KB 313843 describes the vTPM-enabled creation flow like this:
- set firmware to EFI
- use Add New Device
- select Trusted Platform Module
If no Key Provider exists, seeing a Windows 11-related creation error is expected behavior rather than a bug.
7. Validate the Initial VM Settings After Creation
Once the wizard finishes, the job is not done. The first validation should confirm:
- the VM is on the correct datastore
- the NIC is attached to the correct network
- the boot firmware is what you intended
- vTPM is present when required
- the OS installation media is attached correctly
Broadcom KB 313843 notes that you can verify vTPM later under Edit Settings > Security Devices.
Most Common VM Creation Errors and Fixes
Windows 11 creation fails because of vTPM or Key Provider issues
According to Broadcom KB 394956, this is expected if the environment does not yet have a Key Provider. The fix is to deploy a native or external key provider first and then retry VM creation with vTPM.
Invalid operation for device 'X'
Broadcom KB 340172 explains that this can happen when the ESXi scratch location is configured at the root of the datastore. The fix is to move scratch into a subdirectory rather than using the datastore root directly.
The VM is created but boot behavior is wrong
The root causes are usually:
- wrong guest OS choice
- wrong firmware mode
- missing or wrong ISO attachment
- wrong NIC or VLAN mapping
This is especially common when a guest OS expects UEFI but the VM was left in the wrong boot mode.
First 15-Minute Checklist
- The VM was created under the correct host or cluster
- The datastore choice is correct
- The guest OS selection matches the intended workload
- CPU, RAM, and disk are sized appropriately
- EFI or Secure Boot requirements were reviewed
- vTPM was added if required
- The NIC is connected to the correct port group
- First power-on behavior matches expectations
Next Step with LeonX
After the VM is created, the right next step is to define template standards, backup behavior, monitoring agents, network segmentation, and OS hardening as one operating flow. That is how the VM becomes operable instead of just powered on.
Related pages:
- Hardware & Software Sales
- Managed Services
- Contact
- How to Create a VMware Datastore
- How to Add a VMware Host
- How to Install VMware vCenter
Frequently Asked Questions
Should a new VM be created from a host or from a cluster?
Both are technically valid. Broadcom KB 313843 shows that a host or cluster can be the parent object. In most production environments, cluster-based creation is the cleaner starting point.
Why does Windows 11 require vTPM in vSphere?
Because Broadcom KB 394956 states that Windows 11 requires TPM 2.0, and in vSphere that means using a virtual Trusted Platform Module.
Why is a Key Provider required before adding vTPM?
Because Broadcom KB 394956 explicitly says vTPM devices require the vSphere environment to be configured with a Key Provider first.
Why does Invalid operation for device 'X' appear during VM creation?
According to Broadcom KB 340172, this can happen when the ESXi scratch location is configured at the datastore root.
What should be checked first after the VM is created?
Datastore, NIC, boot firmware, and vTPM presence if required. Broadcom KB 313843 specifically points to Edit Settings > Security Devices for vTPM verification.
Conclusion
Creating a VMware virtual machine is not just clicking through a wizard. It requires the right parent object, the right guest OS, the right datastore, and the right security options. In the September 1, 2025 context, the safe approach is to work from a visible current vCenter baseline, resolve vTPM and Key Provider prerequisites before Windows 11-style guest creation, and validate hardware settings immediately after the VM is created.
If you need help defining VM templates, guest OS onboarding standards, or post-creation hardening flow, you can contact LeonX.
