VMware ESXi and vSphere Cluster Management

Configure Virtual Machine Options in VMware vSphere

Learn how to open Edit Settings, use the VM Options tab, configure guest OS, Tools, boot, logging, swap, NPIV, and validate changes in vSphere.

The VM Options tab contains virtual-machine-level settings that are separate from virtual hardware settings such as CPUs, memory, disks, and network adapters. You access these options for an existing virtual machine through Edit Settings in the vSphere Web Client.

The exact sections and controls can differ according to the vSphere version, VM hardware compatibility version, configured guest operating system, licensing, ESXi host capabilities, storage configuration, VM power state, and your permissions. If an option described here is not visible, check those dependencies before assuming that the feature is unavailable.

Open the VM Options tab

Sign in to the vSphere Web Client with an account that has sufficient permission to view and modify the target VM.
Locate the VM in the inventory and select it.
Open the Edit Settings action. Depending on the client layout, this action may be available from the VM's Actions menu or a context menu.
Select the VM Options tab.
Expand the applicable sections, review the current values, and modify only the settings required for the change.
Apply or save the configuration. If the client warns that a power-off, reboot, or other interruption is required, follow the warning and schedule the change appropriately.

Use the virtual hardware area of the same dialog for devices such as virtual disks, network adapters, memory, and CPUs. Use VM Options for VM identity, guest OS behavior, boot and firmware controls, Tools behavior, logging, swap placement, and other platform-level options.

VM Options categories

VM Options category	What it controls	Typical use case	Potential operational impact
General options and VM naming	Display identity and general VM configuration.	Rename a VM for inventory clarity.	The inventory name changes, but datastore files may retain their existing names.
Guest operating system settings	Guest OS family and version presented to the virtualization platform.	Correct an incorrect OS selection after a migration or conversion.	Defaults and guest integration behavior can change.
VMware Remote Console	Controls or exposes console connection behavior where supported.	Permit or restrict direct console access.	Console access affects administrative security and troubleshooting procedures.
VMware Tools	Tools lifecycle and upgrade-related behavior.	Coordinate Tools maintenance with guest updates.	Installation actions or reboots may be required.
Power management	Available VM power and guest shutdown behavior.	Review automation before maintenance.	Unexpected shutdown or startup behavior can affect workloads.
Boot options	Firmware startup behavior, delay, setup entry, and boot-device considerations.	Boot from installation media or enter firmware setup.	A wrong firmware or boot order can prevent startup.
Logging, debugging, and statistics	Diagnostic output and advanced statistics collection.	Investigate a fault with approved diagnostic settings.	Additional files can consume datastore space and affect performance.
Swap file location	Datastore placement of the VM swap file.	Place swap on an approved datastore with suitable capacity and performance.	Placement affects capacity, latency, and VM power-on availability.
Fibre Channel NPIV	Virtual Fibre Channel identities for supported VMs.	Present SAN storage using VM-specific virtual identities.	Requires coordinated fabric, HBA, zoning, and storage administration.

VM identity and guest operating system settings

VM display name

The virtual machine name is the display name shown in the vSphere inventory. It helps administrators identify the workload, environment, or owner. Change it under the general VM options area, save the configuration, and verify that the inventory reflects the new name.

The display name is different from the VM directory. A VM directory is the datastore folder containing the VM configuration, virtual disks, logs, and other associated files. Changing the inventory name does not automatically rename that directory or the existing VM files. File-level renaming or migration is a separate operation that should be planned carefully because references, backups, replication, and storage procedures may depend on those files.

Guest operating system type

Configure or verify the guest operating system family and version. This selection helps vSphere choose suitable defaults and supports VMware Tools integration and other guest-specific behavior. It does not install an operating system and does not replace the operating system actually running inside the VM.

Correct the selection after an operating system migration or when a VM was created with an incorrect type. Validate application behavior and VMware Tools status after changing it, particularly for production systems.

VMware Remote Console options

VMware Remote Console provides direct interaction with a VM's display, keyboard, and pointer. Where the environment exposes console configuration controls, review whether remote console connections are enabled or restricted and apply the organization's administrative access policy.

Console access can bypass normal in-guest remote administration paths, so treat it as privileged access. Use least-privilege permissions, limit access to authorized administrators, and consider the effect of console restrictions on emergency recovery and troubleshooting.

VMware Tools settings

