You might encounter error messages when trying to use VMware Fault Tolerance (FT). The table lists some of these error messages. For each error message there is a description and information about resolving the error, if applicable.

Fault Tolerance Error Messages

Error Message

Description and Solution

This host contains virtual machines (VMs) with Fault Tolerance turned On; therefore, this host cannot be moved out of its current cluster. To move the host to another cluster, first migrate the VMs with Fault Tolerance turned On to a different host

This host cannot be moved out of the cluster because it contains virtual machines with FT turned on. To move the host to another cluster, first migrate the fault tolerant virtual machines to a different host.

Cannot add a host with virtual machines that have Fault Tolerance turned On to a non-HA enabled cluster

FT requires the cluster to be enabled for VMware HA. Edit your cluster settings and turn on VMware HA.

Cannot add a host with virtual machines that have Fault Tolerance turned On as a stand-alone host

FT cannot be enabled on a stand-alone host. While the host is in the VMware HA-enabled cluster, right-click each virtual machine on the host and select Turn Off Fault Tolerance. Once FT is disabled, the host can be made into a stand-alone host.

Fault Tolerance is enabled on one or more VMs on this host and must be disabled to move the host out of the current cluster

This host cannot be moved out of the cluster until FT is turned off. To turn off FT, right-click the fault tolerant virtual machines and select Turn Off Fault Tolerance.

Fault Tolerance is enabled on VM {vmName}. Disable Fault Tolerance to move the VM from the current [Resource pool, Cluster]

To move the virtual machine to another cluster or to a standalone host, first turn off FT.

The host {hostName} has VMs with Fault Tolerance turned On. Before disconnecting the host, the host should be put into maintenance mode or turn Off Fault Tolerance protection on these VMs

This host cannot be disconnected until it is placed in maintenance mode or until FT is turned off. To turn off FT, right-click the fault tolerant virtual machines and select Turn Off Fault Tolerance.

Virtual machines in the same Fault Tolerance pair cannot be on the same host

You have attempted to VMotion a Secondary VM to the same host a Primary VM is on. A Primary VM and its Secondary VM cannot reside on the same host. Select a different destination host for the Secondary VM.

The unused disk blocks of the virtual machine's disks have not been scrubbed on the file system. This is needed to support features like Fault Tolerance

You have attempted to turn on FT on a powered-on virtual machine which has thick formatted disks with the property of being lazy-zeroed. FT cannot be enabled on such a virtual machine while it is powered on. Power off the virtual machine, then turn on FT and power the virtual machine back on. This changes the disk format of the virtual machine when it is powered back on. Turning on FT could take some time to complete if the virtual disk is large.

The disk blocks of the virtual machine's disks have not been fully provisioned on the file system. This is needed to support features like Fault Tolerance

You have attempted to turn on FT on a powered-on virtual machine with thin provisioned disks. FT cannot be enabled on such a virtual machine while it is powered on. Power off the virtual machine, then turn on FT and power the virtual machine back on. This changes the disk format of the virtual machine when it is powered back on. Turning on FT could take some time to complete if the virtual disk is large.

Unsupported virtual machine configuration for Fault Tolerance

The virtual machine has a virtual device that does not support FT. The specific reason for the incompatibility (for example, multiple vCPUs) is specified in the sub-fault of this message. This error also occurs when you attempt to reconfigure a fault tolerant virtual machine with an unsupported operation, for example, extend disk.

There are configuration issues for the Fault Tolerance operation. Refer to the errors and warnings list for details

There are FT operation issues. To troubleshoot this issue, in the vSphere Client select the failed FT operation in either the Recent Tasks pane or the Tasks & Events tab and click the View details link that appears in the Details column.

This operation is not supported on a Secondary VM of a Fault Tolerant pair

An unsupported operation was performed directly on the Secondary VM. Typically this operation would come from an API. FT does not allow direct interaction with the Secondary VM (except for relocating or migrating it to a different host). Most operations must be performed on the Primary VM.

The Secondary VM with instanceUuid '{instanceUuid}' has already been enabled

An attempt was made to enable FT for a virtual machine on which FT was already enabled. Typically, such an operation would come from an API.

The Secondary VM with instanceUuid '{instanceUuid}' has already been disabled

An attempt was made to disable FT for a Secondary VM on which FT was already disabled. Typically, such an operation would come from an API.

Cannot power On the Fault Tolerance Secondary VM for virtual machine {vmName}. Refer to the errors list for details

An attempt to power on the Secondary VM failed. To troubleshoot this issue, in the vSphere Client select the failed FT operation in either the Recent Tasks pane or the Tasks & Events tab and click the View details link that appears in the Details column.

