Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

vSphere Fault Tolerance and HA error messages (1033634)

Last Updated: 2/26/2017Categories: InformationalTotal Views: 11603Language:
Chinese (Simplified)JapaneseEnglish

9 like this article

Subscribe to get an email
newsletter with new updates

9 people found this helpful Please provide article feedback:

Details

This article provides a list of common error messages encountered while configuring vSphere Fault Tolerance (FT).

For information on vSphere High Availability (HA) related error messages, see vSphere High Availability error messages (2146276).

Solution

Configuration Errors

Configuration Error Message

Description and Solution

The file backing ({backingFilename}) for device ([email-masked]}) is not supported for Fault Tolerance

This error can be thrown during FT virtual machine reconfiguration to add a device. The file backing for the device indicated in the error message prevents FT protection. For example, adding a host local CD-ROM or Floppy to the primary virtual machine.

Solution:

If adding a CD-ROM or floppy, ensure that the device is file-backed and placed on shared storage, which is accessible to FT secondary host as well.

Cannot set the vSphere HA restart priority to 'Disabled' for the Fault Tolerance VM {vmName}

HA cannot be disabled for FT VMs.

Cannot place the Fault Tolerance VM in an Enhanced vMotion Compatibility cluster, because there are no compatible hosts that have access to all the devices that are configured to be connected at power on

This error is shown when no compatible host is found for an FT virtual machine when it is powered on in an EVC enabled DRS cluster.

CBRC-enabled disk '{device}' is not supported for Fault Tolerance

Virtual machines with disks which have CBRC enabled are not supported for Fault Tolerance.

Solution:

Disable CBRC and try turning-on FT again.

Multi-writer mode enabled disk '{device}' is not supported for Fault Tolerance

Virtual machines with disks which have multi-writer mode (which allows multiple virtual machines to access the same disk) enabled are not supported with SMP-FT.

The FT tie break datastore '{name}' is not accessible. [email-masked]}

The tie-breaker datastore is not accessible.

Solution:

Check storage connectivity of the tie-breaker datastore from the primary and secondary hosts.

Host is already running the recommended number of {maxNumFtVcpus} Fault Tolerance protected vCPUs. To power on or vMotion more FT VMs to this host, you can either move one of the existing Multi-CPU FT Note: This error may also be seen during migration of FT primary/secondary to a host.

By default, a user can start upto 4 FT protected virtual machines/8 FT protected vCPUs on a host. Both primary and secondary virtual machines count towards this limit. If you want to power on more FT virtual machines on a host than the default limit, set das.maxFtVmsPerHost and das.maxFtVcpusPerHost to a higher value than 4/8.

Note: Setting these values to 0 disables the limit.

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 virtual machines use the same type of CPU.

Solution:

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.

Note: This error also occurs when you attempt to migrate a fault tolerant virtual machine to a different host.

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.

Solution: Use hosts with supported CPU models and BIOS settings.

Virtual Machine ROM is not supported

The virtual machine is running VMI kernel and is paravirtualized.

Solution:

VMI is not supported by FT and should be disabled for the virtual machine.

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

Solution:

In 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.

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

Solution: The check host certificates option is not checked in the SSL settings for vCenter Server. You must select this option.

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 vSphere HA cluster or it has had vSphere HA disabled. Fault Tolerance requires vSphere HA.

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

Solution: Enable FT on an active host. An inactive host is one that is disconnected, in maintenance mode, or in standby mode.

Fault Tolerance has not been licensed on host {hostName}, or the license does not support the number of vCPUs running on this VM

Fault Tolerance is not licensed in all editions of VMware vSphere. Check the edition you are running and upgrade to an edition that includes Fault Tolerance.

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. If you have, 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.

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 ESXi/ESX or if you are using VMware Server.

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

Upgrade to VMware ESXi/ESX 4.1 or later.

The build or Fault Tolerance feature version on the destination host is different from the current build or Fault Tolerance feature version: {build}

FT feature versions must be the same on current and destination hosts. Choose a compatible host or upgrade incompatible hosts.

Virtual Machine Configuration Errors

Virtual Machine Configuration Error Message

Description and Solution

The specified host is not compatible with the Fault Tolerance Secondary VM.

Refer to vSphere Troubleshooting for possible causes of this error.

No compatible host for the Secondary VM {vm.name}

Refer to vSphere Troubleshooting for possible causes of this error.

The virtual machine's disk {device} is using the {mode} disk mode which is not supported.

The virtual machine has one or more hard disks configured to use Independent mode. Edit the setting of the virtual machine, select each hard disk, and deselect Independent mode. Verify with your system administrator that this is acceptable for the environment.

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 for 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 for 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.

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

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

