VmFaultToleranceConfigIssueReasonForIssue_enum

Possible values:

• haNotEnabled: HA is not enabled on the cluster

• moreThanOneSecondary: There is already a secondary virtual machine for the primary virtual machine

• recordReplayNotSupported:

  Deprecated as of vSphere API 6.0.

  The virtual machine does not support record/replay.

  Vm::Capability.RecordReplaySupported is false.

• replayNotSupported:

  Deprecated as of vSphere API 6.0.

  It is not possible to turn on Fault Tolerance on this powered-on VM.

  The support for record/replay should be enabled or Fault Tolerance turned on, when this VM is powered off.

• templateVm: The virtual machine is a template

• multipleVCPU: The virtual machine has more than one virtual CPU

• hostInactive: The host is not active

• ftUnsupportedHardware: The host ftSupported flag is not set because of hardware issues

• ftUnsupportedProduct: The host ftSupported flag is not set because of it is a VMware Server 2.0

• missingVMotionNic: No VMotion license or VMotion nic is not configured on the host

• missingFTLoggingNic: FT logging nic is not configured on the host

• thinDisk: The virtual machine has thin provisioned disks

• verifySSLCertificateFlagNotSet: The "check host certificate" flag is not set

• hasSnapshots: The virtual machine has one or more snapshots

• noConfig: No configuration information is available for the virtual machine

• ftSecondaryVm: The virtual machine is a fault tolerance secondary virtual machine

• hasLocalDisk: The virtual machine has one or more disks on local datastore

• esxAgentVm: The virtual machine is an ESX agent VM

• video3dEnabled: The virtual machine video device has 3D enabled

• hasUnsupportedDisk

• insufficientBandwidth: FT logging nic does not have desired bandwidth

• hasNestedHVConfiguration: The host does not support fault tolerant VM with nested HV or VBS enabled.

• hasVFlashConfiguration: The virtual machine has a vFlash memory device or/and disks with vFlash cache configured.

• unsupportedProduct: VMware product installed on the host does not support fault tolerance

• cpuHvUnsupported: Host CPU does not support hardware virtualization

• cpuHwmmuUnsupported: Host CPU does not support hardware MMU virtualization

• cpuHvDisabled: Host CPU is compatible for replay-based FT, but hardware virtualization has been disabled in the BIOS.

• hasEFIFirmware: The virtual machine firmware is of type EFI

• tooManyVCPUs: The host does not support fault tolerance virtual machines with the specified number of virtual CPUs.

• tooMuchMemory: The host does not support fault tolerance virtual machines with the specified amount of memory.

• vMotionNotLicensed: No VMotion license

  Since: vSphere API Release 8.0.3.0

• ftNotLicensed: Host does not have proper FT license

  Since: vSphere API Release 8.0.3.0

• haAgentIssue: Host does not have HA agent running properly

  Since: vSphere API Release 8.0.3.0

• unsupportedSPBM: The VM has unsupported storage policy

  Since: vSphere API Release 8.0.3.0

• hasLinkedCloneDisk: The virtual machine has virtual disk in linked-clone mode

  Since: vSphere API Release 8.0.3.0

• unsupportedPMemHAFailOver: Virtual Machine with Pmem HA Failover is not supported

  Since: vSphere API Release 7.0.2.0

• unsupportedEncryptedDisk: Virtual Machine with encrypted virtual disk is not supported.

  Since: vSphere API Release 8.0.3.0

• ftMetroClusterNotEditable: The virtual machine does not allow to enable or disable FT Metro Cluster while FT is turned on.

  Since: vSphere API Release 8.0.3.0

• noHostGroupConfigured: Cannot turn on vSphere Fault Tolerance on a FT Metro Cluster enabled VM with no Host Group configured.

  Since: vSphere API Release 8.0.3.0