Host {hostName} does not support virtual machines with Fault Tolerance turned on. This VMware product does not support Fault Tolerance

The product you are using is not compatible with Fault Tolerance. To use the product you must turn Fault Tolerance off. This error message primarily appears when vCenter Server is managing a host with an earlier version of ESX/ESXi or if you are using VMware Server.

Host {hostName} does not support virtual machines with Fault Tolerance turned on. This product supports Fault Tolerance, but the host processor does not

This hosts' processor does not support Fault Tolerance. Use a host with supported hardware to use FT. See the VMware knowledge base article at http://kb.vmware.com/kb/1008027 for information on supported processors.

Host {hostName} has some Fault Tolerance issues for virtual machine {vmName}. Refer to the errors list for details

vCenter Server has detected FT issues on the host. To troubleshoot this issue, in the vSphere Client select the failed FT operation in either the Recent Tasks pane or the Tasks & Events tab and click the View details link that appears in the Details column.

No suitable host can be found to place the Fault Tolerance Secondary VM for virtual machine {vmName}

FT requires that the hosts for the Primary and Secondary VMs use the same CPU model or family and have the same ESX/ESXi host version and patch level. Enable FT on a virtual machine registered to a host with a matching CPU model or family within the cluster. If no such hosts exist, you must add one.

Operation to power On the Fault Tolerance Secondary VM for {vmName} could not be completed within {timeout} seconds

The attempt to start the Secondary VM by copying the state of the Primary VM failed with a timeout. Default timeout is 300 seconds. Determine what is preventing the Secondary VM from powering on. Check if the FT logging NIC on the Primary VM's host and those tried for the Secondary VM is being shared with other network traffic You can reduce traffic on the logging NIC of the Primary and Secondary VMs by moving virtual machines with high network traffic to another host.

The Fault Tolerance Secondary VM was not powered On because the Fault Tolerance Primary VM could not be powered On

The Secondary VM was not powered on due to a failure to power on the Primary VM. This error displays when the vSphere Client is used to attempt to power on a Primary VM or if an SDK client invokes the vim.Datacenter.PowerOnVM() API. You must address the issue that prevented the Primary VM from powering on because vCenter Server attempts to power on the Secondary VM only after it has powered on the Primary VM.

DRS Disabled is the only supported DRS behavior for Fault Tolerance virtual machine {vmName}

An SDK client attempted to set a DRS automation level override for a Primary or Secondary VM. vCenter Server blocks all such attempts to change the DRS automation level of fault tolerant virtual machines.

Host CPU is incompatible with the virtual machine's requirements mismatch detected for these features: CPU does not match

FT requires that the hosts for the Primary and Secondary VMs use the same CPU model, family, and stepping. Enable FT on a virtual machine registered to a host with a matching CPU model, family, and stepping within the cluster. If no such hosts exist, you must add one. This error also occurs when you attempt to migrate a fault tolerant virtual machine to a different host.

Record/Replay is not supported for Guest OS XP/PRO on this CPU

This error occurs when you attempt to power on an FT virtual machine that does not meet all of the configuration requirements for FT. See Turning On Fault Tolerance for Virtual Machines.

The Fault Tolerance configuration of the entity {entityName} has an issue: HA is not enabled on the virtual machine

This virtual machine is on a host that is not in a VMware HA cluster or it has had VMware HA disabled. Fault Tolerance requires VMware HA.

The Fault Tolerance configuration of the entity {entityName} has an issue: Secondary VM already exists

The Primary VM already has a Secondary VM. Do not attempt to create multiple Secondary VMs for the same Primary VM.

The Fault Tolerance configuration of the entity {entityName} has an issue: Template virtual machine

FT cannot be enabled on virtual machines which are templates. Use a non-template virtual machine for FT.

The Fault Tolerance configuration of the entity {entityName} has an issue: Virtual machine with multiple virtual CPUs

FT is only supported on virtual machines with a single vCPU configured. Use a single vCPU virtual machine for FT.

The Fault Tolerance configuration of the entity {entityName} has an issue: Host is inactive

You must enable FT on an active host. An inactive host is one that is disconnected, in maintenance mode, or in standby mode.

The Fault Tolerance configuration of the entity {entityName} has an issue: Fault Tolerance not supported by host hardware

FT is only supported on specific processors and BIOS settings with Hardware Virtualization (HV) enabled. To resolve this issue, use hosts with supported CPU models and BIOS settings.

The Fault Tolerance configuration of the entity {entityName} has an issue: Fault Tolerance not supported by VMware Server 2.0

Upgrade to VMware ESX or ESXi 4.0 or later.