These are two error messages you might see if the virtual machine configuration does not support FT.

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

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

FT only runs on a virtual machine with a single vCPU. You might encounter these errors when attempting to turn on FT on a multiple vCPU virtual machine

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

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

Fault Tolerance does not inter-operate with some vSphere features. If you attempt to turn on FT on a virtual machine using a vSphere feature which FT does not support, you might see one of these error messages. To use FT, you must disable the vSphere feature on the relevant virtual machine or enable FT on a virtual machine not using these features.

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

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

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

The Fault Tolerance configuration of the entity VM Name has an issue: The virtual machine has a video device with 3D enabled

These error messages might occur if your virtual machine has an unsupported device. To enable FT on this virtual machine, remove the unsupported device(s), and turn on FT

Operational Errors

Operational Error Message

Description and Solution

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 virtual machines use the same CPU model or family and have the same FT version number or host build number 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.

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

vCenter Server will report why the primary could not be powered on. Correct the conditions and then retry the operation.

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

Retry the Secondary virtual machine power on. The timeout can occur because of networking or other transient issues.

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

To diagnose why the Secondary virtual machine could not be powered on, see vSphere Troubleshooting.

Resynchronizing Primary and Secondary VMs

Fault Tolerance has detected a difference between the Primary and Secondary virtual machines. 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 virtual machine, and no action is required. If you see this message frequently, you should alert support to determine if there is an issue.

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.

Cannot change the vSphere HA settings for Fault Tolerance Secondary VM {vmName}

The vSphere HA settings for a Secondary virtual machine cannot be changed, because it has the same settings as its Primary virtual machine. Always change only the settings of the Primary virtual machine.

Cannot change the DRS behavior for Fault Tolerance Secondary VM {vmName}

You cannot change the DRS behavior of a Secondary virtual machine. This configuration is inherited from the Primary virtual machine.

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

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

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 vSphere HA. Edit your cluster settings and turn on vSphere HA.

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

Turn off Fault Tolerance before adding the host as a standalone host to vCenter Server.

To turn off FT, right-click each virtual machine on the host and select Turn Off Fault Tolerance. Then you can add the host as a stand-alone host.

Cannot set the HA restart priority to 'Disabled' for the Fault Tolerance VM {vmName}

This setting is not allowed for an FT virtual machine. You only see this error if you change the restart priority of an FT virtual machine to Disabled.

Host already has the recommended number of {maxNumFtVms} Fault Tolerance VMs running on it

To power on or migrate more FT virtual machines to this host, either move one of the existing Fault Tolerance virtual machines to another host or disable this restriction by setting the vSphere HA advanced option das.maxftvmsperhost to 0.

Operations to test Fault Tolerance by terminating the primary VM or secondary VM are not allowed for the Fault Tolerance VM {vmName} at this time, because it is not protected by vSphere HA yet and therefore no action will be taken to recover Fault Tolerance protection for this VM

You tried to test failover functionality or attempted the Restart Secondary task on a virtual machine that is not protected by vSphere HA. Do not attempt these tasks until the virtual machine is protected by vSphere HA.

SDK Operational Errors

SDK Operational Error Message

Description and Solution

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

An unsupported operation was performed directly on the Secondary virtual machine using the API. FT does not allow direct interaction with the Secondary virtual machine (except for relocating or migrating it to a different host).

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

The Primary virtual machine already has a Secondary virtual machine. Do not attempt to create multiple Secondary virtual machines for the same Primary virtual machine.

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 virtual machine on which FT was already disabled. Typically, such an operation would come from an API.

Note: For errors related to CPU compatibility, see Processors and guest operating systems that support VMware Fault Tolerance (1008027). You can also use the VMware SiteSurvey utility (see the VMware Shared Utilities page) to get a clearer understanding of the configuration issues associated with the cluster, host, and virtual machines being used for vSphere FT.

For more information on troubleshooting vSphere 5, see vSphere Troubleshooting in the vSphere 5 Documentation Center.

For more information on troubleshooting vSphere 6, see vSphere Troubleshooting in the vSphere 6 Documentation Center

For error related to High Availability (HA), see vSphere High Availability error messages (2146276) .

Additional Information

For translated versions of this article, see:
Español: Mensajes de error de HA y FT de vSphere (2053741)

Português: Mensagens de erro do vSphere HA e FT (2037322)
日本語: vSphereのHAおよびFTのエラーメッセージ (2013733)
简体中文: vSphere HA 和 FT 错误消息 (2075507)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server

Related Versions:

VMware vCenter Server 5.5.x

VMware vCenter Server 5.1.x

VMware vCenter Server 5.0.x

VMware vCenter Server 4.1.x

Take Our Survey

Support Assistant