The virtual machine options define a range of virtual machine properties such as name, vApp functionality, its behavior with the guest operating system and VMware Tools, and other Advanced options.

1

Click the Options tab.

2

Select Advanced > General in the Settings list.

a

To disable acceleration, select the Disable acceleration check box.

You can enable and disable acceleration while the virtual machine is running.

In rare instances, you might find that when you install or run software inside a virtual machine, the virtual machine appears to stop responding. Generally, the problem occurs early in the program’s execution. In many cases, you can get past the problem by temporarily disabling acceleration in the virtual machine.

This setting slows down virtual machine performance, so use it only for getting past the problem with running the program. After the program stops encountering problems, deselect Disable acceleration. You might then be able to run the program with acceleration.

b

To enable logging mode, select the Enable logging check box.

c

To enable debugging mode, select an option from the Debugging and Statistics section. Debugging information and statistics can be helpful to VMware technical support in resolving issues.

d

To set advanced configuration parameters, click Configuration Parameters. Generally, you should only change these settings if you intend to use experimental features or when instructed to do so by a VMware technical support representative.

3

Select Advanced > CPUID Mask.

a

Specify whether you want to hide the host’s CPU NX flag from the guest operating system.

Hiding the NX flag prevents the guest operating system from making use of this CPU feature, but enables the virtual machine to be moved to hosts that do not include the NX feature. When the NX flag is visible, the guest operating system can make use of the feature, but the virtual machine can be moved only to hosts with the NX capability.

b

Click Advanced to access the CPU Identification Mask dialog box. An explanation of the symbols in this dialog box is available by clicking Legend.

Note

The virtual machine must be powered off before you can change this setting.

4

Select Advanced > Memory/CPU Hotplug. VMware Tools must be installed for hotplug functionality to work properly.

a

Select Enable memory hot add for this virtual machine to enable memory hot add, or select Disable memory hot add for this virtual machine to disable this feature.

b

Select Enable CPU hot add only for this virtual machine to enable CPU hot add, select Enable CPU hot add and remove for this virtual machine to enable CPU hot add and remove, or select Disable CPU hot plug for this virtual machine to disable this feature.

5

Select Advanced > Boot Options.

a

Specify the duration in milliseconds you want to delay entering the boot sequence when the virtual machine is powered on or restarted.

b

Select the option under Force BIOS Setup to have the virtual machine enter BIOS setup when it boots.

These options are useful when you need to enter the virtual machine’s BIOS setup because sometimes the console attaches to the virtual machine after the boot sequence passes the point where you can enter BIOS.

6

Select Advanced > Paravirtualization. Select Support VMI Paravirtualization to enable VMI Paravirtualization to enable it, or deselect it to disable this feature.

VMI is a paravirtualization standard that enables improved performance for virtual machines capable of utilizing it. Currently, this feature is available only for those versions of the Linux guest operating system which support VMI paravirtualization.

Note

Enabling paravirtualization utilizes one of the virtual machine’s six virtual PCI slots. Also, enabling paravirtualization can limit how and where the virtual machine can be migrated. Consider the following before enabling this feature:

These hosts support VMI paravirtualization: ESX/ESXi 3.5 and greater, and Workstation 6.0 and greater. Hardware version 4 virtual machines with paravirtualization enabled that are created on ESX hosts can be migrated to Workstation hosts without loss of functionality.

A virtual machine with paravirtualization enabled and that is powered off can be moved manually to a host that does not support paravirtualization. However, this can result in reduced performance.

A virtual machine with paravirtualization enabled and that is powered on or in a suspended power state can not be migrated to a host that does not support paravirtualization.

Automated vCenter Server DRS migrations of virtual machines with paravirtualization enabled to hosts that do not support paravirtualization are not allowed.

7

Select Advanced > Fibre Channel NPIV Settings.

N-port ID virtualization (NPIV) provides the ability to share a single physical Fibre Channel HBA port among multiple virtual ports, each with unique identifiers. This allows control over virtual machine access to LUNs on a per-virtual machine basis.

Each virtual port is identified by a pair of world wide names (WWNs): a world wide port name (WWPN) and a world wide node name (WWNN). These WWNs are assigned by vCenter Server.

NPIV support is subject to the following limitations:

NPIV must be enabled on the SAN switch. Contact the switch vendor for information about enabling NPIV on their devices.

NPIV is supported only for virtual machines with RDM disks. Virtual machines with regular virtual disks continue to use the WWNs of the host’s physical HBAs.

The physical HBAs on the ESX host must have access to a LUN using its WWNs in order for any virtual machines on that host to have access to that LUN using their NPIV WWNs. Ensure that access is provided to both the host and the virtual machines.

The physical HBAs on the ESX host must support NPIV. If the physical HBAs do not support NPIV, the virtual machines running on that host will fall back to using the WWNs of the host’s physical HBAs for LUN access.

Each virtual machine can have up to 4 virtual ports. NPIV-enabled virtual machines are assigned exactly 4 NPIV-related WWNs, which are used to communicate with physical HBAs through virtual ports. Therefore, virtual machines can utilize up to 4 physical HBAs for NPIV purposes.

To view or edit a virtual machine’s WWNs:

a

To edit the virtual machine’s WWNs, power off the virtual machine.

b

Ensure that the virtual machine has a datastore containing a LUN that has been made available to the host.

c

Select the Options tab.

d

Select Fibre Channel NPIV.

e

Currently assigned WWNs are displayed in the WWN Assignments box.

f

Do one of the following:

To leave WWNs unchanged, select Leave unchanged.

To have vCenter Server or the ESX host generate new WWNs, select Generate New WWNs.

To remove the current WWN assignments, select Remove WWN assignment.

g

Click OK to save your changes and close the dialog box.

Note

A virtual machine with WWNs that are already in use on the storage network is prevented from powering on. To solve this issue, generate new WWNs or remove them.

Provide the WWN assignments to your SAN administrator. The administrator needs those assignments to configure virtual machine access to the LUN. For more information on how to configure NPIV for a virtual machine, see the Fibre Channel SAN Configuration Guide.

8

Select Advanced > Virtualized MMU and specify whether to disable the feature, always use the feature where available, or have the host system determine whether the feature should be used.

9

Select Advanced > Swapfile Location.

10

Select one of the following options:

Default — Store the virtual machine swapfile at the default location defined by the host or cluster swapfile settings. See Host Configuration for more information on host swapfile settings. See the Resource Management Guide for more information on cluster settings.

Always store with the virtual machine — Store the virtual machine swapfile in the same folder as the virtual machine configuration file.

Store in the host’s swapfile datastore — Store the virtual machine swapfile in the swapfile datastore defined by the host or cluster swapfile settings.