VMware Tools is a set of guest utilities and drivers that improves integration between the guest operating system and vSphere. Depending on the platform version and VM state, VM Options may expose Tools upgrade or lifecycle behavior.

Review the available Tools upgrade setting before enabling automatic or scheduled behavior.
Coordinate the change with guest operating system patching and application maintenance.
Determine whether the selected action installs software, restarts guest services, or requires a guest reboot.
After the guest returns to service, check Tools status in vSphere and, when appropriate, inside the guest.

A Tools setting may not appear to take effect immediately because the guest-side installation or reboot has not occurred. Do not force a reboot on a production workload outside an approved maintenance window.

Power management settings

Power-management options control behavior available for powering on, powering off, suspending, resetting, or requesting a guest shutdown. The specific controls depend on the client and platform version.

Review these settings before maintenance, automation changes, backup operations, or host remediation. A guest shutdown request may depend on VMware Tools and guest permissions, while a forced power operation can interrupt applications and risk data loss. Confirm the intended behavior with the workload owner.

Boot options and firmware behavior

Boot options control VM startup behavior where supported. Common controls include a startup delay and forcing entry to firmware setup on the next boot. Firmware type, secure boot, and related controls depend on VM compatibility and guest OS requirements.

Boot delay: Adds time before startup proceeds, allowing an administrator to select a device or enter firmware controls.
Force firmware setup: Sends the next startup to the virtual firmware interface when the option is available.
Boot order: Determines which virtual disk, CD/DVD device, network device, or other supported device the VM attempts first.
Firmware compatibility: Confirm that BIOS or UEFI and secure boot choices match the installed guest OS and VM compatibility level.

The boot option alone does not necessarily provide installation media. Configure and connect the appropriate virtual CD/DVD device or other installation source in the virtual hardware settings, then restart the VM during an approved maintenance window.

Example: boot from installation media

Open the VM's Edit Settings dialog and select VM Options.
Expand Boot Options and configure a suitable boot delay or next-boot firmware setup entry.
Configure and connect the installation media through the appropriate virtual hardware device if necessary.
Save the configuration and restart the VM during the approved window.
Confirm that the VM uses the intended boot device. If it does not, review firmware mode, device connection, and boot order.

Logging, debugging, and statistics

VM logging records information that can help diagnose startup, device, and runtime problems or support a vendor investigation. Debugging and statistics controls are advanced settings and should be changed deliberately, preferably under a documented troubleshooting plan.

Extra logs and diagnostic data can increase datastore consumption. Increased statistics collection or debugging can also add processing or I/O overhead. Before enabling these settings, check available datastore capacity, define how long diagnostic data is needed, and return temporary settings to their normal values after the investigation.

VM swap file location

The VM swap file is used by the VMkernel when host memory reclamation requires swapping VM memory. Its location is separate from the guest operating system's own page file or swap partition.

Where supported, choose a placement strategy such as the VM's datastore or an alternative location defined by the vSphere environment. Before changing it, evaluate:

Available capacity and power-on space on the destination datastore.
Storage performance, latency, and contention for the workload.
Datastore accessibility from every host on which the VM may run.
Operational requirements for clusters, host maintenance, backup, and disaster recovery.

A destination with insufficient capacity or poor performance can prevent the VM from powering on or degrade behavior during host memory pressure. Monitor datastore utilization and VM performance after changing placement.

Fibre Channel NPIV

Fibre Channel NPIV means N_Port ID Virtualization. It allows supported virtual machines to use virtual Fibre Channel identities, commonly represented by virtual World Wide Names, when accessing a Fibre Channel storage fabric. This can help storage administrators identify and manage a VM's SAN access separately from the physical host identity.

NPIV is relevant only in supported Fibre Channel environments. End-to-end support is required from the VM and its compatibility level, ESXi host, Fibre Channel HBAs, switches, storage fabric, and storage array. NPIV configuration also requires coordinated virtual WWN allocation, switch zoning, LUN masking or presentation, and storage-side procedures.

Confirm NPIV support across the VM, host, adapters, switches, and storage system.
Coordinate virtual WWN allocation and SAN zoning with the storage administrators.
Open the applicable NPIV section under VM Options and configure the identifiers according to the approved design.
Save the configuration and validate fabric visibility and guest storage access using the organization's SAN procedures.

Do not change NPIV identifiers or zoning independently on a production workload. Incorrect identities or incomplete zoning can remove access to required LUNs.