The Fault Tolerance configuration of the entity {entityName} has an issue: No VMotion license or no virtual NIC configured for VMotion

Verify that you have correctly configured networking on the host. See Configure Networking for Host Machines. If it is, then you might need to acquire a VMotion license.

The Fault Tolerance configuration of the entity {entityName} has an issue: No virtual NIC configured for Fault Tolerance logging

An FT logging NIC has not been configured. See Configure Networking for Host Machines for instructions.

The Fault Tolerance configuration of the entity {entityName} has an issue: Check host certificates flag not set for vCenter Server

The "check host certificates" box is not checked in the SSL settings for vCenter Server. You must check that box. See Enable Host Certificate Checking.

The Fault Tolerance configuration of the entity {entityName} has an issue: The virtual machine has one or more snapshots

FT does not support virtual machines with snapshots. Enable FT on a virtual machine without snapshots or use the snapshot manager to delete all snapshots associated with this virtual machine.

The Fault Tolerance configuration of the entity {entityName} has an issue: No configuration information for the virtual machine

vCenter Server has no information about the configuration of the virtual machine. Determine if it is misconfigured. You can try removing the virtual machine from the inventory and re-registering it.

The Fault Tolerance configuration of the entity {entityName} has an issue: Record and replay functionality not supported by the virtual machine

Upgrade the hardware the virtual machine is running on and then turn on FT. Potential configuration issues include:

Software virtualization with FT is unsupported.

FT is not supported for SMP virtual machines.

Paravirtualization (VMI) with FT is not supported.

VM has device that is not supported with FT.

Combination of guest operating system, CPU type and configuration options is incompatible with FT.

See Fault Tolerance Interoperability for more details about these requirements.

The Fault Tolerance configuration of the entity {entityName} has an issue: The virtual machine's current configuration does not support Fault Tolerance

This error occurs when you attempt to turn on FT for a powered-on virtual machine that does not meet all of the configuration requirements for FT. Power off the virtual machine, address the configuration issue, then Turn On Fault Tolerance. Potential configuration issues include:

Software virtualization with FT is unsupported.

FT is not supported for SMP virtual machines.

Paravirtualization (VMI) with FT is not supported.

VM has device that is not supported with FT.

Combination of guest operating system, CPU type and configuration options is incompatible with FT.

See Fault Tolerance Interoperability for more details about these requirements.

The virtual machine has {numCpu} virtual CPUs and is not supported for reason: Fault Tolerance

This error occurs when you attempt to reconfigure a Primary VM with more than one vCPU. You must modify the number of vCPUs to one.

The file backing ({backingFilename}) for device Virtual Floppy is not supported for Fault Tolerance

FT is not supported on a virtual machine with a virtual floppy device that has file backing not accessible to the host upon which the Secondary VM resides. To turn on FT for this virtual machine, first remove the unsupported device.

The file backing ({backingFilename}) for device Virtual CDROM is not supported for Fault Tolerance

FT is not supported on a virtual machine with a virtual CDROM device that has file backing not accessible to the host upon which the Secondary VM resides. To turn on FT for this virtual machine, first remove the unsupported device.

The file backing ({backingFilename}) for device Virtual serial port is not supported for Fault Tolerance

FT is not supported on a virtual machine with a virtual serial port device that has file backing not accessible to the host upon which the Secondary VM resides. To turn on FT for this virtual machine, first remove the unsupported device.

The file backing ({backingFilename}) for device Virtual parallel port is not supported for Fault Tolerance

FT is not supported on a virtual machine with a virtual parallel port device that has file backing not accessible to the host upon which the Secondary VM resides. To turn on FT for this virtual machine, first remove the unsupported device.

The file backing ({backingFilename}) for device Virtual disk is not supported for Fault Tolerance

FT is not supported on a virtual machine with a physical disk that has file backing not accessible to the host upon which the Secondary VM resides. To turn on FT for this virtual machine, first remove the unsupported device.

vCenter disabled Fault Tolerance on VM {vmName} because the Secondary VM could not be powered on

To diagnose why the Secondary VM could not be powered on, see Troubleshooting Fault Tolerance.

Starting the Secondary VM {vmName} timed out within {timeout} ms

You might be experiencing network latency that is causing the timeout. See Troubleshooting Fault Tolerance.

Resynchronizing Primary and Secondary VMs

Fault Tolerance has detected a difference between the Primary and Secondary VMs. This can be caused by transient events which occur due to hardware or software differences between the two hosts. FT has automatically started a new Secondary VM, and no action is required. If you see this message frequently, you should alert support to determine if there is an issue.

Note

For errors related to CPU compatibility, see the VMware knowledge base article at http://kb.vmware.com/kb/1008027 for information on supported processors.