VMware vSphere Faults
- The virtual machine has no virtual disks that are suitable for customization.
- The object {file} is not a directory.
- Network card '{device}' has a DVPort backing, which is not supported. This could be because the host does not support VDS or because the host has not joined a VDS.
- Moving a virtual machine that has snapshots is not supported when the virtual machine has disks or other files placed outside of its home directory and datastore.
- Line {lineNumber}: Unknown entity was found.
- The powered on virtual machine is temporarily disabled.
- Illegal or out-of-range value specified for Netflow monitoring configuration.
- This operation would violate a virtual machine affinity/anti-affinity rule.
- Cannot find the device '{deviceIndex}', which is referenced in the edit or remove device operation.
- Virtual machine requires {numCpuVm} logical CPUs to operate, but the host hardware only provides {numCpuDest}.
- Host '{hostName}' does not support the VM Component Protection feature. It cannot be added or moved to the specified cluster, which has this feature enabled.
- The required VMware Tools ISO image does not exist or is inaccessible.
- There are no active hosts in the cluster.
- Cannot complete operation because VMware Tools is not running in this virtual machine.
- SSL is disabled on the host.
- Host specification operation failed. Check log for details.
- Invalid configuration for device '{deviceIndex}'.
- The file backing ({backingFilename}) for device ({backingType.@enum.VmFaultToleranceInvalidFileBacking.DeviceType}) is not supported for Fault Tolerance.
- The object {file} is not a file.
- Invalid virtual machine configuration.
- There is no suitable host in the inventory as reference host for the profile {profileName}.
- The specified host does not support virtual machines with vSphere Replication turned on.
- Line {lineNumber}: No '{boundary}' declared.
- Two conflicting values have been specified - {invalidProperty} and {conflictingProperty}.
- An error occurred while quiescing the virtual machine. See the virtual machine's event log for details.
- An invalid event.
- The amount of CPU resource available in the parent resource pool is insufficient for the operation.
- The login does not have permission to collect inventory/performance data.
- General fault in the Virtual Machine Metadata Manager.
- The total number of virtual CPUs present or requested in virtual machines' configuration has exceeded the limit on the host: {maxSupportedVcpus}.
- Cannot remove the object, since it has active related objects.
- Storage DRS is unable to move vSphere Replication secondary replica disks because the vSphere Replication management server configuration has changed since the last invocation.
- The virtual machine is configured to override the default swapfile placement policy, which is not supported on the host.
- The parent vApp is not running.
- A change in the network configuration disconnected the host '{host}' from vCenter Server. The change has been rolled back.
- Cannot use distributed port {portKey} as both the transmitted source and the destination source in distributed port mirroring sessions with different keys. Session key {vspanSessionKey1} does not match session key {vspanSessionKey2}.
- Host already has the recommended number of {maxNumFtVms} Fault Tolerance VMs running on it. To power on or vMotion more FT VMs to this host either move one of the existing Fault Tolerance VMs to another host or disable this restriction by setting the vSphere HA advanced option das.maxFtVmsPerHost to 0.
- Unsupported element '{name}' was found. Could not export to OVF. '{reason}'.
- Does not support virtual machines with IDE disks.
- The guest operations agent could not be contacted.
- The request version '{vmRequestModuleVersion}' of the virtual flash module '{moduleName}' associated with the VMDK virtual Flash Read Cache is not compatible with versions ['{hostMinSupportedVerson}','{hostModuleVersion}'] supported on the host.
- Line {lineNumber}: Attribute '{attributeName}' refers to non-existing reference '{value}' on element '{elementName}'.
- Device '{device}' is disk which is not in persistent mode.
- I/O filter {name} is being used by one or more disks.
- An error occurred because the guest registry key has sub-keys. To delete the key, use the recursive delete option.
- Storage DRS does not allow shared datastores across datacenters.
- DRS cannot find a host to power on or migrate the virtual machine.
- Virtual machines in the same Fault Tolerance pair cannot be on the same host.
- {connected.@enum.fault.NIC.connected} '{device}' uses network '{backing}', which is accessed on the host via a switch that has insufficient free ports.
- Storage vMotion is not supported on the host '{failedHostName}'.
- Cannot connect to host.
- The specified network resource '{remoteHost}:{remotePath}' cannot be located. Cannot configure NAS datastore '{name}'.
- The operation violates the dvPort's scope.
- Line {lineNumber}: Cannot import OVF descriptor.
- The VMkernel physical NIC adapter {pnicDevice} is currently used by iSCSI Host Bus Adapter.
- vMotion interface '{network}' on the {atSourceHost.@enum.fault.VMotion.atSourceHost} host '{failedHost}' does not have any operational physical network connections.
- Cannot perform power operation on host.
- The host does not have sufficient CPU resources to satisfy the reservation.
- Additional namespaces cannot be created on this virtual machine.
- Virtual machine compatibility is already up-to-date.
- DRS has determined that correcting the soft VM/Host affinity rules constraint violation for VM '{vmName}' would impact respecting cluster constraints or performance goals.
- Invalid IPMI MAC address.
- No datastore in the datastore cluster is compatible with the virtual machine.
- No compatible host has sufficient resources to satisfy the reservation.
- The build or Fault Tolerance feature version on the destination host is different from the current build or Fault Tolerance feature version: {build}.
- Line {lineNumber}: An invalid element '{name}' is found in the OVF descriptor.
- The vApp does not contain any virtual machines.
- No datastore in the datastore cluster is connected to the host that the virtual machine is registered on.
- Limit for number of hosts in the cluster has been reached.
- The specified directory {file} is not empty.
- Swap datastore not writable on host.
- Error encountered while shrinking disk.
- Host customization validation failed. Check the host settings for errors.
- The host advertises different SSL certificates for different management ports and cannot be managed by vCenter. Ensure the same certificate is used by all relevant management ports or use certificates that are verifiable by the vCenter Server. If the host you are adding is an ESX 2.x host, this probably means that the authenticated certificate (in /etc/vmware/ssl/rui.*) and the Management UI certificate (in /etc/vmware-mui/ssl/mui.*) are different.
- Device '{device}' has a backing type that is not supported. {reason.@enum.fault.DeviceNotSupported.Reason}
- A host gateway server '{gatewayType}:{gatewayId}' is not available.
- The VMkernel virtual NIC adapter {vnicDevice} is not valid.
- Migration was temporarily disabled due to another migration activity.
- The feature cannot be set or reset because it is either not available, the license has expired, or it is a special feature such as vCenter agent for ESX 4.0 Server.
- Operation '{op}' disallowed by one or more policies.
- Too large clock skew was detected.
- Patch (ID {patchID}) not applicable to the host.
- Operation rejected - input value {input} too small; minimum value is {policy}: {policyTarget}, {policyTargetProperty}
- Host cannot be added to the cluster.
- The host does not have sufficient memory resources to satisfy the reservation.
- The firewall configuration prevents the current operation from completing successfully.
- The user account selected to connect to the host does not have sufficient permission to enable vCenter to manage the host.
- Duplicated properties found in the OVF package. Not all properties will be prompted for during deployment.
- Changing the network and host of a virtual machine during vMotion is not supported on the {atSourceHost.@enum.fault.VMotion.atSourceHost} host '{failedHostName}'.
- Incompatible device backing specified for device '{deviceIndex}'.
- The selected Enhanced vMotion Compatibility mode cannot be enabled, because the cluster contains disconnected hosts.
- No virtual machines have been configured to power on.
- Cannot change the host configuration.
- The specified folder does not support this operation.
- Unable to access the virtual machine configuration: {reason.msg}
- Line {lineNumber}: Could not parse the document: '{description}'.
- The host {hostName} has VMs with Fault Tolerance turned on. To disconnect the host, you have three options. First, you can turn off Fault Tolerance protection on these VMs. Second, you can power off these VMs, then migrate the primary and secondary VMs of each Fault Tolerance pair to this host, and finally put the host in maintenance mode. Or, third, you can migrate the FT VMs to another host.
- The rollback operation failed on {entityType}: {entityName}. A previous configuration does not exist.
- Reached the structural limitation of the resource pool hierarchy.
- Could not verify the certificate of the specified vSphere Authentication Proxy server.
- Operation rejected - input value {input} not in set {set}: {policyTarget},{policyTargetProperty}
- Could not complete network copy for file {file}
- Cannot take a memory snapshot, since the virtual machine is configured with independent disks.
- Cannot complete the operation because the file or folder {file} already exists
- File {file} was not found
- Operation timed out.
- The host's BMC does not support IPMI.
- The metadata operation has failed. Retry it!
- Unable to access file {file}
- License key has expired.
- Cannot complete install since binaries associated with this patch are missing.
- The default device '{device}' is configured with settings which are incompatible with the default settings on the target host.
- License check out was restricted by the license server's option file.
- Extension registered without a subject name.
- The provided networking configuration contains duplicate entries for interface '{device}'.
- The current operation cannot be performed on the host '{hostname}' because it has been configured as a failover host for a cluster.
- Cannot complete file creation operation.
- Permission to perform this operation was denied.
- {faultType.@enum.fault.QuarantineModeFault.FaultType}
- Line {lineNumber}: Mismatch between property type: '{type}' and property value '{value}'.
- The operation cannot be performed while the host is part of a Windows domain.
- Invalid IPMI login information.
- The setting of {entry.@enum.InvalidDasConfigArgument.EntryForInvalidArgument} is invalid for cluster {clusterName}.
- Cannot complete signature verification on the required VMware Tools ISO image.
- Line {lineNumber}: An OVF specification constrain could not be verified.
- 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.
- Client connected without supplying a certificate.
- Line {lineNumber}: Unsupported attribute '{attributeName}' on element '{elementName}'
- Cannot create a diagnostic bundle.
- The session ticket is invalid.
- An attempt was made to write to the read-only file {file}
- Error caused by file {file}
- Unsupported virtual machine configuration for record and replay.
- The VMkernel FCoE physical NIC adapter {nicDevice} must be bound to a switch uplink port.
- The resource {type} is not available in {containerType} {containerName}.
- The hierarchy of native clones of file {file} is too deep.
- The device or operation specified at index '{deviceIndex}' is not supported for the current virtual machine version '{currentVersion}'.\nA minimum version of '{expectedVersion}' is required for this operation to succeed.
- Line {lineNumber}: Attribute '{attributeName}' value was empty in element '{elementName}'.
- Unsupported virtual machine configuration for Fault Tolerance.
- Virtual ethernet card '{device}' is not supported. {reason.@enum.fault.DeviceNotSupported.Reason}
- The administrator permission has already been disabled on the host (except for the vim user)
- Cannot configure NAS datastore '{name}' on '{remoteHost}:{remotePath}'. Cannot make additional connections to this remote computer because the maximum number of connections has been reached (71).
- Secondary VM could not be relocated or powered on as there are no compatible hosts that can accommodate it.
- The guest process {pid,s} was not found.
- The device or operation specified at index '{deviceIndex}' is not supported for the existing virtual machine platform.
- Relocation of suspended virtual machines is not supported between the source and destination hosts.
- Operation rejected - input value {input} not in range [{minval}-{maxval}]: {policyTarget},{policyTargetProperty}
- Privilege '{privilege}' does not exist.
- Line {lineNumber}: Backing '{backingName}' not supported by device '{deviceName}'.
- Invalid type {type} for property {id}.
- The virtual machine's disk {device} is using the {mode} disk mode which is not supported.
- A virtual machine reconfigure operation includes a change to the disk mode property which cannot be changed if the virtual machine has at least one snapshot.
- Too many concurrent guest login sessions are active.
- The configurations of the objects are in conflict.
- Unable to export disk '{diskName}'. Could not parse disk name.
- Cannot change non-promiscuous distributed port group {portgroupName} to promiscuous mode. One or more distributed ports in this distributed port group are used as transmitted source or destination ports in a distributed port mirroring session.
- Gateway server '{gatewayType}:{gatewayId}' cannot connect to {hostname}:{port}. Details:\n{message}
- Database temporarily unavailable or has network problems.
- Hot plug of device '{deviceIndex}' is not supported for this virtual machine.
- The virtual machine is installing VMware Tools and cannot initiate a migration operation
- Metadata '{metaData}' missing or corrupted.
- {connected.@enum.fault.NIC.connected} '{device}' is a previous interface whose network association cannot be determined.
- Operation rejected - input value {input} too large; maximum value is {policy}: {policyTarget}, {policyTargetProperty}
- The datastore is not compatible with the virtual machine.
- vCenter Server cannot access the host gateway server '{gatewayType}:{gatewayId}'.
- Another task is already in progress.
- An error occurred because the specified guest registry key already exists.
- There were too many consecutive overrides of the resource settings pushed from the cluster.
- Line {lineNumber}: Unable to parse '{value}' for attribute '{attributeName}' on element '{elementName}'.
- The Secondary VM with instanceUuid '{instanceUuid}' has already been disabled.
- Import operation failed on one or more hosts.
- Unable to compute fault tolerant compatible hosts on the VM {vmName}.
- Cannot find a peer host to wake up this host.
- The vCenter Server managed IP is not configured.
- {message}
- The operation failed because the guest alias store mapping file contains multiple instances of the same certificate and user name.
- Cannot complete the license assignment operation
- The VMware Tools upgrade operation was canceled.
- Success.
- The disk resides on a non-local storage transport: '{device}'.
- Operation to power on the Fault Tolerance Secondary VM for {vmName} could not be completed within {timeout} seconds
- Gateway server '{gatewayType}:{gatewayId}' cannot communicate with remote host {hostname}.
- The device '{deviceIndex}' is referring to a nonexisting controller '{controllerKey}'.
- A failure occurred during 3rd party license assignment.
- An error occurred during customization while running the IP or host name generator application.
- Line {lineNumber}: Attribute '{attributeName}' refers to a non-existing configuration '{value}' on element '{elementName}'.
- The {edition} license cannot be assigned to {entityId} because some features are in use.
- The host's CPU hardware does not support Enhanced vMotion Compatibility, which is enabled for this cluster.
- Copying this virtual machine will cause loss of snapshots at the destination.
- Line {lineNumber}: No space left for device '{name}' on parent controller '{parent}'.
- Cannot complete installation - higher version of patch already installed.
- Cannot move the distributed port {portKey} from distributed port group {srcPortgroupName} to promiscuous distributed port group {destPortgroupName}. This operation might change the non-promiscuous distributed port to promiscuous mode.
- VM name '{name}' could not be normalized.
- Gateway server '{gatewayType}:{gatewayId}' requires user validation to trust host {hostname}.
- The available storage space is not sufficient for the operation.
- 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.
- The attempted operation cannot be performed in the current state ({existingState.@enum.VirtualMachine.PowerState}).
- Virtual machine uses {roDiskCount} undoable or nonpersistent disks. For a vMotion to a previous-version host, this number of disks will cause the following condition: {timeoutDanger.@enum.fault.VMotion.tooManyRODisks}.
- An error occurred while accessing a disk lease.
- Unable to access virtual disk '{device}' from the host. Either the host is disconnected from the datastore or has insufficient privilege. Details: {fault.msg}
- The virtual machine requires hardware features that are unsupported or disabled on the target host. If possible, use a cluster with Enhanced vMotion Compatibility (EVC) enabled; see KB article 1003212.\n\nCPUID details: incompatibility at level {level,x} register '{registerName}'.\nHost bits: {registerBits}\nRequired: {desiredBits}
- The host's CPU hardware does not support the cluster's current Enhanced vMotion Compatibility mode. The host CPU lacks features required by that mode.
- Failed to enable Storage Policy Based Management feature on compute resource {csName}
- Cannot change the vSphere HA settings for Fault Tolerance Secondary VM {vmName}.
- Line {lineNumber}: Missing attribute '{attributeName}' on element '{elementName}'.
- Line {lineNumber}: Unsupported hardware family '{version}'.
- Datastore '{name}' conflicts with an existing datastore in the datacenter that has the same URL ({url}), but is backed by different physical storage.
- Line {lineNumber}: Duplicated boundary '{boundary}'.
- A specified parameter is not correct.\n{invalidProperty}[{key}]
- The vSphere HA agent on host '{hostName}' failed to quiesce file activity on datastore '{dsName}'. To proceed with the operation to unmount or remove a datastore, ensure that the datastore is accessible, the host is reachable and its vSphere HA agent is running.
- DRS was invoked to place inter-dependent virtual machines but they are not listed in topological order.
- The requested Storage vMotion would place a mapped direct-access LUN in a location other than the virtual machine's new home, but such a move is not supported on the {atSourceHost.@enum.fault.VMotion.atSourceHost} host '{failedHostName}'.
- The host does not have a suitable FQDN.
- Line {lineNumber}: Unsupported value '{value}' for element '{name}'.
- The VMkernel virtual NIC adapter {vnicDevice} cannot be used because the attached physical uplink does not match the iSCSI Host Bus adapter.
- The host's CPU hardware should support the cluster's current Enhanced vMotion Compatibility mode, but some of the necessary CPU features are missing from the host. Check the host's BIOS configuration to ensure that no necessary features are disabled (such as XD, VT, AES, or PCLMULQDQ for Intel, or NX for AMD). For more information, see KB articles 1003212 and 1034926.
- Host '{hostName}' is of type ({productName} {productVersion}), it does not support the VM that has VPX assigned MAC address which is not prefixed with 00:50:56
- The specified vSphere Authentication Proxy server is not valid or could not be contacted.
- Virtual disk '{device}' is a mapped direct-access LUN in physical compatibility mode, which is not supported. {reason.@enum.fault.DeviceNotSupported.Reason}
- Cannot complete the configuration of the vSphere HA agent on the host. {reason.@enum.fault.DasConfigFault.DasConfigFaultReason}.
- Device '{device}' is a connected parallel port, which is also a file-backed serial port.
- Windows customization resources were not found on the server.
- The VMkernel virtual NIC adapter {vnicDevice} is not bound to iSCSI Host Bus Adapter.
- Host is down.
- Invalid datastore path '{datastorePath}'.
- Unknown login or incorrect password.
- Enhanced vMotion Compatibility (EVC) cannot be enabled because the cluster contains hosts that lack EVC-capable hardware.
- Concurrent vApp operation in progress on target.
- Cannot connect to 'perfmon'. Remote registry disabled or the collector service is not running with administrator privileges.
- Cannot export '{vmPath}' to an OVF file.
- Target does not support CPU validation.
- The cluster cannot have mixed environment of older ESXi hosts and new ESXi 6.0 hosts. Upgrade your ESXi hosts to 6.0 or later.
- You cannot {operation.@enum.fault.CannotPowerOffVmInCluster.Operation} the virtual machine {vmName} at this time because the virtual machine is not managed by the master vSphere HA agent to which vCenter Server is connected. This condition will occur if the cluster has a management network partition or a datastore connectivity problem. If there is a management network partition, disabling vSphere HA is not advised because the virtual machine might be subsequently restarted by vSphere HA on an inaccessible host. As a result, you would not be able to manage the virtual machine until the partition has been resolved. However, if the problem is due to a storage issue and at least one host in the cluster has access to the datastores required by the virtual machine, the master should become the manager of the virtual machine shortly, after which the operation would be allowed.
- The virtual machine requires hardware features that are unsupported or disabled on the target host. If possible, use a cluster with Enhanced vMotion Compatibility (EVC) enabled; see KB article 1003212.\n\nCPUID details: incompatibility at level {level,x} register '{registerName}'.\nHost bits: {registerBits}\nRequired: {desiredBits}
- All required agent virtual machines are not currently deployed on host '{hostname}'.
- Disk provisioning type {diskProvisioning} is not supported by the host. Supported disk provisioning types are: {supportedDiskProvisioning}.
- Line {lineNumber}: OVF hardware element '{name}' with instance ID '{instanceId}': No support for the virtual hardware device type '{deviceType}'.
- Specifying non-standard disk movement types is not supported.
- There are active storage paths using this VMkernel virtual NIC adapter {vnicDevice}.
- OVF System error.
- Operation violates conditions of one or more policies.
- Fault Tolerance is enabled on VM {vmName}. Disable Fault Tolerance to move the VM from the current {moveType.@enum.CannotMoveFaultToleranceVm.MoveType}.
- Invalid value '{value}' specified for property {id}.
- Migration of virtual machines with snapshots is not supported between the source and destination.
- The guest authentication being used does not have sufficient permissions to perform the operation.
- The Secondary VM with instanceUuid '{instanceUuid}'is not registered with this Primary VM.
- Unable to acquire licenses because the license source is unavailable: The license manager has not been started yet, the wrong port@host or license file is being used, or the port or host name in the license file has been changed.
- The vSAN host cannot be moved to the destination cluster: destination cluster {destinationCluster} is vSAN disabled.
- The user or group named '{principal}' does not exist.
- Insufficient disk space on datastore '{datastore}'.
- Duplicated property {fqid} in vApp. This might not import properly on all platforms.
- Virtual disk '{device}' is a mapped direct-access LUN which is not supported on the datastore '{datastoreName}'.
- The available storage IOPs capacity is not sufficient for the operation.
- Authenticity of the host's SSL certificate is not verified.
- Cannot configure NAS datastore '{name}'.
- Host {hostName} does not support virtual machine Record/Replay. \n{reason.@enum.fault.HostIncompatibleForRecordReplay.Reason}
- The provided network mapping between OVF networks and the system network is not supported by any host.
- Resource settings were modified directly on the host while it was disconnected from vCenter Server.
- Operation must be executed by a non Active Directory user.
- The method is disabled by '{source}'
- The requested Enhanced vMotion Compatibility configuration requires CPU vendor '{modeCPUVendor}', but the cluster's hosts have CPU vendor '{clusterCPUVendor}'.
- {connected.@enum.fault.Device.connected} '{device}' uses backing '{backing}', which is not accessible.
- Host '{hostName}' does not support the vSphere HA VM Component Protection feature. It cannot be added or moved to the specified cluster, which has this feature enabled.
- Device '{device}' is a SCSI controller engaged in bus-sharing.
- An error occurred while accessing or modifying a Windows guest registry value.
- The requested operation is currently disallowed on host using a direct connection.
- This operation is restricted by the administrator - '{details}'. Contact your system administrator.
- Device '{device}' is a connected device with a remote backing.
- Unable to change license state as the license server is not available.
- Metadata for patch missing.
- User account has no right to add hosts to the domain.
- An error occurred while accessing or modifying the Windows guest registry.
- Line {lineNumber}: Unsupported virtual hardware device '{deviceSubType}'.
- Operation rejected - input value {input} cannot equal {policy}: {policyTarget}, {policyTargetProperty}
- Cannot ping target host
- Cannot complete a vSphere Distributed Switch operation for one or more host members.
- Virtual machine is configured to use a device that prevents the operation: {fault.msg}
- Line {lineNumber}: Qualifier '{qualifier}' was ignored.
- Hosts of this type ({productName} {productVersion}) do not support all of the features required to participate in the specified vSphere Distributed Switch.
- No suitable host can be found to place the Fault Tolerance Secondary VM for virtual machine {vmName}.
- No running-point snapshot was found.
- The guest operating system '{unsupportedGuestOS}' is not supported.
- Virtual disk '{device}' is a mapped direct-access LUN, which is not supported. {reason.@enum.fault.DeviceNotSupported.Reason}
- Storage DRS is unable to move the following vSphere Replication secondary replica disks: {nonMovableDiskIds}
- Line {lineNumber}: Invalid value '{value}' for attribute '{attributeName}' on element '{elementName}'.
- The available virtual flash resource '{freeSpaceInMB}' MB ('{freeSpace}' bytes) is not sufficient for the requested operation '{requestedSpaceInMB}' MB ('{requestedSpace}' bytes).
- Netflow monitoring cannot be enabled because the switch does not have an IP address and/or port specified for the collector.
- Existing partitions found on disk '{device}'.
- The memory size, reservation, limit or shares of the virtual machine {vmName} cannot be edited while Fault Tolerance is turned on.
- Operation rejected owing to a value controlled by one or more policies.
- The provided owner OP value is invalid.
- Line {lineNumber}: Invalid attribute in OVF descriptor.
- Line {lineNumber}: HostResource value ({value})is not supported.
- The extension key of the vSphere Distributed Switch {dvsExtensionKey} is not the same as the login session's extension key {sessionExtensionKey}.
- Property {id} is not user configurable.
- {message}
- The disk is the only HDD disk remaining in a disk group: '{device}'.
- The operation is not allowed in the current state.
- Cannot create a quiesced snapshot because the create snapshot operation exceeded the time limit for holding off I/O in the frozen virtual machine.
- There are insufficient licenses to complete this operation.
- Cannot complete the operation. The vRAM limit of {limit}GB will be exceeded. Upgrade the vCenter Server license or decrease the amount of the consumed vRAM.
- The host's CPU vendor '{hostCPUVendor}' does not match the required CPU vendor '{clusterCPUVendor}' in the Enhanced vMotion Compatibility configuration for the cluster.
- Memory hot plug is not supported for this virtual machine.
- Unknown device: '{device.deviceInfo.label}'.
- Cannot change the distributed port group {portgroupName} type from static/dynamic binding to ephemeral. Some of its distributed ports participate in a distributed port mirroring session.
- Cannot complete image library operation.
- Line {lineNumber}: Unexpected element '{name}'.
- Enhanced vMotion Compatibility cannot be enabled because the cluster contains CPUs from more than one vendor.
- Storage DRS is unable to move virtual disks shared by multiple virtual machines.
- Enhanced vMotion Compatibility (EVC) cannot be enabled because the cluster contains hosts that do not support EVC.
- Storage DRS is unable to move vSphere Replication secondary replica disks because the vSphere Replication management server is unreachable.
- An error occurred during host configuration.
- Cannot add a host with virtual machines that have Fault Tolerance turned on to a non-vSphere HA enabled cluster.
- The virtual machine requires hardware features that are unsupported or disabled on the target host:\n{nx.@enum.fault.CpuIncompatible81EDX.nx}{ffxsr.@enum.fault.CpuIncompatible81EDX.ffxsr}{rdtscp.@enum.fault.CpuIncompatible81EDX.rdtscp}{lm.@enum.fault.CpuIncompatible81EDX.lm}{otherOnly.@enum.fault.CpuIncompatible81EDX.otherOnly}\nFor incompatibilities other than NX/XD or longmode: if possible, use a cluster with Enhanced vMotion Compatibility (EVC) enabled; see KB article 1003212.\n\nCPUID details: incompatibility at level {level,x} register '{registerName}'.\nHost bits: {registerBits}\nRequired: {desiredBits}
- The host does not have sufficient network capacity to satisfy the reservation.
- Invalid or unsupported virtual machine configuration.
- The Secondary VM with instanceUuid '{instanceUuid}'is already registered with this Primary VM.
- The version of VMware Tools installed in the virtual machine is already up-to-date.
- An error occurred while using host gateway server '{gatewayType}:{gatewayId}'.
- Cannot complete import operation for one or more entities.
- The object or item referred to could not be found.
- The cluster contains no hosts satisfying the hard VM/host affinity rules constraint for VM '{vmName}'.
- Line {lineNumber}: Invalid OVF property.
- Device '{device}' uses a controller that is not supported. {reason.@enum.fault.DeviceNotSupported.Reason}
- Reverting to snapshot might generate {errors.@enum.fault.Snapshot.revert.errors} on the destination host.
- The user '{userName}' does not have sufficient permission on the CIFS volume. Could not configure NAS datastore {name}.
- Cannot login to the remote host. The user name '{userName}' or password specified may be incorrect.\nCannot configure NAS datastore '{name}'.
- The virtual flash resource on host '{hostName}' is not accessible.
- The target host does not support the virtual machine's current hardware requirements.
- Cannot write on datastore '{name}' on the target host.
- Operation violates one or more policies.
- Console access to the virtual machine cannot be granted since the connection limit of {connectionLimit} has been reached.
- Out of IP addresses on network '{value}'.
- Storage DRS is unable to move vSphere Replication secondary replica disks because the vSphere Replication management server is currently moving a subset of disks.
- The vSAN cluster cannot be re-configured when vSphere HA is enabled.
- Invalid disk reference '{diskName}' for virtual system '{vmName}'.
- Unable to access the network to configure NAS datastore '{name}'.
- The specified domain either does not exist or could not be contacted.
- There are insufficient CPU/memory resources on standby hosts (if any) to meet the requirements of a given operation.
- The requested change cannot be completed because it could leave the system without full administrative privileges for a user or group.
- One or more virtual machines on host {hostname} are already registered to hosts in the destination datacenter.
- Missing hardware element '{name}' with RASD type '{resourceType}'.
- The FT tie break datastore '{name}' is not accessible. {detail.@enum.fault.InaccessibleDatastore.Reason}
- The vMotion interface is not configured (or is misconfigured) on the {atSourceHost.@enum.fault.VMotion.atSourceHost} host '{failedHost}'.
- Metadata associated with this path is corrupted or unreadable.
- Cannot export an OVF descriptor.
- A generic vApp configuration fault.
- The name of the object {file} is too long.
- vSphere Replication operation error. Cannot start a {requestedActivity.@enum.fault.ReplicationVmInProgressFault.Activity} because a {inProgressActivity.@enum.fault.ReplicationVmInProgressFault.Activity} is already in progress.
- Storage DRS is unable to move virtual machines with mounted CD-ROM drives or with snapshots having mounted CD-ROM drives.
- Operation rejected - input value {input} must equal {policy}: {policyTarget}, {policyTargetProperty}
- The disk blocks of the virtual machine's disks have not been fully provisioned on the file system.\nThis is needed to support features like Fault Tolerance.
- The VMkernel virtual NIC adapter {vnicDevice} is already bound to the iSCSI Host Bus Adapter.
- The specified NFS volume '{remoteHost}:{remotePath}' is not mounted on the server. Cannot configure NAS datastore '{name}'.
- The license assignment cannot be completed because the license type and entity type do not match.
- Disabling administrator permission is not supported on the host.
- Line {lineNumber}: OVF descriptor could not be parsed.
- The number of network adapter settings in the customization specification: {numberOfNicsInSpec} does not match the number of network adapters present in the virtual machine: {numberOfNicsInVM}.
- Write failed on backup blob for {entityType}: {entityName}.
- Cannot complete the operation. See the event log for details.
- Cannot power on the Fault Tolerance Secondary VM for virtual machine {vmName}. Refer to the errors list for details.
- The available Memory resources in the parent resource pool are insufficient for the operation.
- Distributed port {portKey} cannot be used as destination port in multiple distributed port mirroring sessions with keys {vspanSessionKey1} and {vspanSessionKey2}.
- {connected.@enum.fault.NIC.connected} '{device}' uses network '{backing}', which is configured for different offload or security policies on the destination host than on the source host.
- Line {lineNumber}: Unsupported element '{name}'
- Switch feature cannot be enabled because the switch does not have an IP address assigned.
- Storage DRS is unable to move independent disks.
- Connected device '{device.deviceInfo.label}'.
- The cluster contains no hosts satisfying the soft VM/host affinity rules constraint for VM '{vmName}'.
- The virtual disk is either corrupted or not a supported format.
- Cannot complete acquiring {count} Add on licenses '{feature}'.
- Cannot delete file {file}
- Cannot complete patch installation. \n{text}
- Cannot complete customization, possibly due to a scripting runtime error or invalid script parameters.
- 'DRS Disabled' is the only supported DRS behavior for Fault Tolerance virtual machine {vmName}.
- The manually assigned WWN {wwn} are in conflict with the WWN used by {name}.
- Migration will cause the virtual machine's configuration to be modified, to preserve the CPU feature requirements for its guest OS.
- Invalid operation for device '{deviceIndex}'.
- Virtual machine is configured to use a device that prevents the snapshot operation: {fault.msg}
- Detected an invalid snapshot configuration.
- Virtual machine has {memorySizeMB} megabytes of memory, which is outside the range of {minMemorySizeMB} to {maxMemorySizeMB} megabytes supported on the host. This may be a general limitation of the host software, or specific to the guest OS selected for the virtual machine.
- Cloning this virtual machine from a snapshot point is not supported.
- The administrator permission is enabled on the host
- Hardware compatibility check is disabled.
- An error occurred with the Fault Tolerance configuration.
- Cannot complete client certificate validation.
- The host cannot be admitted to the cluster's current Enhanced vMotion Compatibility mode. Powered-on or suspended virtual machines on the host may be using CPU features hidden by that mode.
- Required patch or library is not installed.
- Cannot move a VM with native delta disk backing.
- Moving a powered on virtual machine with snapshots is not supported.
- Snapshot not taken since the state of the virtual machine has not changed since the last snapshot operation.
- The vCenter extension '{extensionName}' returned a section with an unbound prefix '{prefix}'
- One or more properties are referring to an unknown network '{network}'.
- Storage DRS initial placement cannot be completed until existing virtual disks are migrated with Storage vMotion.
- Error upgrading VMware Tools.
- Insufficient capacity on each physical CPU.
- Host property '{property}' value '{value}' could not be parsed.
- Invalid or unknown locale provided.
- Read failed on backup blob for {entityType}: {entityName}.
- Snapshot directory settings will be reset to the VM's home directory after the migration.
- CBRC-enabled disk '{device}' is not supported for Fault Tolerance."
- Moving a virtual machine that has snapshots is not supported.
- {connected.@enum.fault.NIC.connected} '{device}' cannot use network '{backing}', because {reason.@enum.fault.CannotUseNetwork.Reason}.
- The provided configuration contains duplicate entries for disk: '{device}'.
- Virtual disk '{device}' is a mapped direct-access LUN in physical compatibility mode; converting it to a different disk type is not supported for this operation.
- Host did not have any virtual network defined.
- There are storage paths available only through this VMkernel virtual NIC adapter {vnicDevice}.
- Cannot mount the virtual disk.
- Cannot apply the host configuration.
- A customization operation was performed on a Linux source virtual machine that was not shut down correctly.
- Host cannot be added to the cluster because it would result in the Primary and Secondary VMs in the same Fault Tolerance pair belonging to different clusters. Recommend adding the host to the same cluster where the other VM in the same Fault Tolerance pair has been added.
- The specified virtual disk or disk chain could not be locked. This might be caused when other operations hold the lock.
- A non-volatile registry subkey cannot be created under a volatile registry parent key.
- 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 VMs to another host or disable this restriction by setting the vSphere HA advanced option das.maxFtVCpusPerHost to 0.
- Virtual machine uses an unsupported type of virtual disk backing.
- Storage DRS is disabled on the virtual machine.
- vMotion is not licensed for the {atSourceHost.@enum.fault.VMotion.atSourceHost} host '{failedHost}'.
- Virtual machine requires {numCpuVm} CPUs to operate, but the host hardware only provides {numCpuDest}.
- The selected Enhanced vMotion Compatibility mode cannot be enabled, because the cluster contains hosts with CPU hardware that does not support that mode.
- Multiple snapshots are not supported for the host.
- An error occurred because the specified guest registry key was either not valid or not found. Check the root HKEY for validity.
- Host does not support the virtual hardware configuration of virtual machine.
- Datastore '{name}' is not accessible. {detail.@enum.fault.InaccessibleDatastore.Reason}
- Host '{hostName}' is not compatible with the vSphere Replication configuration supported by the virtual machine '{vmName}': {reason.@enum.fault.IncompatibleHostForVmReplication.IncompatibleReason}.
- A snapshot operation cannot be performed.
- Property '{label}' must be configured for the VM to power on.
- The namespace is full.
- VMFS volume could not be mounted as it may be missing an extent or multiple copies exist.
- The virtual machine requires hardware features that are unsupported or disabled on the target host. Incompatibility at CPUID level '{level}', register '{registerName}' with value '{registerValue}'. Required bits: '{desiredRegisterValue}'.
- A generic property fault for {id}.
- Invalid network {value} in property {id}.
- Unable to access file {file} since it is locked
- CPU hot plug is not supported for this virtual machine.
- The VMkernel virtual NIC adapter {vnicDevice} has multiple physical uplinks.
- Licensable entity does not exist.
- Insufficient resources.
- You cannot change the virtual machine's storage placement and its execution host at the same time on this {atSourceHost.@enum.fault.VMotion.atSourceHost} host '{failedHostName}'.
- Virtual disk '{device}' is a mapped direct-access LUN and larger than 2 TB. This configuration is not supported on the datastore '{datastoreName}'.
- The operation cannot be performed because the Record/Replay capability has not been enabled for the virtual machine.
- Line {lineNumber}: Invalid property value '{value}'.
- The datastore '{datastoreName}' is connected to one or more pre-4.1 hosts that do not support Storage I/O Control.
- Failed to read resource pool tree from host.
- {reason}
- Virtual disk '{device}' is a mapped direct-access LUN which has only limited support on the destination host; after migration, the virtual machine properties would incorrectly display the disk as a virtual disk.
- Insufficient resources on gateway server '{gatewayType}:{gatewayId}'.
- The operation is not allowed in the current state of the datastore.
- No guest OS heartbeats are being received. Either the guest OS is not responding or VMware Tools is not configured correctly.
- The host is reporting errors in its attempts to provide vSphere HA support.
- The {atSourceHost.@enum.fault.VMotion.atSourceHost} host '{failedHost}' does not support vMotion.
- The virtual machine requires hardware features that are unsupported or disabled on the target host:\n{sse3.@enum.fault.CpuIncompatible1ECX.sse3}{pclmulqdq.@enum.fault.CpuIncompatible1ECX.pclmulqdq}{ssse3.@enum.fault.CpuIncompatible1ECX.ssse3}{sse41.@enum.fault.CpuIncompatible1ECX.sse41}{sse42.@enum.fault.CpuIncompatible1ECX.sse42}{aes.@enum.fault.CpuIncompatible1ECX.aes}{otherOnly.@enum.fault.CpuIncompatible1ECX.otherOnly}\nIf possible, use a cluster with Enhanced vMotion Compatibility (EVC) enabled; see KB article 1003212.\n\nCPUID details: incompatibility at level {level,x} register '{registerName}'.\nHost bits: {registerBits}\nRequired: {desiredBits}
- The current DRS migration priority setting prevents generating a recommendation to correct the soft VM/Host affinity rules constraint violation for VM '{vmName}'.
- DRS was unable to place the virtual machines of a prerequisite power on group.
- The amount of graphics resource available in the parent resource pool is insufficient for the operation.
- The guest operating system agent has been configured to disable the operation.
- Unknown vSAN disk error '{device}'.
- The uploaded license content is not valid.
- An error occurred in the open source components during volume editing.
- If this operation is performed, the virtual machine will lose vSphere HA protection. If you proceed with this operation and it completes successfully, {resolution.@enum.fault.WillLoseHAProtection.Resolution}.
- Host '{hostName}' has a component failure. {componentType.@enum.fault.HostHasComponentFailure.HostComponentType} '{componentName}' is inaccessible.
- The licensing limit on the number of running virtual machines has been reached.
- Host '{hostName}' does not support vSAN.
- Virtual disk '{device}' is a mapped direct-access LUN that is not accessible.
- A component of the virtual machine is not accessible on the host.
- The Fault Tolerance configuration of the entity {entityName} has an issue: {reason.@enum.VmFaultToleranceConfigIssue.ReasonForIssue}.
- Only virtual machines on eight different hosts can have a single virtual disk backing opened for read at once.
- Cannot enable vSphere HA VM Component Protection for the specified cluster, because it contains a host {hostName} with {reason.@enum.fault.CannotEnableVmcpForCluster.Reason}.
- The vMotion interface is not enabled on this host.
- {description}
- Virtual machine uses {diskCount} disk(s); for a vMotion involving ESX 2.x hosts, high disk count will lead to longer vMotion durations and possibly time-outs.
- No host is compatible with the virtual machine.
- Virtual machine has {memorySizeMB} megabytes of memory, which is larger than the maximum {maxMemorySizeMB} megabytes supported by the datastore.
- Cannot determine the target system type.
- Certain disks in the host do not support checksum.
- The specified operating system identifier '{ovfDescription}' (id: {ovfId}) is not supported on the selected host. It will be mapped to the following OS identifier: '{targetDescription}'.
- 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.
- Patch is already installed on the host.
- At least one virtual disk is required for the operation to succeed.
- Storage DRS is unable to move virtual machine files from the datastore.
- Cannot initialize property '{id}'. Network '{value}' has no associated network protocol profile.
- CPU feature requirements for the guest OS are different on the destination host, and that host does not support modifying the virtual machine's configuration to mask those differences.
- The requested virtual machine metadata is not accessible.
- Moving a virtual machine that has snapshots is not supported when placing disks somewhere other than the virtual machine's new home datastore.
- Storage DRS is unable to move virtual machines with no files specified in the layout.
- Unsupported property type '{type}' with value '{value}'.
- Line {lineNumber}: Backing '{backingName}' is not supported by device '{deviceName}'.
- Line {lineNumber}: Syntax error in qualifier specification '{qualifier}'.
- The virtual machine version is not compatible with the version of the host '{hostName}'.
- Policy URN not found or is invalid: {urn}
- A gateway has not been configured.
- Storage DRS IO load balancing component was not run due to an unsupported configuration or insufficient information about datastores or virtual disks.
- Cannot configure NAS datastore '{name}' on '{remoteHost}:{remotePath}' for user '{userName}'.\nMultiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again. (1219)
- Customization of the guest operating system '{uncustomizableGuestOS}' is not supported in this configuration. Microsoft Vista (TM) and Linux guests with Logical Volume Manager are supported only for recent ESX host and VMware Tools versions. Refer to vCenter documentation for supported configurations.
- There are insufficient memory resources on standby hosts (if any) to meet the requirements of a given operation.
- Cannot install the vCenter Server agent service. {reason.@enum.fault.AgentInstallFailed.Reason}
- Insufficient resources to satisfy configured failover level for vSphere HA.
- sIgNaTuRe
- An error occurred because the specified guest registry value was not found.
- Line {lineNumber}: Duplicate qualifier was found '{qualifier}'.
- The ISO image '{filename}' is connected to device '{device.deviceInfo.label}'. The ISO image is not included in the generated OVF package.
- Snapshot hierarchy is too deep.
- Authentication of connection to host {hostname} via gateway server failed. There are missing or wrong authentication parameters.
- Distributed port {portKey} cannot be used as both the source and destination in the same distributed port mirroring session with key {vspanSessionKey}.
- Cannot complete patch '{patch}' installation; reboot required.
- Virtual machine has {numCoresPerSocketVm} cores per socket, but the host only supports {maxSupportedCoresPerSocketDest}. The number of cores per socket may be limited by the guest OS selected for the virtual machine or by the licensing for the host.
- Host '{hostName}' does not support Fault Tolerance for virtual machine {vmName}, because the VM has a {deviceType.@enum.NotSupportedDeviceForFT.DeviceType} device '{deviceLabel}'. To use Fault Tolerance on this host, either upgrade host to ESX 4.1 or reconfigure the VM to not use this device.
- The vCenter extension '{extensionName}' returned an undeclared section: '{qualifiedSectionType}'
- Device '{device}' is a raw disk, which is not supported.
- Line {lineNumber}: Invalid value '{value}' for element '{name}'.
- The vCenter Server is unable to decrypt passwords stored in the customization specification.
- Cannot add a host with virtual machines that have Fault Tolerance turned on as a stand-alone host.
- Virtual machine '{vmName}' on host '{hostName}' would violate a virtual machine - host affinity rule.
- A value exceeded the acceptable range.
- Failed to authenticate with the guest operating system using the supplied credentials.
- Storage DRS is unable to move virtual machines with manually placed swap files.
- Host {hostName} has some Fault Tolerance issues for virtual machine {vmName}. Refer to the errors list for details.
- Virtual machine is not ready for the migration operation. {reason}
- Failed to copy the VMware Tools installation image to the guest operating system.
- The operation is not allowed in the current state of the host.
- The host's CPU vendor cannot be determined, so it cannot enter an Enhanced vMotion Compatibility cluster.
- Device '{device.deviceInfo.label}' cannot be exported.
- Profile validation failed. Check the profile for errors.
- The VMkernel virtual NIC adapter {vnicDevice} does not exist.
- Line {lineNumber}: Unsupported value '{value}' for attribute '{attributeName}' on element '{elementName}'.
- The requested Storage vMotion would move a virtual machine's disks without assigning the virtual machine a new home, but such a move is not supported on the {atSourceHost.@enum.fault.VMotion.atSourceHost} host '{failedHostName}'.
- {connected.@enum.fault.NIC.connected} '{device}' uses network '{backing}', which is not accessible.
- Failed to export OVF package.
- The guest operations agent is out of date.
- {connected.@enum.fault.NIC.connected} '{device}' uses dvPort '{backing}', which is a conflict port.
- This host is currently being managed by the vCenter Server with IP address '{ipAddress}'. Changes made to this host during this session may not be reflected in vSphere Client sessions currently viewing vCenter Server.
- ESX 5.1 or later is required for Intel 'Ivy Bridge' Generation mode, AMD Opteron 'Piledriver' Generation mode, and later EVC modes.
- Cannot connect to remote registry.
- VMI is enabled for the virtual machine, but VMI is not supported on the host.
- Cannot issue a new session ticket because the maximum number of tickets have been issued.
- The host is not compatible with the virtual machine.
- Failed to deploy OVF package.
- Virtual machine has {memorySizeMB} megabytes of memory, which is outside the recommended range of {minMemorySizeMB} to {maxMemorySizeMB} megabytes for the virtual machine's guest OS.
- The vMotion interface on the {atSourceHost.@enum.fault.VMotion.atSourceHost} host '{failedHost}' has an unknown error.
- A warning or error occurred when migrating the virtual machine.
- Line {lineNumber}: Duplicate element '{name}'.
- The virtual machine is not supported on the target datastore.
- The specified vSphere Authentication Proxy server is not reachable, or has denied access to the service.
- This operation is not supported on a Secondary VM of a Fault Tolerant pair.
- An in progress operation on FT VM {vmName} is blocking this operation. Please retry operation again.
- Cannot allocate IP address for property '{label}'. Network '{value}' has no associated network protocol profile.
- The cluster cannot be configured with the selected Enhanced vMotion Compatibility mode; CPU features disabled by that mode may currently be in use by powered-on or suspended virtual machines in the cluster.
- The virtual machine has virtual disk, '{device}', in linked-clone mode that prevents migration.
- The disk {name} has already been enabled as a Universal Point-in-Time storage object.
- vCenter does not support hosts of this type ({productName} {productVersion}).
- There are insufficient CPU resources on standby hosts (if any) to meet the requirements of a given operation.
- The {property} exceeds the limit {limit}.
- Host '{hostName}' is of type ({productName} {productVersion}) with build {build}, it does not support vSphere HA clustering features and cannot be part of vSphere HA clusters.
- The virtual machine is running in a monitor mode that is incompatible for Fault Tolerance.
- General vSAN error.
- Migration will involve moving one or more virtual machine files to another datastore, which is not permitted when the source host is in maintenance mode.
- '{count}' of device '{device}' was found. Only '{max}' allowed.
- The virtual machine has CPU and/or memory affinities configured, which is preventing vMotion.
- Virtual machine has {numCpuVm} virtual CPUs, but the host only supports {maxSupportedVcpusDest}. The number of virtual CPUs may be limited by the guest OS selected for the virtual machine or by the licensing for the host.
- Promiscuous distributed port {portKey} cannot be used as the transmitted source or destination in the distributed port mirroring session with key {vspanSessionKey}.
- The CPU pair is not compatible for fault tolerance:\n{model.@enum.fault.FaultToleranceCpuIncompatible.model}{family.@enum.fault.FaultToleranceCpuIncompatible.family}{stepping.@enum.fault.FaultToleranceCpuIncompatible.stepping}\nSee KB 1008027.
- Operation cannot be performed while a vApp operation is in progress.
- Attempted to power on a virtual machine with the .vmx file not stored on a NAS or VMFS version 3 datastore. The virtual machine files must be relocated or VMFS upgraded.
- Cannot complete operation due to concurrent modification by another operation.
- The available network bandwidth in resource pool '{resourcePoolKey}' of distributed switch '{dvsName}' is '{available}' MBps, which is less than the requested bandwidth of '{requested}' MBps.
- Cannot set the vSphere HA restart priority to 'Disabled' for the Fault Tolerance VM {vmName}.
- Cannot complete template upgrade for {name} ({path}).\n{reason.msg}
- The specified key '{key}' is not valid.
- The specified host is not compatible with the Fault Tolerance Secondary VM.
- Cannot perform this operation due to a license restriction. Either the license edition of the ESXi host does not support this operation, or the vCenter Server system that manages the host has a license that restricts this operation through a direct connection to this host. Check the licensed features for the host or connect to vCenter Server and retry the operation.
- The backing for the specified virtual device is not supported.
- {connected.@enum.fault.NIC.connected} '{device}' uses network '{backing}', which is a 'virtual intranet'.
- Storage DRS is unable to move virtual machines in fault-tolerance pairs.
- Incorrect host name or the host name cannot be resolved by either DNS or NetBios.
- The license server is not configured to perform the operation.
- Cannot change non-promiscuous distributed port {portKey} to promiscuous mode. The distributed port is used as a transmitted source or destination port in a distributed port mirroring session.
- Number of virtual devices exceeds the maximum for a given controller.
- The VMkernel virtual NIC adapter {vnicDevice} has no physical uplinks.
- An error occurred in the common Message Bus Proxy service.
- Host '{hostName}' does not support the virtual memory file type.
- Virtual flash module '{moduleName}' on virtual machine '{vmName}'is not supported by host '{hostName}': {reason.@enum.fault.VFlashModuleNotSupported.Reason}. Refer to host configuration for supported virtual flash module configuration options.
- An error occurred processing an operation in the guest operating system.
- Wake-on-LAN is not supported by the vMotion NIC on this host.
- The virtual machine's guest operating system does not support auto-upgrade of VMware Tools.
- Storage DRS is unable to move virtual machine templates.
- Unable to access local licensing configuration.
- The specified key, name, or identifier '{name}' already exists.
- This edition of vCenter only supports {capacity} host(s) in the inventory. Remove some hosts from the inventory before performing the operation.
- The floppy image '{filename}' is connected to device '{device.deviceInfo.label}'. The image is not included in the generated OVF package.
- Cannot change the DRS behavior for Fault Tolerance Secondary VM {vmName}.
- The virtual machine is pinned to a host.
- The operation exceeds a limit.
- Multi-writer mode enabled disk '{device}' is not supported for Fault Tolerance.
- File {file} is larger than the maximum size supported by datastore '{datastore}'
- Only connected hosts can enter an Enhanced vMotion Compatibility cluster.
- The name '{name}' already exists.
- The host {name} is already connected to this vCenter Server.
- The specified delta disk format '{deltaDiskFormat}' is not supported.
- Host did not provide enough information to acquire the correct set of licenses.
- The vMotion interface of the destination host uses network '{destNetwork}', which differs from the network '{sourceNetwork}' used by the vMotion interface of the source host.
- Cannot complete login due to an incorrect user name or password.
- Unshared swap vMotion is not supported.
- Cannot complete customization.
- The vCenter extension '{extensionName}' returned an invalid section. Details: '{description}'
- An invalid format was detected.
- An error occurred while communicating with the vCenter extension '{extensionName}'. Details: '{description}'
- Line {lineNumber}: Incorrect namespace '{namespaceName}' found.
- Virtual disk '{device}' is a mapped direct-access LUN and larger than two TB; converting it to a different disk type is not supported for this operation.
- vMotion interface '{network}' on the {atSourceHost.@enum.fault.VMotion.atSourceHost} host '{failedHost}' does not have the recommended capacity (full duplex / 1000 Mbps) to properly support vMotion.
- The vSAN host cannot be moved to the destination cluster: unknown error.
- Unsupported device backing for device '{device.deviceInfo.label}'.
- The guest operating system does not support the operation.
- vMotion from source host to destination host is unsupported because of vMotion protocol differences.
- Invalid datastore format '{name}'.
- Flash disk '{devicePath}' is not available. It is either in use or it is not a flash-based disk.
- Storage DRS does not move manually placed virtual machines.
- Cannot complete the configuration of the vSphere HA agent on the host. {reason.@enum.fault.DasConfigFault.DasConfigFaultReason}.
- The Fault Tolerance configuration of the entity {entityName} has an issue: check the error property for details.
- Limit for number of concurrent native clones on file {file} has been reached.
- An error occurred while accessing or modifying a Windows guest registry key.
- Incorrect file type for file {file}
- Errors in Active Directory operations.
- Line {lineNumber}: Property with type '{type}' and value '{value}' refers to a non-existing network.
- Cannot complete acquiring {count} Edition licenses '{feature}'.
- Storage DRS is unable to move disks in multi-writer mode.
- Device requires a controller.
- Unknown error encountered.
- Error encountered while wiping disk.
- Enhanced vMotion Compatibility (EVC) cannot be enabled because all hosts in the cluster must be ESX 5.1 or later to support Intel 'Ivy Bridge' Generation mode, AMD Opteron 'Piledriver' Generation mode, or later EVC modes.
- Unsupported version of the API: {version}
- The vSphere Replication configuration for disk with key {key} of the virtual machine has an issue: {reason.@enum.fault.ReplicationDiskConfigFault.ReasonForFault}
- Not enough disk space to enable vSAN on '{device}'.
- Cannot create a disk group without HDD disks or a flash disk. Each disk group needs at least one flash disk and one or multiple HDD disks
- vCenter Server cannot validate the identity of the host {hostName}
- Open source components required for Linux customization were not found on the server.
- The virtual machine has {numCpu} virtual CPUs and is not supported for {reason.@enum.fault.NumVirtualCpusIncompatible.Reason}.
- '{name}' is invalid or exceeds the maximum number of characters permitted.
- The vSAN host cannot be moved to the destination cluster: vSAN cluster UUID mismatch (host: {hostClusterUuid}, destination: {destinationClusterUuid}).
- The operation cannot be allowed at the current time because the virtual machine has a question pending:\n '{text}'.
- The change cannot be performed because it is not allowed by '{serviceName}'.
- Host {hostName} does not support virtual machines with Fault Tolerance turned on. \n{reason.@enum.fault.HostIncompatibleForFaultTolerance.Reason}
- The VMkernel virtual NIC adapter {vnicDevice} is currently used by iSCSI Host Bus Adapter.
- Cannot disable DRS on a cluster which is managed by a Virtual DataCenter
- The method is already disabled by '{sourceId}'
- The vSAN cluster UUID cannot be changed in the current state.
- Line {lineNumber}: The order of Disk elements in the DiskSection is not consistent with the order of the File references.
- Device '{device}' is not supported. {reason.@enum.fault.DeviceNotSupported.Reason}
- Cannot disable DRS on a cluster that contains vApps.
- No virtual NIC available.
- Fault Tolerance has not been licensed on host {hostName}, or the license does not support the number of vCPUs running on this VM.
- Internal error.
- The namespace is write protected.
- Access to resource settings on the host is restricted to the server that is managing it: '{managementServer}'.
- The disk is a USB disk: '{device}'.
- The Secondary VM with instanceUuid '{instanceUuid}' has already been enabled.
- Line {lineNumber}: Invalid OVF package.
- Storage DRS cannot relocate the disk as it is disabled for current state of VM.
- Licensable entity already exists.
- Limit for number of native clones on file {file} has been reached.
- There are configuration issues for the Fault Tolerance operation. Refer to the errors and warnings list for details.
- A challenge response is required to authenticate in the guest operating system.
- This snapshot is not revertible.
- An attempt was made to move or clone a disk with an uncommitted REDO log.
- The license assignment is disallowed because the inventory has standalone hosts that do not have the vCenter agent license
- The selected vSAN host UUID cannot be changed in the current state.
- Swap datastore is unset.
- The operation is not allowed in the current connection state of the host.
- The virtual machine uses network '{name}'. Since the operation is being conducted across datacenters, this network may not be the same network on the source and destination. This is because network names are only unique within a datacenter.
- A VMFS volume with the same UUID '{uuid}' is already mounted in the datacenter.
- The vSphere Replication configuration of the virtual machine has an issue: {reason.@enum.fault.ReplicationVmConfigFault.ReasonForFault}
- The input arguments had entities that did not belong to the same datacenter.
- DRS was unable to place all the virtual machines in the power on group.
- Extended fault.
- HTTP communication could not be completed with status {statusCode}
- Fault Tolerance VM {vmName} requires the disks to be scrubbed on the file system.
- Cannot contact the specified host ({name}). The host may not be available on the network, a network configuration problem may exist, or the management services on this host may not be responding.
- BMC user does not have the necessary privileges.
- No virtual machines have been configured to power off.
- A required migration feature is not supported on the {atSourceHost.@enum.fault.VMotion.atSourceHost} host '{failedHostName}'.
- Storage DRS is unable to move virtual machines placed in user folders.
- Line {lineNumber}: Unsupported section '{name}' ({info}).
- Line {lineNumber}: Missing child element '{name}'.
- The resource '{name}' is in use.
- The unused disk blocks of the virtual machine's disks have not been scrubbed on the file system.\nThis is needed to support features like Fault Tolerance.
- The Fault Tolerance Secondary VM was not powered on because the Fault Tolerance Primary VM could not be powered on.
- vSphere Replication operation error: {reason.@enum.fault.ReplicationVmFault.ReasonForFault}
- vSphere Replication and Fault Tolerance cannot be enabled on the same virtual machine.
- The session is not authenticated.
- Virtual Flash Read Cache is not supported for a virtual disk stored on a '{type}' datastore: '{datastoreName}'.