Saving and validating changes

Use the dialog's Apply or Save action to commit changes. A setting that can be edited while a VM is powered on may still affect later startup, guest integration, or storage behavior. Other settings require the VM to be powered off, rebooted, or briefly interrupted.

Setting area	Can usually be changed while powered on	May require power off or reboot	Validation to perform
VM name	Usually yes.	Usually no; verify any client-specific restriction.	Confirm the inventory name and understand that datastore file names remain unchanged.
Guest OS type	Often editable, subject to platform restrictions.	A reboot or power state change may be advised for certain changes.	Check guest behavior, defaults, and VMware Tools integration.
VMware Tools settings	Some lifecycle settings can be changed.	Tools installation or upgrade may require a guest reboot.	Check Tools status and guest services.
Boot options	Some settings can be staged for the next boot.	Restart is required to test startup behavior; firmware changes may require power off.	Confirm firmware, boot order, media, and successful guest startup.
Swap file location	Often requires a VM power operation or relocation action.	Power off may be required, depending on the setting and version.	Check destination capacity, accessibility, latency, and VM power-on status.
NPIV	Availability depends on the platform and configuration.	Power off or reconfiguration may be required before identifiers are applied.	Validate virtual WWNs, zoning, fabric visibility, and guest LUN access.

After saving, reopen Edit Settings and confirm the stored value. Then test the behavior relevant to the change: guest functionality for OS or Tools changes, console access for Remote Console changes, boot behavior for firmware changes, datastore health for swap changes, and SAN connectivity for NPIV changes.

Practical VM Options procedures

Rename a VM for inventory clarity

Select the VM, open Edit Settings, and choose VM Options.
Change the VM display name in the general options area.
Save the configuration and verify the new name in the inventory.
Confirm that the datastore directory and existing VM file names were not renamed by this action.

If the datastore files must also be renamed, treat that as a separate migration or file-management task. Consider backup, replication, snapshot, registration, and application dependencies first.

Review VMware Tools maintenance behavior

Open the VM Options tab and expand the VMware Tools section.
Review the available upgrade or lifecycle setting.
Choose behavior that matches the guest patching process and change-control policy.
Schedule a guest reboot if the selected maintenance action requires one.
After the guest is available, validate VMware Tools status and guest integration features.

Place a VM swap file appropriately

Review capacity, performance, latency, and host accessibility for candidate datastores.
Select the supported swap-file location option that meets the operational requirement.
Apply the change according to the VM power-state and maintenance requirements.
Monitor datastore space and VM behavior after the change.

Troubleshooting

The inventory name changed, but the datastore folder did not

This is expected. The inventory display name and datastore file names are separate identities. Treat any file-level rename or migration as a separate administrative task and plan it carefully.

A VM Options setting is missing

The option may depend on the VM power state, compatibility level, guest OS, host capability, storage configuration, licensing, or your assigned permissions. Check each prerequisite and confirm that your role allows the required operation. Also consider whether the setting is exposed differently in your vSphere version.

VMware Tools changes are not effective immediately

The guest may need a Tools installation action, service restart, or reboot. Check Tools status in vSphere and inside the guest, complete the required guest-side action, and reboot only within an approved maintenance window.

The VM does not boot from the expected device

Review the firmware type, boot delay or firmware-setup behavior, connected virtual media, device connection state, and boot-device order. Confirm that the installation media is available and that the selected firmware mode is compatible with the guest.

NPIV configuration fails or SAN access is unavailable

Verify NPIV support, virtual WWNs, HBA configuration, switch zoning, storage masking, and LUN presentation. Work with SAN administrators to validate the entire path from the VM's virtual identity to the storage array.

Swap placement causes capacity or performance problems

Check datastore utilization, latency, contention, and accessibility. If the selected destination is unsuitable, choose another supported placement strategy that meets workload and cluster requirements.

Operational cautions

Review the effect of every change on production workloads and schedule disruptive actions in a maintenance window.
Use least-privilege roles and avoid granting broad configuration rights solely for a single VM change.
Document significant changes, including the previous value, new value, reason, operator, and validation result.
Confirm backup, snapshot, replication, and change-control requirements before consequential modifications.
Do not use snapshots as a substitute for a backup before configuration work; follow the organization's protection policy.
Coordinate Tools, boot, swap, and NPIV changes with the guest, virtualization, and storage owners as appropriate.