vCenter Events




Key Description Category FormatOnDatacenter FormatOnComputeResource FormatOnHost FormatOnVm Message
Key Description Category FormatOnDatacenter FormatOnComputeResource FormatOnHost FormatOnVm Message
AccountCreatedEvent Account created info An account was created Account {spec.id} was created on host {host.name}
AccountRemovedEvent Account removed info Account {account} was removed Account {account} was removed on host {host.name}
AccountUpdatedEvent Account updated info An account was updated Account {spec.id} was updated on host {host.name}
AdminPasswordNotChangedEvent Administrator password not changed info The default password for the root user has not been changed The default password for the root user on the host {host.name} has not been changed
AlarmAcknowledgedEvent Alarm acknowledged info Acknowledged alarm '{alarm.name}' on {entity.name} Acknowledged alarm '{alarm.name}' on {entity.name} Acknowledged alarm '{alarm.name}' on {entity.name} Acknowledged alarm '{alarm.name}' Acknowledged alarm '{alarm.name}' on {entity.name}
AlarmActionTriggeredEvent Alarm action triggered info Alarm '{alarm.name}' on {entity.name} triggered an action Alarm '{alarm.name}' on {entity.name} triggered an action Alarm '{alarm.name}' on {entity.name} triggered an action
AlarmClearedEvent Alarm cleared info Manually cleared alarm '{alarm.name}' on {entity.name} from {from.@enum.ManagedEntity.Status} Manually cleared alarm '{alarm.name}' on {entity.name} from {from.@enum.ManagedEntity.Status} Manually cleared alarm '{alarm.name}' on {entity.name} from {from.@enum.ManagedEntity.Status} Manually cleared alarm '{alarm.name}' from {from.@enum.ManagedEntity.Status} Manually cleared alarm '{alarm.name}' on {entity.name} from {from.@enum.ManagedEntity.Status}
AlarmCreatedEvent Alarm created info Created alarm '{alarm.name}' on {entity.name} Created alarm '{alarm.name}' on {entity.name} Created alarm '{alarm.name}' on {entity.name} Created alarm '{alarm.name}' Created alarm '{alarm.name}' on {entity.name}
AlarmEmailCompletedEvent Alarm email sent info Alarm '{alarm.name}' on {entity.name} sent email to {to} Alarm '{alarm.name}' on {entity.name} sent email to {to} Alarm '{alarm.name}' on {entity.name} sent email to {to} Alarm '{alarm.name}' sent email to {to} Alarm '{alarm.name}' on {entity.name} sent email to {to}
AlarmEmailFailedEvent Cannot send alarm email error Alarm '{alarm.name}' on {entity.name} cannot send email to {to} Alarm '{alarm.name}' on {entity.name} cannot send email to {to} Alarm '{alarm.name}' on {entity.name} cannot send email to {to} Alarm '{alarm.name}' cannot send email to {to} Alarm '{alarm.name}' on {entity.name} cannot send email to {to}
AlarmReconfiguredEvent Alarm reconfigured info Reconfigured alarm '{alarm.name}' on {entity.name} Reconfigured alarm '{alarm.name}' on {entity.name} Reconfigured alarm '{alarm.name}' on {entity.name} Reconfigured alarm '{alarm.name}' Reconfigured alarm '{alarm.name}' on {entity.name}
AlarmRemovedEvent Alarm removed info Removed alarm '{alarm.name}' on {entity.name} Removed alarm '{alarm.name}' on {entity.name} Removed alarm '{alarm.name}' on {entity.name} Removed alarm '{alarm.name}' Removed alarm '{alarm.name}' on {entity.name}
AlarmScriptCompleteEvent Alarm script completed info Alarm '{alarm.name}' on {entity.name} ran script {script} Alarm '{alarm.name}' on {entity.name} ran script {script} Alarm '{alarm.name}' on {entity.name} ran script {script} Alarm '{alarm.name}' ran script {script} Alarm '{alarm.name}' on {entity.name} ran script {script}
AlarmScriptFailedEvent Alarm script not completed error Alarm '{alarm.name}' on {entity.name} did not complete script: {reason.msg} Alarm '{alarm.name}' on {entity.name} did not complete script: {reason.msg} Alarm '{alarm.name}' on {entity.name} did not complete script: {reason.msg} Alarm '{alarm.name}' did not complete script: {reason.msg} Alarm '{alarm.name}' on {entity.name} did not complete script: {reason.msg}
AlarmSnmpCompletedEvent Alarm SNMP trap sent info Alarm '{alarm.name}': an SNMP trap for entity {entity.name} was sent Alarm '{alarm.name}': an SNMP trap for entity {entity.name} was sent Alarm '{alarm.name}': an SNMP trap for entity {entity.name} was sent Alarm '{alarm.name}': an SNMP trap was sent Alarm '{alarm.name}': an SNMP trap for entity {entity.name} was sent
AlarmSnmpFailedEvent Alarm SNMP trap not sent error Alarm '{alarm.name}' on entity {entity.name} did not send SNMP trap: {reason.msg} Alarm '{alarm.name}' on entity {entity.name} did not send SNMP trap: {reason.msg} Alarm '{alarm.name}' on entity {entity.name} did not send SNMP trap: {reason.msg} Alarm '{alarm.name}' did not send SNMP trap: {reason.msg} Alarm '{alarm.name}' on entity {entity.name} did not send SNMP trap: {reason.msg}
AlarmStatusChangedEvent Alarm status changed info Alarm '{alarm.name}' on {entity.name} changed from {from.@enum.ManagedEntity.Status} to {to.@enum.ManagedEntity.Status} Alarm '{alarm.name}' on {entity.name} changed from {from.@enum.ManagedEntity.Status} to {to.@enum.ManagedEntity.Status} Alarm '{alarm.name}' on {entity.name} changed from {from.@enum.ManagedEntity.Status} to {to.@enum.ManagedEntity.Status} Alarm '{alarm.name}' changed from {from.@enum.ManagedEntity.Status} to {to.@enum.ManagedEntity.Status} Alarm '{alarm.name}' on {entity.name} changed from {from.@enum.ManagedEntity.Status} to {to.@enum.ManagedEntity.Status}
AllVirtualMachinesLicensedEvent All virtual machines are licensed info All running virtual machines are licensed
AlreadyAuthenticatedSessionEvent Already authenticated info User cannot logon since the user is already logged on
BadUsernameSessionEvent Invalid user name error Cannot login {userName}@{ipAddress}
CanceledHostOperationEvent Canceled host operation info The operation performed on host {host.name} was canceled The operation performed on host {host.name} was canceled The operation was canceled The operation performed on host {host.name} in {datacenter.name} was canceled
ChangeOwnerOfFileEvent Change owner of file info Changed ownership of file name {filename} from {oldOwner} to {newOwner} on {host.name} in cluster {computeResource.name}. Changed ownership of file name {filename} from {oldOwner} to {newOwner} on {host.name}. Changed ownership of file name {filename} from {oldOwner} to {newOwner}. Changed ownership of file name {filename} from {oldOwner} to {newOwner} on {host.name} in {datacenter.name}.
ChangeOwnerOfFileFailedEvent Cannot change owner of file name error Cannot change ownership of file name {filename} from {owner} to {attemptedOwner} on {host.name} in cluster {computeResource.name}. Cannot change ownership of file name {filename} from {owner} to {attemptedOwner} on {host.name}. Cannot change ownership of file name {filename} from {owner} to {attemptedOwner}. Cannot change ownership of file name {filename} from {owner} to {attemptedOwner} on {host.name} in {datacenter.name}.
ClusterComplianceCheckedEvent Checked cluster for compliance info Checked cluster {computeResource.name} for compliance Cluster was checked for compliance with profile {profile.name} Checked cluster for compliance
ClusterCreatedEvent Cluster created info Created cluster {computeResource.name} Created in folder {parent.name} Created cluster {computeResource.name} in {datacenter.name}
ClusterDestroyedEvent Cluster deleted info Removed cluster {computeResource.name} Removed cluster Removed cluster {computeResource.name} in datacenter {datacenter.name}
ClusterOvercommittedEvent Cluster overcommitted error Insufficient capacity in cluster {computeResource.name} to satisfy resource configuration Insufficient capacity to satisfy resource configuration Insufficient capacity in cluster {computeResource.name} to satisfy resource configuration in {datacenter.name}
ClusterReconfiguredEvent Cluster reconfigured info Reconfigured cluster {computeResource.name} Cluster reconfigured Reconfigured cluster {computeResource.name} in datacenter {datacenter.name}
ClusterStatusChangedEvent Cluster status changed info Configuration status on cluster {computeResource.name} changed from {oldStatus.@enum.ManagedEntity.Status} to {newStatus.@enum.ManagedEntity.Status} Configuration status changed from {oldStatus.@enum.ManagedEntity.Status} to {newStatus.@enum.ManagedEntity.Status} Configuration status on cluster {computeResource.name} changed from {oldStatus.@enum.ManagedEntity.Status} to {newStatus.@enum.ManagedEntity.Status} in {datacenter.name}
CustomFieldDefAddedEvent Custom field definition added info Created new custom field definition {name}
CustomFieldDefRemovedEvent Custom field definition removed info Removed field definition {name}
CustomFieldDefRenamedEvent Custom field definition renamed info Renamed field definition from {name} to {newName}
CustomFieldValueChangedEvent Custom field value changed info Changed custom field {name} on {entity.name} to {value} Changed custom field {name} on {entity.name} to {value} Changed custom field {name} on {entity.name} to {value} Changed custom field {name} to {value} Changed custom field {name} on {entity.name} in {datacenter.name} to {value}
CustomizationFailed info Cannot complete customization Cannot complete customization of VM {vm.name}. See customization log at {logLocation} on the guest OS for details.
CustomizationLinuxIdentityFailed Customization Linux Identity Failed error An error occurred while setting up Linux identity. See log file '{logLocation}' on guest OS for details.
CustomizationNetworkSetupFailed Cannot complete customization network setup error An error occurred while setting up network properties of the guest OS. See the log file {logLocation} in the guest OS for details.
CustomizationStartedEvent Started customization info Started customization of VM {vm.name}. Customization log located at {logLocation} in the guest OS.
CustomizationSucceeded Customization succeeded info Customization of VM {vm.name} succeeded. Customization log located at {logLocation} in the guest OS.
CustomizationSysprepFailed Cannot complete customization Sysprep error The version of Sysprep {sysprepVersion} provided for customizing VM {vm.name} does not match the version of guest OS {systemVersion}. See the log file {logLocation} in the guest OS for more information.
CustomizationUnknownFailure Unknown customization error error An error occurred while customizing VM {vm.name}. For details reference the log file {logLocation} in the guest OS.
DasAdmissionControlDisabledEvent vSphere HA admission control disabled info vSphere HA admission control disabled for cluster {computeResource.name} vSphere HA admission control disabled vSphere HA admission control disabled for cluster {computeResource.name} in {datacenter.name}
DasAdmissionControlEnabledEvent vSphere HA admission control enabled info vSphere HA admission control enabled for cluster {computeResource.name} vSphere HA admission control enabled vSphere HA admission control enabled for cluster {computeResource.name} in {datacenter.name}
DasAgentFoundEvent vSphere HA agent found info Re-established contact with a primary host in this vSphere HA cluster
DasAgentUnavailableEvent vSphere HA agent unavailable error Unable to contact a primary vSphere HA agent in cluster {computeResource.name} Unable to contact a primary vSphere HA agent Unable to contact a primary vSphere HA agent in cluster {computeResource.name} in {datacenter.name}
DasClusterIsolatedEvent All vSphere HA hosts isolated error All hosts in the vSphere HA cluster {computeResource.name} were isolated from the network. Check the network configuration for proper network redundancy in the management network All hosts in the vSphere HA cluster were isolated from the network. Check the network configuration for proper network redundancy in the management network All hosts in the vSphere HA cluster were isolated from the network. Check the network configuration for proper network redundancy in the management network All hosts in the vSphere HA cluster {computeResource.name} in {datacenter.name} were isolated from the network. Check the network configuration for proper network redundancy in the management network.
DasDisabledEvent vSphere HA disabled for cluster info vSphere HA disabled for cluster {computeResource.name} vSphere HA disabled for this cluster vSphere HA disabled for cluster {computeResource.name} in {datacenter.name}
DasEnabledEvent vSphere HA enabled for cluster info vSphere HA enabled for cluster {computeResource.name} vSphere HA enabled for this cluster vSphere HA enabled for cluster {computeResource.name} in {datacenter.name}
DasHostFailedEvent vSphere HA host failed error A possible host failure has been detected by vSphere HA on {failedHost.name} A possible host failure has been detected by vSphere HA on {failedHost.name} A possible host failure has been detected by vSphere HA on {failedHost.name} in cluster {computeResource.name} in {datacenter.name}
DasHostIsolatedEvent vSphere HA host isolated warning Host {isolatedHost.name} has been isolated from cluster {computeResource.name} Host {isolatedHost.name} has been isolated Host has been isolated from cluster Host {isolatedHost.name} has been isolated from cluster {computeResource.name} in {datacenter.name}
DatacenterCreatedEvent Datacenter created info Created in folder {parent.name} Created datacenter {datacenter.name} Created datacenter {datacenter.name} in folder {parent.name}
DatacenterRenamedEvent Datacenter renamed info Renamed datacenter Renamed datacenter from {oldName} to {newName} Renamed datacenter from {oldName} to {newName}
DatastoreCapacityIncreasedEvent Datastore capacity increased info Datastore {datastore.name} increased in capacity from {oldCapacity} bytes to {newCapacity} bytes Datastore {datastore.name} increased in capacity from {oldCapacity} bytes to {newCapacity} bytes in {datacenter.name}
DatastoreDestroyedEvent Datastore deleted info Removed unconfigured datastore {datastore.name} Removed unconfigured datastore {datastore.name}
DatastoreDiscoveredEvent Datastore discovered info Discovered datastore {datastore.name} on {host.name} Discovered datastore {datastore.name} on {host.name} Discovered datastore {datastore.name} Discovered datastore {datastore.name} on {host.name} in {datacenter.name}
DatastoreDuplicatedEvent Datastore duplicated error Multiple datastores named {datastore} detected on host {host.name} Multiple datastores named {datastore} detected on host {host.name} Multiple datastores named {datastore} detected Multiple datastores named {datastore} detected on host {host.name} in {datacenter.name}
DatastoreFileCopiedEvent File or directory copied to datastore info File or directory {sourceFile} copied from {sourceDatastore.name} to {datastore.name} as {targetFile} File or directory {sourceFile} copied from {sourceDatastore.name} to {datastore.name} as {targetFile}
DatastoreFileDeletedEvent File or directory deleted info File or directory {targetFile} deleted from {datastore.name} File or directory {targetFile} deleted from {datastore.name}
DatastoreFileMovedEvent File or directory moved to datastore info File or directory {sourceFile} moved from {sourceDatastore.name} to {datastore.name} as {targetFile} File or directory {sourceFile} moved from {sourceDatastore.name} to {datastore.name} as {targetFile}
DatastoreIORMReconfiguredEvent Reconfigured Storage I/O Control on datastore info Reconfigured Storage I/O Control on datastore {datastore.name} Reconfigured Storage I/O Control on datastore {datastore.name} Reconfigured Storage I/O Control on datastore {datastore.name} Reconfigured Storage I/O Control on datastore {datastore.name} Reconfigured Storage I/O Control on datastore {datastore.name}
DatastorePrincipalConfigured Datastore principal configured info Configured datastore principal {datastorePrincipal} on host {host.name} Configured datastore principal {datastorePrincipal} on host {host.name} Configured datastore principal {datastorePrincipal} Configured datastore principal {datastorePrincipal} on host {host.name} in {datacenter.name}
DatastoreRemovedOnHostEvent Datastore removed from host info Removed datastore {datastore.name} from {host.name} Removed datastore {datastore.name} Removed datastore {datastore.name} from {host.name} in {datacenter.name}
DatastoreRenamedEvent Datastore renamed info Renamed datastore from {oldName} to {newName} Renamed datastore from {oldName} to {newName} in {datacenter.name}
DatastoreRenamedOnHostEvent Datastore renamed from host info Renamed datastore from {oldName} to {newName} Renamed datastore from {oldName} to {newName} in {datacenter.name}
DrsDisabledEvent DRS disabled info Disabled DRS on cluster {computeResource.name} Disabled DRS Disabled DRS on cluster {computeResource.name} in datacenter {datacenter.name}
DrsEnabledEvent DRS enabled info Enabled DRS on cluster {computeResource.name} with automation level {behavior} Enabled DRS with automation level {behavior} Enabled DRS on {computeResource.name} with automation level {behavior} in {datacenter.name}
DrsEnteredStandbyModeEvent DRS entered standby mode info DRS put {host.name} into standby mode DRS put {host.name} into standby mode DRS put the host into standby mode DRS put {host.name} into standby mode
DrsEnteringStandbyModeEvent DRS entering standby mode info DRS is putting {host.name} into standby mode DRS is putting {host.name} into standby mode DRS is putting the host into standby mode DRS is putting {host.name} into standby mode
DrsExitedStandbyModeEvent DRS exited standby mode info DRS moved {host.name} out of standby mode DRS moved {host.name} out of standby mode DRS moved the host out of standby mode DRS moved {host.name} out of standby mode
DrsExitingStandbyModeEvent DRS exiting standby mode info DRS is moving {host.name} out of standby mode DRS is moving {host.name} out of standby mode DRS is moving the host out of standby mode DRS is moving {host.name} out of standby mode
DrsExitStandbyModeFailedEvent DRS cannot exit the host out of standby mode error DRS cannot move {host.name} out of standby mode DRS cannot move {host.name} out of standby mode DRS cannot move the host out of standby mode DRS cannot move {host.name} out of standby mode
DrsInvocationFailedEvent DRS invocation not completed error DRS invocation not completed DRS invocation not completed DRS invocation not completed
DrsRecoveredFromFailureEvent DRS has recovered from the failure info DRS has recovered from the failure DRS has recovered from the failure DRS has recovered from the failure
DrsResourceConfigureFailedEvent Cannot complete DRS resource configuration error Unable to apply DRS resource settings on host. {reason.msg}. This can significantly reduce the effectiveness of DRS. Unable to apply DRS resource settings on host {host.name} in {datacenter.name}. {reason.msg}. This can significantly reduce the effectiveness of DRS.
DrsResourceConfigureSyncedEvent DRS resource configuration synchronized info Resource configuration specification returns to synchronization from previous failure Resource configuration specification returns to synchronization from previous failure on host '{host.name}' in {datacenter.name}
DrsRuleComplianceEvent VM is now compliant with DRS VM-Host affinity rules info {vm.name} on {host.name} is now compliant with DRS VM-Host affinity rules {vm.name} on {host.name} is now compliant with DRS VM-Host affinity rules {vm.name} is now compliant with DRS VM-Host affinity rules virtual machine on {host.name} is now compliant with DRS VM-Host affinity rules {vm.name} on {host.name} in {datacenter.name} is now compliant with DRS VM-Host affinity rules
DrsRuleViolationEvent VM is violating a DRS VM-Host affinity rule info {vm.name} on {host.name} is violating a DRS VM-Host affinity rule {vm.name} on {host.name} is violating a DRS VM-Host affinity rule {vm.name} is violating a DRS VM-Host affinity rule virtual machine on {host.name} is violating a DRS VM-Host affinity rule {vm.name} on {host.name} in {datacenter.name} is violating a DRS VM-Host affinity rule
DrsSoftRuleViolationEvent The VM is violating a DRS VM-Host soft affinity rule info {vm.name} on {host.name} is violating a DRS VM-Host soft affinity rule {vm.name} on {host.name} is violating a DRS VM-Host soft affinity rule {vm.name} is violating a DRS VM-Host soft affinity rule virtual machine on {host.name} is violating a DRS VM-Host soft affinity rule {vm.name} on {host.name} in {datacenter.name} is violating a DRS VM-Host soft affinity rule
DrsVmMigratedEvent DRS VM migrated info DRS migrated {vm.name} from {sourceHost.name} to {host.name} in cluster {computeResource.name} DRS migrated {vm.name} from {sourceHost.name} to {host.name} DRS migrated {vm.name} from {sourceHost.name} Migrated from {sourceHost.name} to {host.name} by DRS DRS migrated {vm.name} from {sourceHost.name} to {host.name} in cluster {computeResource.name} in {datacenter.name}
DrsVmPoweredOnEvent DRS VM powered on info DRS powered On {vm.name} on {host.name} DRS powered On {vm.name} on {host.name} DRS powered On {vm.name} DRS powered On the virtual machine on {host.name} DRS powered On {vm.name} on {host.name} in {datacenter.name}
DuplicateIpDetectedEvent Duplicate IP detected info Virtual machine {macAddress} has a duplicate IP {duplicateIP} Virtual machine {macAddress} on host {host.name} has a duplicate IP {duplicateIP}
DvpgImportEvent Import Operation event info Import operation with type {importType} was performed on {net.name} Import operation with type {importType} was performed on {net.name}
DvpgRestoreEvent Restore Operation event info Restore operation was performed on {net.name} Restore operation was performed on {net.name}
DVPortgroupCreatedEvent dvPort group created info dvPort group {net.name} was added to switch {dvs}. dvPort group {net.name} in {datacenter.name} was added to switch {dvs.name}.
DVPortgroupDestroyedEvent dvPort group deleted info dvPort group {net.name} was deleted. dvPort group {net.name} in {datacenter.name} was deleted.
DVPortgroupEvent dvPort group event info dvPort group event dvPort group event
DVPortgroupReconfiguredEvent dvPort group reconfigured info dvPort group {net.name} was reconfigured. dvPort group {net.name} in {datacenter.name} was reconfigured.
DVPortgroupRenamedEvent dvPort group renamed info dvPort group {oldName} was renamed to {newName}. dvPort group {oldName} in {datacenter.name} was renamed to {newName}
DvsCreatedEvent vSphere Distributed Switch created info A vSphere Distributed Switch {dvs.name} was created A vSphere Distributed Switch {dvs.name} was created in {datacenter.name}.
DvsDestroyedEvent vSphere Distributed Switch deleted info vSphere Distributed Switch {dvs.name} was deleted. vSphere Distributed Switch {dvs.name} in {datacenter.name} was deleted.
DvsEvent vSphere Distributed Switch event info vSphere Distributed Switch event vSphere Distributed Switch event
DvsHealthStatusChangeEvent Health check status of the switch changed. info Health check status changed in vSphere Distributed Switch {dvs.name} on host {host.name} Health check status changed in vSphere Distributed Switch {dvs.name} Health check status was changed in vSphere Distributed Switch {dvs.name} on host {host.name} in {datacenter.name}
DvsHostBackInSyncEvent The vSphere Distributed Switch configuration on the host was synchronized with that of the vCenter Server. info The vSphere Distributed Switch {dvs.name} configuration on the host was synchronized with that of the vCenter Server. The vSphere Distributed Switch {dvs.name} configuration on the host was synchronized with that of the vCenter Server.
DvsHostJoinedEvent Host joined the vSphere Distributed Switch info The host {hostJoined.name} joined the vSphere Distributed Switch {dvs.name}. The host {hostJoined.name} joined the vSphere Distributed Switch {dvs.name} in {datacenter.name}.
DvsHostLeftEvent Host left vSphere Distributed Switch info The host {hostLeft.name} left the vSphere Distributed Switch {dvs.name}. The host {hostLeft.name} left the vSphere Distributed Switch {dvs.name} in {datacenter.name}.
DvsHostStatusUpdated Host status changed on the vSphere Distributed Switch info The host {hostMember.name} changed status on the vSphere Distributed Switch {dvs.name}. The host {hostMember.name} changed status on the vSphere Distributed Switch {dvs.name} in {datacenter.name}.
DvsHostWentOutOfSyncEvent The vSphere Distributed Switch configuration on the host differed from that of the vCenter Server. warning The vSphere Distributed Switch {dvs.name} configuration on the host differed from that of the vCenter Server. The vSphere Distributed Switch {dvs.name} configuration on the host differed from that of the vCenter Server.
DvsImportEvent Import Operation event info Import operation with type {importType} was performed on {dvs.name} Import operation with type {importType} was performed on {dvs.name}
DvsMergedEvent vSphere Distributed Switch merged info vSphere Distributed Switch {srcDvs.name} was merged into {dstDvs.name}. vSphere Distributed Switch {srcDvs.name} was merged into {dstDvs.name} in {datacenter.name}.
DvsPortBlockedEvent dvPort blocked info The dvPort {portKey} was blocked in the vSphere Distributed Switch {dvs.name}. The dvPort {portKey} was blocked in the vSphere Distributed Switch {dvs.name} in {datacenter.name}.
DvsPortConnectedEvent dvPort connected info The dvPort {portKey} was connected in the vSphere Distributed Switch {dvs.name}. The dvPort {portKey} was connected in the vSphere Distributed Switch {dvs.name} in {datacenter.name}
DvsPortCreatedEvent dvPort created info New ports were created in the vSphere Distributed Switch {dvs.name}. New ports were created in the vSphere Distributed Switch {dvs.name} in {datacenter.name}.
DvsPortDeletedEvent dvPort deleted info Ports were deleted in the vSphere Distributed Switch {dvs.name}. Deleted ports in the vSphere Distributed Switch {dvs.name} in {datacenter.name}.
DvsPortDisconnectedEvent dvPort disconnected info The dvPort {portKey} was disconnected in the vSphere Distributed Switch {dvs.name}. The dvPort {portKey} was disconnected in the vSphere Distributed Switch {dvs.name} in {datacenter.name}.
DvsPortEnteredPassthruEvent dvPort in passthrough mode info The dvPort {portKey} was in passthrough mode in the vSphere Distributed Switch {dvs.name}. The dvPort {portKey} was in passthrough mode in the vSphere Distributed Switch {dvs.name} in {datacenter.name}.
DvsPortExitedPassthruEvent dvPort not in passthrough mode info The dvPort {portKey} was not in passthrough mode in the vSphere Distributed Switch {dvs.name}. The dvPort {portKey} was not in passthrough mode in the vSphere Distributed Switch {dvs.name} in {datacenter.name}.
DvsPortJoinPortgroupEvent A dvPort was moved into the dvPort group. info The dvPort {portKey} was moved into the dvPort group {portgroupName}. The dvPort {portKey} was moved into the dvPort group {portgroupName} in {datacenter.name}.
DvsPortLeavePortgroupEvent A dvPort was moved out of the dvPort group. info The dvPort {portKey} was moved out of the dvPort group {portgroupName}. The dvPort {portKey} was moved out of the dvPort group {portgroupName} in {datacenter.name}.
DvsPortLinkDownEvent dvPort link was down info The dvPort {portKey} link was down in the vSphere Distributed Switch {dvs.name}. The dvPort {portKey} link was down in the vSphere Distributed Switch {dvs.name} in {datacenter.name}
DvsPortLinkUpEvent dvPort link was up info The dvPort {portKey} link was up in the vSphere Distributed Switch {dvs.name}. The dvPort {portKey} link was up in the vSphere Distributed Switch {dvs.name} in {datacenter.name}
DvsPortReconfiguredEvent dvPort reconfigured info Ports were reconfigured in the vSphere Distributed Switch {dvs.name}. Reconfigured ports in the vSphere Distributed Switch {dvs.name} in {datacenter.name}.
DvsPortRuntimeChangeEvent dvPort runtime information changed. info The dvPort {portKey} runtime information changed in the vSphere Distributed Switch {dvs.name}. The dvPort {portKey} runtime information changed in the vSphere Distributed Switch {dvs.name} in {datacenter.name}.
DvsPortUnblockedEvent dvPort unblocked info The dvPort {portKey} was unblocked in the vSphere Distributed Switch {dvs.name}. The dvPort {portKey} was unblocked in the vSphere Distributed Switch {dvs.name} in {datacenter.name}.
DvsPortVendorSpecificStateChangeEvent dvPort vendor specific state changed. info The dvPort {portKey} vendor specific state changed in the vSphere Distributed Switch {dvs.name}. The dvPort {portKey} vendor specific state changed in the vSphere Distributed Switch {dvs.name} in {datacenter.name}.
DvsReconfiguredEvent vSphere Distributed Switch reconfigured info The vSphere Distributed Switch {dvs.name} was reconfigured. The vSphere Distributed Switch {dvs.name} in {datacenter.name} was reconfigured.
DvsRenamedEvent vSphere Distributed Switch renamed info The vSphere Distributed Switch {oldName} was renamed to {newName}. The vSphere Distributed Switch {oldName} in {datacenter.name} was renamed to {newName}.
DvsRestoreEvent Restore Operation event info Restore operation was performed on {dvs.name} Restore operation was performed on {dvs.name}
DvsUpgradeAvailableEvent An upgrade for the vSphere Distributed Switch is available. info An upgrade for vSphere Distributed Switch {dvs.name} is available. An upgrade for the vSphere Distributed Switch {dvs.name} in datacenter {datacenter.name} is available.
DvsUpgradedEvent The vSphere Distributed Switch was upgraded. info vSphere Distributed Switch {dvs.name} was upgraded. vSphere Distributed Switch {dvs.name} in datacenter {datacenter.name} was upgraded.
DvsUpgradeInProgressEvent An upgrade for the vSphere Distributed Switch is in progress. info An upgrade for vSphere Distributed Switch {dvs.name} is in progress. An upgrade for the vSphere Distributed Switch {dvs.name} in datacenter {datacenter.name} is in progress.
DvsUpgradeRejectedEvent Cannot complete the upgrade for the vSphere Distributed Switch info An upgrade for vSphere Distributed Switch {dvs.name} was rejected. Cannot complete an upgrade for the vSphere Distributed Switch {dvs.name} in datacenter {datacenter.name}
EnteredMaintenanceModeEvent Entered maintenance mode info Host {host.name} in {datacenter.name} has entered maintenance mode Host {host.name} in {datacenter.name} has entered maintenance mode Enter maintenance mode completed. All virtual machine operations are disabled Host {host.name} in {datacenter.name} has entered maintenance mode
EnteredStandbyModeEvent Entered standby mode info Entered standby mode The host {host.name} is in standby mode
EnteringMaintenanceModeEvent Entering maintenance mode info Host {host.name} has started to enter maintenance mode Host {host.name} has started to enter maintenance mode Started to enter maintenance mode. Waiting for virtual machines to shut down, suspend, or migrate Host {host.name} in {datacenter.name} has started to enter maintenance mode
EnteringStandbyModeEvent Entering standby mode info Entering standby mode The host {host.name} is entering standby mode
ErrorUpgradeEvent Upgrade error error {message}
com.vmware.license.AddLicenseEvent Added License info License {licenseKey} added to VirtualCenter
com.vmware.license.AssignLicenseEvent Assigned License info License {licenseKey} assigned to asset {entityName} with id {entityId}
com.vmware.license.DLFDownloadFailedEvent Download License Information warning Failed to download license information from the host {hostname} due to {errorReason}
com.vmware.license.LicenseAssignFailedEvent License assignment faults info License assignment on the host fails. Reasons: {errorMessage.@enum.com.vmware.license.LicenseAssignError}.
com.vmware.license.LicenseCapacityExceededEvent License Capacity Exceeded warning The current license usage ({currentUsage} {costUnitText}) for {edition} exceeds the license capacity ({capacity} {costUnitText})
com.vmware.license.LicenseExpiryEvent License Expiry warning Your host license expires in {remainingDays} days. The host will disconnect from vCenter Server when its license expires. Your host license expires in {remainingDays} days. The host will disconnect from vCenter Server when its license expires.
com.vmware.license.LicenseUserThresholdExceededEvent License User Threshold Exceeded warning The current license usage ({currentUsage} {costUnitText}) for {edition} exceeds the user-defined threshold ({threshold} {costUnitText})
com.vmware.license.RemoveLicenseEvent Removed License info License {licenseKey} removed from VirtualCenter
com.vmware.license.UnassignLicenseEvent Unassigned License info License unassigned from asset {entityName} with id {entityId}
com.vmware.pbm.profile.associate Storage policy associated info Associated storage policy: {ProfileId} with entity: {EntityId} Associated storage policy: {ProfileId} with entity: {EntityId} Associated storage policy: {ProfileId} with entity: {EntityId} Associated storage policy: {ProfileId} with entity: {EntityId} Associated storage policy: {ProfileId} with entity: {EntityId}
com.vmware.pbm.profile.delete Storage policy deleted info Deleted storage policy: {ProfileId} Deleted storage policy: {ProfileId} Deleted storage policy: {ProfileId} Deleted storage policy: {ProfileId} Deleted storage policy: {ProfileId}
com.vmware.pbm.profile.dissociate Storage policy dissociated info Dissociated storage policy: {ProfileId} from entity: {EntityId} Dissociated storage policy: {ProfileId} from entity: {EntityId} Dissociated storage policy: {ProfileId} from entity: {EntityId} Dissociated storage policy: {ProfileId} from entity: {EntityId} Dissociated storage policy: {ProfileId} from entity: {EntityId}
com.vmware.pbm.profile.updateName Storage policy name updated info Storage policy name updated for {ProfileId}. New name: {NewProfileName} Storage policy name updated for {ProfileId}. New name: {NewProfileName} Storage policy name updated for {ProfileId}. New name: {NewProfileName} Storage policy name updated for {ProfileId}. New name: {NewProfileName} Storage policy name updated for {ProfileId}. New name: {NewProfileName}
com.vmware.vc.HA.ClusterFailoverActionInitiatedEvent vSphere HA initiated a failover action warning vSphere HA initiated a failover action on {pendingVms} virtual machines in cluster {computeResource.name} vSphere HA initiated a failover action on {pendingVms} virtual machines vSphere HA initiated a failover action on {pendingVms} virtual machines in cluster {computeResource.name} in datacenter {datacenter.name}
com.vmware.vc.HA.ClusterFailoverInProgressEvent vSphere HA failover operation in progress Warning vSphere HA failover operation in progress in cluster {computeResource.name}: {numBeingPlaced} VMs being restarted, {numToBePlaced} VMs waiting for a retry, {numAwaitingResource} VMs waiting for resources, {numAwaitingVsanVmChange} inaccessible Virtual SAN VMs vSphere HA failover operation in progress: {numBeingPlaced} VMs being restarted, {numToBePlaced} VMs waiting for a retry, {numAwaitingResource} VMs waiting for resources, {numAwaitingVsanVmChange} inaccessible Virtual SAN VMs vSphere HA failover operation in progress in cluster {computeResource.name} in datacenter {datacenter.name}: {numBeingPlaced} VMs being restarted, {numToBePlaced} VMs waiting for a retry, {numAwaitingResource} VMs waiting for resources, {numAwaitingVsanVmChange} inaccessible Virtual SAN VMs
com.vmware.vc.HA.DasHostCompleteDatastoreFailureEvent Host complete datastore failure error All shared datastores failed on the host {hostName} in cluster {computeResource.name} All shared datastores failed on the host {hostName} All shared datastores failed on the host {hostName} All shared datastores failed on the host {hostName} in cluster {computeResource.name} in {datacenter.name}
com.vmware.vc.HA.DasHostCompleteNetworkFailureEvent Host complete network failure error All VM networks failed on the host {hostName} in cluster {computeResource.name} All VM networks failed on the host {hostName} All VM networks failed on the host {hostName} All VM networks failed on the host {hostName} in cluster {computeResource.name} in {datacenter.name}
com.vmware.vc.HA.HeartbeatDatastoreChanged vSphere HA changed a host's heartbeat datastores info Datastore {dsName} is {changeType.@enum.com.vmware.vc.HA.HeartbeatDatastoreChange} for storage heartbeating monitored by the vSphere HA agent on host {host.name} in cluster {computeResource.name} Datastore {dsName} is {changeType.@enum.com.vmware.vc.HA.HeartbeatDatastoreChange} for storage heartbeating monitored by the vSphere HA agent on host {host.name} Datastore {dsName} is {changeType.@enum.com.vmware.vc.HA.HeartbeatDatastoreChange} for storage heartbeating monitored by the vSphere HA agent on this host Datastore {dsName} is {changeType.@enum.com.vmware.vc.HA.HeartbeatDatastoreChange} for storage heartbeating monitored by the vSphere HA agent on host {host.name} in cluster {computeResource.name} in {datacenter.name}
com.vmware.vc.HA.HeartbeatDatastoreNotSufficient vSphere HA heartbeat datastore number for a host is insufficient warning The number of vSphere HA heartbeat datastores for host {host.name} in cluster {computeResource.name} is {selectedNum}, which is less than required: {requiredNum} The number of vSphere HA heartbeat datastores for host {host.name} is {selectedNum}, which is less than required: {requiredNum} The number of vSphere HA heartbeat datastores for this host is {selectedNum}, which is less than required: {requiredNum} The number of vSphere HA heartbeat datastores for host {host.name} in cluster {computeResource.name} in {datacenter.name} is {selectedNum}, which is less than required: {requiredNum}
com.vmware.vc.HA.HostAgentErrorEvent vSphere HA agent on a host has an error warning vSphere HA agent for host {host.name} has an error in {computeResource.name}: {reason.@enum.com.vmware.vc.HA.HostAgentErrorReason} vSphere HA agent for host {host.name} has an error: {reason.@enum.com.vmware.vc.HA.HostAgentErrorReason} vSphere HA agent for this host has an error: {reason.@enum.com.vmware.vc.HA.HostAgentErrorReason} vSphere HA agent for host {host.name} has an error in {computeResource.name} in {datacenter.name}: {reason.@enum.com.vmware.vc.HA.HostAgentErrorReason}
com.vmware.vc.HA.HostDasErrorEvent vSphere HA agent error error vSphere HA agent on host {host.name} has an error: {reason.@enum.com.vmware.vc.HA.HostDasErrorEvent.HostDasErrorReason} vSphere HA agent on host {host.name} has an error. {reason.@enum.com.vmware.vc.HA.HostDasErrorEvent.HostDasErrorReason} vSphere HA agent has an error: {reason.@enum.HostDasErrorEvent.HostDasErrorReason} vSphere HA agent on {host.name} in cluster {computeResource.name} in {datacenter.name} has an error: {reason.@enum.HostDasErrorEvent.HostDasErrorReason}
com.vmware.vc.HA.HostStateChangedEvent The vSphere HA host availability state changed info The vSphere HA availability state of the host {host.name} in cluster {computeResource.name} has changed to {newState.@enum.com.vmware.vc.HA.DasFdmAvailabilityState} The vSphere HA availability state of the host {host.name} has changed to {newState.@enum.com.vmware.vc.HA.DasFdmAvailabilityState} The vSphere HA availability state of this host has changed to {newState.@enum.com.vmware.vc.HA.DasFdmAvailabilityState} The vSphere HA availability state of the host {host.name} in cluster in {computeResource.name} in {datacenter.name} has changed to {newState.@enum.com.vmware.vc.HA.DasFdmAvailabilityState}
com.vmware.vc.HA.HostUnconfiguredWithProtectedVms A disconnected host has vSphere HA protected VMs error Host {host.name} in cluster {computeResource.name} is disconnected from vCenter Server, but contains {protectedVmCount} protected virtual machine(s) Host {host.name} is disconnected from vCenter Server, but contains {protectedVmCount} protected virtual machine(s) This host is disconnected from vCenter Server, but contains {protectedVmCount} vSphere HA protected virtual machine(s) Host {host.name} in cluster {computeResource.name} in {datacenter.name} is disconnected from vCenter Server, but contains {protectedVmCount} protected virtual machine(s)
com.vmware.vc.HA.InvalidMaster vSphere HA detected an invalid master agent warning vSphere HA agent on host {remoteHostname} is an invalid master. The host should be examined to determine if it has been compromised. vSphere HA agent on host {remoteHostname} is an invalid master. The host should be examined to determine if it has been compromised. vSphere HA agent on host {remoteHostname} is an invalid master. The host should be examined to determine if it has been compromised.
com.vmware.vc.HA.NotAllHostAddrsPingable vSphere HA agent cannot reach some cluster management addresses info The vSphere HA agent on the host {host.name} in cluster {computeResource.name} cannot reach some of the management network addresses of other hosts, and thus HA may not be able to restart VMs if a host failure occurs: {unpingableAddrs} The vSphere HA agent on the host {host.name} cannot reach some of the management network addresses of other hosts, and thus HA may not be able to restart VMs if a host failure occurs: {unpingableAddrs} The vSphere HA agent on this host cannot reach some of the management network addresses of other hosts, and HA may not be able to restart VMs if a host failure occurs: {unpingableAddrs} The vSphere HA agent on the host {host.name} in cluster {computeResource.name} in {datacenter.name} cannot reach some of the management network addresses of other hosts, and thus HA may not be able to restart VMs if a host failure occurs: {unpingableAddrs}
com.vmware.vc.HA.StartFTSecondaryFailedEvent vSphere HA failed to start a Fault Tolerance secondary VM. error vSphere HA agent failed to start Fault Tolerance secondary VM {secondaryCfgPath} on host {secondaryHost} for primary VM {vm.name} in cluster {computeResource.name}. Reason : {fault.msg}. vSphere HA agent will retry until it times out. vSphere HA agent failed to start Fault Tolerance secondary VM {secondaryCfgPath} on host {secondaryHost} for primary VM {vm.name}. Reason : {fault.msg}. vSphere HA agent will retry until it times out. vSphere HA agent failed to start Fault Tolerance secondary VM {secondaryCfgPath} on host {secondaryHost} for primary VM {vm.name}. Reason : {fault.msg}. vSphere HA agent will retry until it times out. vSphere HA agent failed to start Fault Tolerance secondary VM {secondaryCfgPath} on host {secondaryHost}. Reason : {fault.msg}. vSphere HA agent will retry until it times out. vSphere HA agent failed to start Fault Tolerance secondary VM {secondaryCfgPath} on host {secondaryHost} for primary VM {vm.name} in cluster {computeResource.name} in {datacenter.name}. Reason : {fault.msg}. vSphere HA agent will retry until it times out.
com.vmware.vc.HA.StartFTSecondarySucceededEvent vSphere HA successfully started a Fault Tolerance secondary VM. info vSphere HA agent successfully started Fault Tolerance secondary VM {secondaryCfgPath} on host {secondaryHost} for primary VM {vm.name} in cluster {computeResource.name}. vSphere HA agent successfully started Fault Tolerance secondary VM {secondaryCfgPath} on host {secondaryHost} for primary VM {vm.name}. vSphere HA agent successfully started Fault Tolerance secondary VM {secondaryCfgPath} on host {secondaryHost} for primary VM {vm.name}. vSphere HA agent successfully started Fault Tolerance secondary VM {secondaryCfgPath} on host {secondaryHost}. vSphere HA agent successfully started Fault Tolerance secondary VM {secondaryCfgPath} on host {secondaryHost} for primary VM {vm.name} in cluster {computeResource.name}.
com.vmware.vc.HA.UserHeartbeatDatastoreRemoved vSphere HA removed a datastore from preferred heartbeat datastores warning vSphere HA removed datastore {dsName} from the set of preferred heartbeat datastores selected for cluster {computeResource.name} because the datastore is removed from inventory vSphere HA removed datastore {dsName} from the set of preferred heartbeat datastores selected for cluster because the datastore is removed from inventory vSphere HA removed datastore {dsName} from the set of preferred heartbeat datastores selected for cluster {computeResource.name} in {datacenter.name} because the datastore is removed from inventory
com.vmware.vc.HA.VcCannotCommunicateWithMasterEvent vCenter Server cannot communicate with the master vSphere HA agent warning vCenter Server cannot communicate with the master vSphere HA agent on {hostname} in cluster {computeResource.name} vCenter Server cannot communicate with the master vSphere HA agent on {hostname} vCenter Server cannot communicate with the master vSphere HA agent on {hostname} in cluster {computeResource.name} in {datacenter.name}
com.vmware.vc.HA.VcConnectedToMasterEvent vCenter Server connected to a vSphere HA master agent info vCenter Server is connected to a master HA agent running on host {hostname} in {computeResource.name} vCenter Server is connected to a master HA agent running on host {hostname} vCenter Server is connected to a master HA agent running on host {hostname} in {computeResource.name} in {datacenter.name}
com.vmware.vc.HA.VcDisconnectedFromMasterEvent vCenter Server disconnected from a master vSphere HA agent warning vCenter Server is disconnected from a master HA agent running on host {hostname} in {computeResource.name} vCenter Server is disconnected from a master HA agent running on host {hostname} vCenter Server is disconnected from a master HA agent running on host {hostname} in {computeResource.name} in {datacenter.name}
com.vmware.vc.VCHealthStateChangedEvent vCenter Service Overall Health Changed info vCenter Service overall health changed from '{oldState}' to '{newState}'
com.vmware.vc.VmCloneFailedInvalidDestinationEvent Cannot complete virtual machine clone. error Cannot clone {vm.name} as {destVmName} to invalid or non-existent destination with ID {invalidMoRef}: {fault}
com.vmware.vc.VmCloneToResourcePoolFailedEvent Cannot complete virtual machine clone. error Cannot clone {vm.name} as {destVmName} to resource pool {destResourcePool}: {fault}
com.vmware.vc.certmgr.HostCaCertsAndCrlsUpdatedEvent CA Certificates were updated on host info CA Certificates were updated on {hostname} CA Certificates were updated on {hostname}
com.vmware.vc.certmgr.HostCertExpirationImminentEvent Host Certificate expiration is imminent warning Host Certificate expiration is imminent on {hostname}. Expiration Date: {expiryDate} Host Certificate expiration is imminent on {hostname}. Expiration Date: {expiryDate}
com.vmware.vc.certmgr.HostCertExpiringEvent Host Certificate is nearing expiration warning Host Certificate on {hostname} is nearing expiration. Expiration Date: {expiryDate} Host Certificate on {hostname} is nearing expiration. Expiration Date: {expiryDate}
com.vmware.vc.certmgr.HostCertExpiringShortlyEvent Host Certificate will expire soon warning Host Certificate on {hostname} will expire soon. Expiration Date: {expiryDate} Host Certificate on {hostname} will expire soon. Expiration Date: {expiryDate}
com.vmware.vc.certmgr.HostCertRevokedEvent Host Certificate revoked warning Host Certificate on {hostname} is revoked. Host Certificate on {hostname} is revoked.
com.vmware.vc.certmgr.HostCertUpdatedEvent Host Certificate was updated info Host Certificate was updated on {hostname}, new thumbprint: {thumbprint} Host Certificate was updated on {hostname}, new thumbprint: {thumbprint}
com.vmware.vc.certmgr.HostMgmtAgentsRestartedEvent Management Agents on ESX Host info Management Agents were restarted on {hostname} Management Agents were restarted on {hostname}
com.vmware.vc.cim.CIMGroupHealthStateChanged Hardware Health Changed info Health of {data.group} changed from {data.oldState} to {data.newState}. {data.cause}
com.vmware.vc.datastore.UpdateVmFilesFailedEvent Failed to update VM files error Failed to update VM files on datastore {ds.name} Failed to update VM files on datastore {ds.name} using host {hostName}
com.vmware.vc.datastore.UpdatedVmFilesEvent Updated VM files info Updated VM files on datastore {ds.name} Updated VM files on datastore {ds.name} using host {hostName}
com.vmware.vc.datastore.UpdatingVmFilesEvent Updating VM Files info Updating VM files on datastore {ds.name} Updating VM files on datastore {ds.name} using host {hostName}
com.vmware.vc.guestOperations.GuestOperation Guest operation info Guest operation {operationName.@enum.com.vmware.vc.guestOp} performed. Guest operation {operationName.@enum.com.vmware.vc.guestOp} performed on Virtual machine {vm.name}.
com.vmware.vc.guestOperations.GuestOperationAuthFailure Guest operation authentication failure warning Guest operation authentication failed for operation {operationName.@enum.com.vmware.vc.guestOp}. Guest operation authentication failed for operation {operationName.@enum.com.vmware.vc.guestOp} on Virtual machine {vm.name}.
com.vmware.vc.host.clear.vFlashResource.reachthreshold Host's virtual flash resource usage dropped below the threshold. info Host's virtual flash resource usage dropped below {1}%. Host's virtual flash resource usage dropped below {1}%. Host's virtual flash resource usage dropped below {1}%. Host's virtual flash resource usage dropped below {1}%.
com.vmware.vc.host.problem.vFlashResource.reachthreshold Host's virtual flash resource usage exceeds the threshold. warning Host's virtual flash resource usage is more than {1}%. Host's virtual flash resource usage is more than {1}%. Host's virtual flash resource usage is more than {1}%. Host's virtual flash resource usage is more than {1}%.
com.vmware.vc.host.vFlash.defaultModuleChangedEvent Default virtual flash module is changed to {vFlashModule} on the host info Default virtual flash module is changed to {vFlashModule} on the host Default virtual flash module is changed to {vFlashModule} on the host Default virtual flash module is changed to {vFlashModule} on the host Any new virtual Flash Read Cache configuration request will use {vFlashModule} as default virtual flash module. All existing virtual Flash Read Cache configurations remain unchanged.
com.vmware.vc.iofilter.HostVendorProviderRegistrationFailedEvent vSphere APIs for I/O Filters (VAIO) host vendor provider registration has failed. Reason : {fault.msg}. error vSphere APIs for I/O Filters (VAIO) vendor provider {host.name} registration has failed. Reason : {fault.msg}. vSphere APIs for I/O Filters (VAIO) vendor provider {host.name} registration has failed. Reason : {fault.msg}. vSphere APIs for I/O Filters (VAIO) vendor provider {host.name} registration has failed. Reason : {fault.msg}. vSphere APIs for I/O Filters (VAIO) vendor provider {host.name} registration has failed. Reason : {fault.msg}.
com.vmware.vc.iofilter.HostVendorProviderUnregistrationFailedEvent Failed to unregister vSphere APIs for I/O Filters (VAIO) host vendor provider. Reason : {fault.msg}. error Failed to unregister vSphere APIs for I/O Filters (VAIO) vendor provider {host.name}. Reason : {fault.msg}. Failed to unregister vSphere APIs for I/O Filters (VAIO) vendor provider {host.name}. Reason : {fault.msg}. Failed to unregister vSphere APIs for I/O Filters (VAIO) vendor provider {host.name}. Reason : {fault.msg}. Failed to unregister vSphere APIs for I/O Filters (VAIO) vendor provider {host.name}. Reason : {fault.msg}.
com.vmware.vc.npt.VmAdapterEnteredPassthroughEvent Virtual NIC entered passthrough mode info Network passthrough is active on adapter {deviceLabel} of virtual machine {vm.name} on host {host.name} Network passthrough is active on adapter {deviceLabel} of virtual machine {vm.name} on host {host.name} Network passthrough is active on adapter {deviceLabel} of virtual machine {vm.name} Network passthrough is active on adapter {deviceLabel} Network passthrough is active on adapter {deviceLabel} of virtual machine {vm.name} on host {host.name} in {datacenter.name}
com.vmware.vc.npt.VmAdapterExitedPassthroughEvent Virtual NIC exited passthrough mode info Network passthrough is inactive on adapter {deviceLabel} of virtual machine {vm.name} on host {host.name} Network passthrough is inactive on adapter {deviceLabel} of virtual machine {vm.name} on host {host.name} Network passthrough is inactive on adapter {deviceLabel} of virtual machine {vm.name} Network passthrough is inactive on adapter {deviceLabel} Network passthrough is inactive on adapter {deviceLabel} of virtual machine {vm.name} on host {host.name} in {datacenter.name}
com.vmware.vc.ovfconsumers.CloneOvfConsumerStateErrorEvent Failed to clone state for entity on extension error Failed to clone state on extension {extensionName} Failed to clone state for the entity '{entityName}' on extension {extensionName}
com.vmware.vc.ovfconsumers.GetOvfEnvironmentSectionsErrorEvent Failed to retrieve OVF environment sections for VM on extension error Failed to retrieve OVF environment sections from extension {extensionName} Failed to retrieve OVF environment sections for VM '{vm.name}' from extension {extensionName}
com.vmware.vc.ovfconsumers.PowerOnAfterCloneErrorEvent Unable to power on VM after cloning error Powering on after cloning was blocked by an extension. Message: {description} Powering on VM '{vm.name}' after cloning was blocked by an extension. Message: {description}
com.vmware.vc.ovfconsumers.RegisterEntityErrorEvent Failed to register entity on extension error Failed to register entity '{entityName}' on extension {extensionName}
com.vmware.vc.ovfconsumers.UnregisterEntitiesErrorEvent Failed to unregister entities on extension error Failed to unregister entities on extension {extensionName}
com.vmware.vc.ovfconsumers.ValidateOstErrorEvent Failed to validate OVF descriptor on extension error Failed to validate OVF descriptor on extension {extensionName}
com.vmware.vc.rp.ResourcePoolRenamedEvent Resource pool renamed info Resource pool '{oldName}' has been renamed to '{newName}' Resource pool '{oldName}' has been renamed to '{newName}' Resource pool '{oldName}' has been renamed to '{newName}' Resource pool '{oldName}' has been renamed to '{newName}' Resource pool '{oldName}' has been renamed to '{newName}'
com.vmware.vc.sdrs.DatastoreInMultipleDatacentersEvent Datastore cluster has datastores shared across multiple datacenters warning Datastore cluster {objectName} has one or more datastores {datastore} shared across multiple datacenters Datastore cluster {objectName} has one or more datastores {datastore} shared across multiple datacenters Datastore cluster {objectName} has one or more datastores {datastore} shared across multiple datacenters Datastore cluster {objectName} has one or more datastores {datastore} shared across multiple datacenters Datastore cluster {objectName} has one or more datastores {datastore} shared across multiple datacenters
com.vmware.vc.sdrs.StorageDrsEnabledEvent Storage DRS enabled info Enabled storage DRS on datastore cluster {objectName} with automation level {behavior.@enum.storageDrs.PodConfigInfo.Behavior} Enabled storage DRS on datastore cluster {objectName} with automation level {behavior.@enum.storageDrs.PodConfigInfo.Behavior} Enabled storage DRS on datastore cluster {objectName} with automation level {behavior.@enum.storageDrs.PodConfigInfo.Behavior} Enabled storage DRS on datastore cluster {objectName} with automation level {behavior.@enum.storageDrs.PodConfigInfo.Behavior} Enabled storage DRS on datastore cluster {objectName} with automation level {behavior.@enum.storageDrs.PodConfigInfo.Behavior}
com.vmware.vc.sdrs.StorageDrsNotSupportedHostConnectedToPodEvent Datastore cluster connected to host(s) that do not support storage DRS warning Datastore cluster {objectName} is connected to one or more hosts {host} that do not support storage DRS Datastore cluster {objectName} is connected to one or more hosts {host} that do not support storage DRS Datastore cluster {objectName} is connected to one or more hosts {host} that do not support storage DRS Datastore cluster {objectName} is connected to one or more hosts {host} that do not support storage DRS Datastore cluster {objectName} is connected to one or more hosts {host} that do not support storage DRS
com.vmware.vc.sdrs.StorageDrsStorageMigrationEvent Storage DRS migrated VM disks info Storage DRS migrated disks of VM {vm.name} to datastore {ds.name} Storage DRS migrated disks of VM {vm.name} to datastore {ds.name} Storage DRS migrated disks of VM {vm.name} to datastore {ds.name} Storage DRS migrated disks of VM {vm.name} to datastore {ds.name} Storage DRS migrated disks of VM {vm.name} to datastore {ds.name}
com.vmware.vc.sdrs.StorageDrsStoragePlacementEvent Storage DRS placed VM disks info Storage DRS placed disks of VM {vm.name} on datastore {ds.name} Storage DRS placed disks of VM {vm.name} on datastore {ds.name} Storage DRS placed disks of VM {vm.name} on datastore {ds.name} Storage DRS placed disks of VM {vm.name} on datastore {ds.name} Storage DRS placed disks of VM {vm.name} on datastore {ds.name}
com.vmware.vc.sdrs.StoragePodCreatedEvent Datastore cluster created info Created datastore cluster {objectName} Created datastore cluster {objectName} Created datastore cluster {objectName} Created datastore cluster {objectName} Created datastore cluster {objectName}
com.vmware.vc.sdrs.StoragePodDestroyedEvent Datastore cluster deleted info Removed datastore cluster {objectName} Removed datastore cluster {objectName} Removed datastore cluster {objectName} Removed datastore cluster {objectName} Removed datastore cluster {objectName}
com.vmware.vc.sioc.NotSupportedHostConnectedToDatastoreEvent SIOC: pre-4.1 host connected to SIOC-enabled datastore warning SIOC has detected that a host: {host} connected to a SIOC-enabled datastore: {objectName} is running an older version of ESX that does not support SIOC. This is an unsupported configuration. SIOC has detected that a host: {host} connected to a SIOC-enabled datastore: {objectName} is running an older version of ESX that does not support SIOC. This is an unsupported configuration. SIOC has detected that a host: {host} connected to a SIOC-enabled datastore: {objectName} is running an older version of ESX that does not support SIOC. This is an unsupported configuration. SIOC has detected that a host: {host} connected to a SIOC-enabled datastore: {objectName} is running an older version of ESX that does not support SIOC. This is an unsupported configuration. SIOC has detected that a host: {host} connected to a SIOC-enabled datastore: {objectName} is running an older version of ESX that does not support SIOC. This is an unsupported configuration.
com.vmware.vc.sms.LunCapabilityInitEvent System capability warning from storage provider warning Storage provider [{providerName}] : system capability warning for {eventSubjectId} : {msgTxt}
com.vmware.vc.sms.LunCapabilityMetEvent System capability normal event from storage provider info Storage provider [{providerName}] : system capability normal for {eventSubjectId}
com.vmware.vc.sms.LunCapabilityNotMetEvent System capability alert from storage provider error Storage provider [{providerName}] : system capability alert for {eventSubjectId} : {msgTxt}
com.vmware.vc.sms.ObjectTypeAlarmClearedEvent A Storage Alarm of type 'Object' cleared by the VASA provider info Storage provider [{providerName}] cleared a Storage Alarm of type 'Object' on {eventSubjectId} : {msgTxt}
com.vmware.vc.sms.ObjectTypeAlarmErrorEvent An alert on an object raised by the VASA provider error Storage provider [{providerName}] raised an alert type 'Object' on {eventSubjectId} : {msgTxt}
com.vmware.vc.sms.ObjectTypeAlarmWarningEvent A warning on an object raised by the VASA provider warning Storage provider [{providerName}] raised a warning of type 'Object' on {eventSubjectId} : {msgTxt}
com.vmware.vc.sms.ThinProvisionedLunThresholdClearedEvent Thin provisioning capacity threshold normal event from storage provider info Storage provider [{providerName}] : thin provisioning capacity threshold normal for {eventSubjectId}
com.vmware.vc.sms.ThinProvisionedLunThresholdCrossedEvent Thin provisioning capacity threshold alert from storage provider error Storage provider [{providerName}] : thin provisioning capacity threshold alert for {eventSubjectId}
com.vmware.vc.sms.ThinProvisionedLunThresholdInitEvent Thin provisioning capacity threshold warning from storage provider warning Storage provider [{providerName}] : thin provisioning capacity threshold warning for {eventSubjectId}
com.vmware.vc.sms.VasaProviderCertificateHardLimitReachedEvent Storage provider certificate will expire very shortly error Certificate for storage provider {providerName} will expire very shortly. Expiration date : {expiryDate}
com.vmware.vc.sms.VasaProviderCertificateSoftLimitReachedEvent Storage provider certificate will expire soon warning Certificate for storage provider {providerName} will expire soon. Expiration date : {expiryDate}
com.vmware.vc.sms.VasaProviderCertificateValidEvent Storage provider certificate is valid info Certificate for storage provider {providerName} is valid
com.vmware.vc.sms.VasaProviderConnectedEvent Storage provider is connected info Storage provider {providerName} is connected
com.vmware.vc.sms.VasaProviderDisconnectedEvent Storage provider is disconnected error Storage provider {providerName} is disconnected
com.vmware.vc.sms.VasaProviderRefreshCACertsAndCRLsFailure Refreshing CA certificates and CRLs failed for some VASA providers error Refreshing CA certificates and CRLs failed for VASA providers with url : {providerUrls}
com.vmware.vc.sms.datastore.ComplianceStatusCompliantEvent Virtual disk bound to a policy profile is compliant backing object based storage. info Virtual disk {diskKey} on {vmName} connected to {datastore.name} is compliant from storage provider {providerName}. Virtual disk {diskKey} on {vmName} connected to datastore {datastore.name} in {datacenter.name} is compliant from storage provider {providerName}.
com.vmware.vc.sms.datastore.ComplianceStatusNonCompliantEvent Virtual disk bound to a policy profile is non compliant backing object based storage. error Virtual disk {diskKey} on {vmName} connected to {datastore.name} is not compliant {operationalStatus] from storage provider {providerName}. Virtual disk {diskKey} on {vmName} connected to {datastore.name} in {datacenter.name} is not compliant {operationalStatus] from storage provider {providerName}.
com.vmware.vc.sms.datastore.ComplianceStatusUnknownEvent Virtual disk bound to a policy profile is unknown compliance status backing object based storage. warning Virtual disk {diskKey} on {vmName} connected to {datastore.name} compliance status is unknown from storage provider {providerName}. Virtual disk {diskKey} on {vmName} connected to {datastore.name} in {datacenter.name} compliance status is unknown from storage provider {providerName}.
com.vmware.vc.sms.provider.health.event Health event from storage provider info Storage provider [{providerName}] : health event for {eventSubjectId} : {msgTxt}
com.vmware.vc.sms.provider.system.event System event from storage provider info Storage provider [{providerName}] : system event : {msgTxt}
com.vmware.vc.sms.vm.ComplianceStatusCompliantEvent Virtual disk bound to a policy profile is complianct backing object based storage. info Virtual disk {diskKey} on {vm.name} on {host.name} in {computeResource.name} is compliant from storage provider {providerName}. Virtual disk {diskKey} on {vm.name} on {host.name} is compliant from storage provider {providerName}. Virtual disk {diskKey} on {vm.name} is compliant from storage provider {providerName}. Virtual disk {diskKey} on {vm.name} is compliant from storage provider {providerName}. Virtual disk {diskKey} on {vm.name} on {host.name} and {computeResource.name} in {datacenter.name} is compliant from storage provider {providerName}.
com.vmware.vc.sms.vm.ComplianceStatusNonCompliantEvent Virtual disk bound to a policy profile is non complianct backing object based storage. error Virtual disk {diskKey} on {vm.name} on {host.name} in {computeResource.name} is not compliant {operationalStatus] from storage provider {providerName}. Virtual disk {diskKey} on {vm.name} on {host.name} is not compliant {operationalStatus] from storage provider {providerName}. Virtual disk {diskKey} on {vm.name} is not compliant {operationalStatus] from storage provider {providerName}. Virtual disk {diskKey} on {vm.name} is not compliant {operationalStatus] from storage provider {providerName}. Virtual disk {diskKey} on {vm.name} on {host.name} and {computeResource.name} in {datacenter.name} is not compliant {operationalStatus] from storage provider {providerName}.
com.vmware.vc.sms.vm.ComplianceStatusUnknownEvent Virtual disk bound to a policy profile is unknown compliance status backing object based storage. warning Virtual disk {diskKey} on {vm.name} on {host.name} in {computeResource.name} compliance status is unknown from storage provider {providerName}. Virtual disk {diskKey} on {vm.name} on {host.name} compliance status is unknown from storage provider {providerName}. Virtual disk {diskKey} on {vm.name} compliance status is unknown from storage provider {providerName}. Virtual disk {diskKey} on {vm.name} compliance status is unknown from storage provider {providerName}. Virtual disk {diskKey} on {vm.name} on {host.name} and {computeResource.name} in {datacenter.name} compliance status is unknown from storage provider {providerName}.
com.vmware.vc.spbm.ProfileAssociationFailedEvent Profile association/dissociation failed error Profile association/dissociation failed for {entityName} Profile association/dissociation failed for {entityName} Profile association/dissociation failed for {entityName} Profile association/dissociation failed for {entityName} Profile association/dissociation failed for {entityName}
com.vmware.vc.spbm.ServiceErrorEvent Configuring storage policy failed. error Configuring storage policy failed for VM {entityName}. Verify that SPBM service is healthy. Fault Reason : {errorMessage} Configuring storage policy failed for VM {entityName}. Verify that SPBM service is healthy. Fault Reason : {errorMessage} Configuring storage policy failed for VM {entityName}. Verify that SPBM service is healthy. Fault Reason : {errorMessage} Configuring storage policy failed for VM {entityName}. Verify that SPBM service is healthy. Fault Reason : {errorMessage} Configuring storage policy failed for VM {entityName}. Verify that SPBM service is healthy. Fault Reason : {errorMessage}
com.vmware.vc.vcp.TestEndEvent VM Component Protection test ends info VM Component Protection test ends on host {host.name} in cluster {computeResource.name} VM Component Protection test ends on host {host.name} VM Component Protection test ends VM Component Protection test ends on host {host.name} in cluster {computeResource.name} in datacenter {datacenter.name}
com.vmware.vc.vcp.TestStartEvent VM Component Protection test starts info VM Component Protection test starts on host {host.name} in cluster {computeResource.name} VM Component Protection test starts on host {host.name} VM Component Protection test starts VM Component Protection test starts on host {host.name} in cluster {computeResource.name} in datacenter {datacenter.name}
com.vmware.vc.vcp.VmDatastoreFailedEvent Virtual machine lost datastore access error Virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} lost access to {datastore} Virtual machine {vm.name} on host {host.name} lost access to {datastore} Virtual machine {vm.name} lost access to {datastore} Virtual machine lost access to {datastore} Virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in datacenter {datacenter.name} lost access to {datastore}
com.vmware.vc.vcp.VmNetworkFailedEvent Virtual machine lost VM network accessibility error Virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} lost access to {network} Virtual machine {vm.name} on host {host.name} lost access to {network} Virtual machine {vm.name} lost access to {network} Virtual machine lost access to {network} Virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in datacenter {datacenter.name} lost access to {network}
com.vmware.vc.vcp.VmPowerOffHangEvent VM power off hang error HA VM Component Protection could not power off virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} successfully after trying {numTimes} times and will keep trying HA VM Component Protection could not power off virtual machine {vm.name} on host {host.name} successfully after trying {numTimes} times and will keep trying HA VM Component Protection could not power off virtual machine {vm.name} successfully after trying {numTimes} times and will keep trying HA VM Component Protection could not power off virtual machine successfully after trying {numTimes} times and will keep trying HA VM Component Protection could not power off virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in datacenter {datacenter.name} successfully after trying {numTimes} times and will keep trying
com.vmware.vc.vcp.VmWaitForCandidateHostEvent No candidate host to restart error HA VM Component Protection could not find a destination host for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} after waiting {numSecWait} seconds and will keep trying HA VM Component Protection could not find a destination host for virtual machine {vm.name} on host {host.name} after waiting {numSecWait} seconds and will keep trying HA VM Component Protection could not find a destination host for virtual machine {vm.name} after waiting {numSecWait} seconds and will keep trying HA VM Component Protection could not find a destination host for this virtual machine after waiting {numSecWait} seconds and will keep trying HA VM Component Protection could not find a destination host for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in datacenter {datacenter.name} after waiting {numSecWait} seconds and will keep trying
com.vmware.vc.vflash.SsdConfigurationFailedEvent Operation on the SSD device failed error Configuration on disk {disk.path} failed. Reason : {fault.msg} Configuration on disk {disk.path} failed. Reason : {fault.msg}
com.vmware.vc.vm.DstVmMigratedEvent Virtual machine migrated successfully info Virtual machine {vm.name} {newMoRef} in {computeResource.name} was migrated from {oldMoRef} Virtual machine {vm.name} {newMoRef} on host {host.name} was migrated from {oldMoRef} Virtual machine {vm.name} {newMoRef} was migrated from {oldMoRef} Virtual machine {vm.name} {newMoRef} was migrated from {oldMoRef} Virtual machine {vm.name} {newMoRef} in {computeResource.name} in {datacenter.name} was migrated from {oldMoRef}
com.vmware.vc.vm.SrcVmMigratedEvent Virtual machine migrated successfully info Virtual machine {vm.name} {oldMoRef} in {computeResource.name} was migrated to {newMoRef} Virtual machine {vm.name} {oldMoRef} on host {host.name} was migrated to {newMoRef} Virtual machine {vm.name} {oldMoRef} was migrated to {newMoRef} Virtual machine {vm.name} {oldMoRef} was migrated to {newMoRef} Virtual machine {vm.name} {oldMoRef} in {computeResource.name} in {datacenter.name} was migrated to {newMoRef}
com.vmware.vc.vm.VmAdapterResvNotSatisfiedEvent Virtual NIC reservation is not satisfied error Reservation of Virtual NIC {deviceLabel} of machine {vm.name} on host {host.name} is not satisfied Reservation of Virtual NIC {deviceLabel} of machine {vm.name} on host {host.name} is not satisfied Reservation of Virtual NIC {deviceLabel} of machine {vm.name} on this host is not satisfied Reservation of Virtual NIC {deviceLabel} is not satisfied Reservation of Virtual NIC {deviceLabel} of machine {vm.name} on host {host.name} in datacenter {datacenter.name} is not satisfied
com.vmware.vc.vm.VmAdapterResvSatisfiedEvent Virtual NIC reservation is satisfied info Reservation of Virtual NIC {deviceLabel} of machine {vm.name} on host {host.name} is satisfied Reservation of Virtual NIC {deviceLabel} of machine {vm.name} on host {host.name} is satisfied Reservation of Virtual NIC {deviceLabel} of machine {vm.name} on this host is satisfied Reservation of Virtual NIC {deviceLabel} is satisfied Reservation of Virtual NIC {deviceLabel} of machine {vm.name} on host {host.name} in datacenter {datacenter.name} is satisfied
com.vmware.vc.vm.VmStateFailedToRevertToSnapshot Failed to revert the virtual machine state to a snapshot error Failed to revert the execution state of the virtual machine {vm.name} on host {host.name}, in compute resource {computeResource.name} to snapshot {snapshotName}, with ID {snapshotId} Failed to revert the execution state of the virtual machine {vm.name} on host {host.name} to snapshot {snapshotName}, with ID {snapshotId} Failed to revert the execution state of the virtual machine {vm.name} to snapshot {snapshotName}, with ID {snapshotId} Failed to revert the execution state of the virtual machine to snapshot {snapshotName}, with ID {snapshotId} Failed to revert the execution state of the virtual machine {vm.name} on host {host.name}, in compute resource {computeResource.name} to snapshot {snapshotName}, with ID {snapshotId}
com.vmware.vc.vm.VmStateRevertedToSnapshot The virtual machine state has been reverted to a snapshot info The execution state of the virtual machine {vm.name} on host {host.name}, in compute resource {computeResource.name} has been reverted to the state of snapshot {snapshotName}, with ID {snapshotId} The execution state of the virtual machine {vm.name} on host {host.name} has been reverted to the state of snapshot {snapshotName}, with ID {snapshotId} The execution state of the virtual machine {vm.name} has been reverted to the state of snapshot {snapshotName}, with ID {snapshotId} The execution state of the virtual machine has been reverted to the state of snapshot {snapshotName}, with ID {snapshotId} The execution state of the virtual machine {vm.name} on host {host.name}, in compute resource {computeResource.name} has been reverted to the state of snapshot {snapshotName}, with ID {snapshotId}
com.vmware.vc.vmam.VmAppHealthMonitoringStateChangedEvent vSphere HA detected application heartbeat status change warning vSphere HA detected that the application heartbeat status changed to {status.@enum.VirtualMachine.AppHeartbeatStatusType} for {vm.name} on {host.name} in cluster {computeResource.name} vSphere HA detected that the application heartbeat status changed to {status.@enum.VirtualMachine.AppHeartbeatStatusType} for {vm.name} on {host.name} vSphere HA detected that the application heartbeat status changed to {status.@enum.VirtualMachine.AppHeartbeatStatusType} for {vm.name} vSphere HA detected that the application heartbeat status changed to {status.@enum.VirtualMachine.AppHeartbeatStatusType} for this virtual machine vSphere HA detected that the application heartbeat status changed to {status.@enum.VirtualMachine.AppHeartbeatStatusType} for {vm.name} on {host.name} in cluster {computeResource.name} in {datacenter.name}
com.vmware.vc.vmam.VmAppHealthStateChangedEvent vSphere HA detected application state change warning vSphere HA detected that the application state changed to {state.@enum.vm.GuestInfo.AppStateType} for {vm.name} on {host.name} in cluster {computeResource.name} vSphere HA detected that the application state changed to {state.@enum.vm.GuestInfo.AppStateType} for {vm.name} on {host.name} vSphere HA detected that the application state changed to {state.@enum.vm.GuestInfo.AppStateType} for {vm.name} vSphere HA detected that the application state changed to {state.@enum.vm.GuestInfo.AppStateType} for this virtual machine vSphere HA detected that the application state changed to {state.@enum.vm.GuestInfo.AppStateType} for {vm.name} on {host.name} in cluster {computeResource.name} in {datacenter.name}
com.vmware.vc.vsan.ChecksumNotSupportedDiskFoundEvent Virtual SAN disk that does not support checksum error Virtual SAN disk {disk} on {host.name} in cluster {computeResource.name} does not support checksum Virtual SAN disk {disk} on {host.name} does not support checksum Virtual SAN disk {disk} does not support checksum Virtual SAN disk {disk} on {host.name} in cluster {computeResource.name} in datacenter {datacenter.name} does not support checksum Virtual SAN disk {disk} on {host.name} in cluster {computeResource.name} in datacenter {datacenter.name} does not support checksum
com.vmware.vc.vsan.DatastoreNoCapacityEvent Virtual SAN datastore {datastoreName} does not have capacity error Virtual SAN datastore {datastoreName} in cluster {computeResource.name} does not have capacity Virtual SAN datastore {datastoreName} does not have capacity Virtual SAN datastore {datastoreName} in cluster {computeResource.name} in datacenter {datacenter.name} does not have capacity Virtual SAN datastore {datastoreName} in cluster {computeResource.name} in datacenter {datacenter.name} does not have capacity
com.vmware.vc.vsan.HostCommunicationErrorEvent Host cannot communicate with all other nodes in the Virtual SAN enabled cluster error Host {host.name} in cluster {computeResource.name} cannot communicate with all other nodes in the Virtual SAN enabled cluster Host {host.name} cannot communicate with all other nodes in the Virtual SAN enabled cluster Host cannot communicate with all other nodes in the Virtual SAN enabled cluster Host {host.name} in cluster {computeResource.name} in datacenter {datacenter.name} cannot communicate with all other nodes in the Virtual SAN enabled cluster Host {host.name} in cluster {computeResource.name} in datacenter {datacenter.name} cannot communicate with all other nodes in the Virtual SAN enabled cluster
com.vmware.vc.vsan.HostVendorProviderDeregistrationFailedEvent Virtual SAN host vendor provider registration has failed. Reason : {fault.msg}. error Virtual SAN vendor provider {host.name} registration has failed. Reason : {fault.msg}. Virtual SAN vendor provider {host.name} registration has failed. Reason : {fault.msg}. Virtual SAN vendor provider {host.name} registration has failed. Reason : {fault.msg}. Virtual SAN vendor provider {host.name} registration has failed. Reason : {fault.msg}.
com.vmware.vc.vsan.HostVendorProviderRegistrationFailedEvent Virtual SAN host vendor provider registration failed. Reason : {fault.msg}. error Virtual SAN vendor provider {host.name} registration has failed. Reason : {fault.msg}. Virtual SAN vendor provider {host.name} registration has failed. Reason : {fault.msg}. Virtual SAN vendor provider {host.name} registration has failed. Reason : {fault.msg}. Virtual SAN vendor provider {host.name} registration has failed. Reason : {fault.msg}.
com.vmware.vc.vsan.RogueHostFoundEvent Found another host participating in the Virtual SAN service which is not a member of this host's vCenter cluster error Found host(s) {hostString} participating in the Virtual SAN service which is not a member of this host's vCenter cluster {computeResource.name} Found host(s) {hostString} participating in the Virtual SAN service which is not a member of this host's vCenter cluster Found host(s) {hostString} participating in the Virtual SAN service which is not a member of this host's vCenter cluster Found host(s) {hostString} participating in the Virtual SAN service in cluster {computeResource.name} in datacenter {datacenter.name} is not a member of this host's vCenter cluster Found host(s) {hostString} participating in the Virtual SAN service in cluster {computeResource.name} in datacenter {datacenter.name} is not a member of this host's vCenter cluster
com.vmware.vc.vsan.TurnDiskLocatorLedOffFailedEvent Failed to turn off the disk locator LED error Failed to turn off the locator LED of disk {disk.path}. Reason : {fault.msg} Failed to turn off the locator LED of disk {disk.path}. Reason : {fault.msg}
com.vmware.vc.vsan.TurnDiskLocatorLedOnFailedEvent Failed to turn on the disk locator LED error Failed to turn on the locator LED of disk {disk.path}. Reason : {fault.msg} Failed to turn on the locator LED of disk {disk.path}. Reason : {fault.msg}
com.vmware.vc.vsan.VsanHostNeedsUpgradeEvent Virtual SAN cluster needs disk format upgrade warning Virtual SAN cluster {computeResource.name} has one or more hosts that need disk format upgrade: {host}. For more detailed information of Virtual SAN upgrade, please see the 'Virtual SAN upgrade procedure' section in the documentation Virtual SAN cluster has one or more hosts for which disk format upgrade is recommended: {host}. For more detailed information of Virtual SAN upgrade, please see the 'Virtual SAN upgrade procedure' section in the documentation Virtual SAN cluster {computeResource.name} has one or more hosts that need disk format upgrade: {host}. For more detailed information of Virtual SAN upgrade, please see the 'Virtual SAN upgrade procedure' section in the documentation Virtual SAN cluster {computeResource.name} has one or more hosts that need disk format upgrade: {host}. For more detailed information of Virtual SAN upgrade, please see the 'Virtual SAN upgrade procedure' section in the documentation
com.vmware.vim.vsm.dependency.bind.vApp vService dependency bound info vService dependency '{dependencyName}' on vApp '{targetName}' bound to provider '{providerName}'
com.vmware.vim.vsm.dependency.bind.vm vService dependency bound info vService dependency '{dependencyName}' on '{vm.name}' bound to provider '{providerName}'
com.vmware.vim.vsm.dependency.create.vApp vService dependency created info Created vService dependency '{dependencyName}' with type '{dependencyType}' on vApp '{targetName}'
com.vmware.vim.vsm.dependency.create.vm vService dependency created info Created vService dependency '{dependencyName}' with type '{dependencyType}' on '{vm.name}'
com.vmware.vim.vsm.dependency.destroy.vApp vService dependency destroyed info Destroyed vService dependency '{dependencyName}' on vApp '{targetName}'
com.vmware.vim.vsm.dependency.destroy.vm vService dependency destroyed info Destroyed vService dependency '{dependencyName}' on '{vm.name}'
com.vmware.vim.vsm.dependency.reconfigure.vApp vService dependency reconfigured info Reconfigured vService dependency '{dependencyName}' on vApp '{targetName}'
com.vmware.vim.vsm.dependency.reconfigure.vm vService dependency reconfigured info Reconfigured vService dependency '{dependencyName}' on '{vm.name}'
com.vmware.vim.vsm.dependency.unbind.vApp vService dependency unbound info vService dependency '{dependencyName}' on vApp '{targetName}' unbound from provider '{providerName}'
com.vmware.vim.vsm.dependency.unbind.vm vService dependency unbound info vService dependency '{dependencyName}' on '{vm.name}' unbound from provider '{providerName}'
com.vmware.vim.vsm.dependency.update.vApp vService dependency updated info Updated vService dependency '{dependencyName}' on vApp '{targetName}'
com.vmware.vim.vsm.dependency.update.vm vService dependency updated info Updated vService dependency '{dependencyName}' on '{vm.name}'
com.vmware.vim.vsm.provider.register vService provider registered info vService provider '{providerName}' with type '{providerType}' registered for extension '{extensionKey}'
com.vmware.vim.vsm.provider.unregister vService provider unregistered info vService provider '{providerName}' with type '{providerType}' unregistered for extension '{extensionKey}'
com.vmware.vim.vsm.provider.update vService provider updated info Updating vService provider '{providerName}' registered for extension '{extensionKey}'
esx.audit.account.locked Remote access for an ESXi local user account has been locked temporarilly due to multiple failed login attempts. warning Remote access for ESXi local user account '{1}' has been locked for {2} seconds after {3} failed login attempts.
esx.audit.account.loginfailures Multiple remote login failures detected for an ESXi local user account. warning Multiple remote login failures detected for ESXi local user account '{1}'.
esx.audit.dcui.login.failed Login authentication on DCUI failed error Authentication of user {1} has failed. Please consult ESXi Embedded and vCenter Server Setup Guide or follow the Ask VMware link for more information.
esx.audit.dcui.login.passwd.changed DCUI login password changed. info Login password for user {1} has been changed. Please consult ESXi Embedded and vCenter Server Setup Guide or follow the Ask VMware link for more information.
esx.audit.dcui.network.restart Restarting network through DCUI. info A management interface {1} has been restarted. Please consult ESXi Embedded and vCenter Server Setup Guide or follow the Ask VMware link for more information.
esx.audit.esxcli.host.poweroff Powering off host through esxcli warning The host is being powered off through esxcli. Reason for powering off: {1}. Please consult vSphere Documentation Center or follow the Ask VMware link for more information.
esx.audit.esxcli.host.restart Rebooting host through esxcli warning The host is being rebooted through esxcli. Reason for reboot: {1}. Please consult vSphere Documentation Center or follow the Ask VMware link for more information.
esx.audit.esximage.hostacceptance.changed Host acceptance level changed info Host acceptance level changed from {1} to {2}
esx.audit.esximage.install.securityalert SECURITY ALERT: Installing image profile. warning SECURITY ALERT: Installing image profile '{1}' with {2}.
esx.audit.esximage.profile.install.successful Successfully installed image profile. info Successfully installed image profile '{1}'. Installed {2} VIB(s), removed {3} VIB(s). Please use 'esxcli software profile get' or see log for more detail about the transaction.
esx.audit.esximage.profile.update.successful Successfully updated host to new image profile. info Successfully updated host to image profile '{1}'. Installed {2} VIB(s), removed {3} VIB(s). Please use 'esxcli software profile get' or see log for more detail about the transaction.
esx.audit.esximage.vib.install.successful Successfully installed VIBs. info Successfully installed {1} VIB(s), removed {2} VIB(s). Please use 'esxcli software profile get' or see log for more detail about the transaction.
esx.audit.esximage.vib.remove.successful Successfully removed VIBs info Successfully removed {1} VIB(s). Please use 'esxcli software profile get' or see log for more detail about the transaction.
esx.audit.host.maxRegisteredVMsExceeded The number of virtual machines registered on the host exceeded limit. warning The number of virtual machines registered on host {host.name} in cluster {computeResource.name} exceeded limit: {current} registered, {limit} is the maximum supported. The number of virtual machines registered on host {host.name} exceeded limit: {current} registered, {limit} is the maximum supported. The number of virtual machines registered exceeded limit: {current} registered, {limit} is the maximum supported. The number of virtual machines registered on host {host.name} in cluster {computeResource.name} in {datacenter.name} exceeded limit: {current} registered, {limit} is the maximum supported.
esx.audit.net.firewall.config.changed Firewall configuration has changed. info Firewall configuration has changed. Operation '{1}' for rule set {2} succeeded.
esx.audit.net.firewall.enabled Firewall has been enabled for port. info Firewall has been enabled for port {1}.
esx.audit.net.firewall.port.hooked Port is now protected by Firewall. info Port {1} is now protected by Firewall.
esx.audit.net.firewall.port.removed Port is no longer protected with Firewall. warning Port {1} is no longer protected with Firewall.
esx.audit.net.lacp.disable LACP disabled info LACP for VDS {1} is disabled.
esx.audit.net.lacp.enable LACP eabled info LACP for VDS {1} is enabled.
esx.audit.net.lacp.uplink.connected uplink is connected info LACP info: uplink {1} on VDS {2} got connected.
esx.audit.uw.secpolicy.alldomains.level.changed Enforcement level changed for all security domains. warning The enforcement level for all security domains has been changed to {1}. The enforcement level must always be set to enforcing.
esx.audit.uw.secpolicy.domain.level.changed Enforcement level changed for security domain. warning The enforcement level for security domain {1} has been changed to {2}. The enforcement level must always be set to enforcing.
esx.audit.vmfs.volume.mounted File system mounted. info File system {1} on volume {2} has been mounted in {3} mode on this host.
esx.audit.vmfs.volume.umounted LVM volume un-mounted. info The volume {1} has been safely un-mounted. The datastore is no longer accessible on this host.
esx.clear.net.connectivity.restored Restored network connectivity to portgroups info Network connectivity restored on virtual switch {1}, portgroups: {2}. Physical NIC {3} is up.
esx.clear.net.dvport.connectivity.restored Restored Network Connectivity to DVPorts info Network connectivity restored on DVPorts: {1}. Physical NIC {2} is up.
esx.clear.net.dvport.redundancy.restored Restored Network Redundancy to DVPorts info Uplink redundancy restored on DVPorts: {1}. Physical NIC {2} is up.
esx.clear.net.lacp.lag.transition.up lag transition up info LACP info: LAG {1} on VDS {2} is up.
esx.clear.net.lacp.uplink.transition.up uplink transition up info LACP info: uplink {1} on VDS {2} is moved into link aggregation group.
esx.clear.net.lacp.uplink.unblocked uplink is unblocked info LACP info: uplink {1} on VDS {2} is unblocked.
esx.clear.net.redundancy.restored Restored uplink redundancy to portgroups info Uplink redundancy restored on virtual switch {1}, portgroups: {2}. Physical NIC {3} is up.
esx.clear.net.vmnic.linkstate.up Link state up info Physical NIC {1} linkstate is up.
esx.clear.scsi.device.io.latency.improved Scsi Device I/O Latency has improved info Device {1} performance has improved. I/O latency reduced from {2} microseconds to {3} microseconds.
esx.clear.scsi.device.state.on Device has been turned on administratively. info Device {1}, has been turned on administratively.
esx.clear.scsi.device.state.permanentloss.deviceonline Device that was permanently inaccessible is now online. info Device {1}, that was permanently inaccessible is now online. No data consistency guarantees.
esx.clear.storage.apd.exit Exited the All Paths Down state info Device or filesystem with identifier {1} has exited the All Paths Down state.
esx.clear.storage.connectivity.restored Restored connectivity to storage device info Connectivity to storage device {1} (Datastores: {2}) restored. Path {3} is active again.
esx.clear.storage.redundancy.restored Restored path redundancy to storage device info Path redundancy to storage device {1} (Datastores: {2}) restored. Path {3} is active again.
esx.problem.3rdParty.error A 3rd party component on ESXi has reported an error. error A 3rd party component, {1}, running on ESXi has reported an error. Please follow the knowledge base link ({2}) to see the steps to remedy the problem as reported by {3}. The message reported is: {4}.
esx.problem.3rdParty.info A 3rd party component on ESXi has reported an informational event. info A 3rd party component, {1}, running on ESXi has reported an informational event. If needed, please follow the knowledge base link ({2}) to see the steps to remedy the problem as reported by {3}. The message reported is: {4}.
esx.problem.3rdParty.warning A 3rd party component on ESXi has reported a warning. warning A 3rd party component, {1}, running on ESXi has reported a warning related to a problem. Please follow the knowledge base link ({2}) to see the steps to remedy the problem as reported by {3}. The message reported is: {4}.
esx.problem.apei.bert.memory.error.corrected A corrected memory error occurred error A corrected memory error occurred in last boot. The following details were reported. Physical Addr: {1}, Physical Addr Mask: {2}, Node: {3}, Card: {4}, Module: {5}, Bank: {6}, Device: {7}, Row: {8}, Column: {9} Error type: {10}
esx.problem.apei.bert.memory.error.fatal A fatal memory error occurred error A fatal memory error occurred in the last boot. The following details were reported. Physical Addr: {1}, Physical Addr Mask: {2}, Node: {3}, Card: {4}, Module: {5}, Bank: {6}, Device: {7}, Row: {8}, Column: {9} Error type: {10}
esx.problem.apei.bert.memory.error.recoverable A recoverable memory error occurred error A recoverable memory error occurred in last boot. The following details were reported. Physical Addr: {1}, Physical Addr Mask: {2}, Node: {3}, Card: {4}, Module: {5}, Bank: {6}, Device: {7}, Row: {8}, Column: {9} Error type: {10}
esx.problem.apei.bert.pcie.error.corrected A corrected PCIe error occurred error A corrected PCIe error occurred in last boot. The following details were reported. Port Type: {1}, Device: {2}, Bus #: {3}, Function: {4}, Slot: {5}, Device Vendor: {6}, Version: {7}, Command Register: {8}, Status Register: {9}.
esx.problem.apei.bert.pcie.error.fatal A fatal PCIe error occurred error Platform encounterd a fatal PCIe error in last boot. The following details were reported. Port Type: {1}, Device: {2}, Bus #: {3}, Function: {4}, Slot: {5}, Device Vendor: {6}, Version: {7}, Command Register: {8}, Status Register: {9}.
esx.problem.apei.bert.pcie.error.recoverable A recoverable PCIe error occurred error A recoverable PCIe error occurred in last boot. The following details were reported. Port Type: {1}, Device: {2}, Bus #: {3}, Function: {4}, Slot: {5}, Device Vendor: {6}, Version: {7}, Command Register: {8}, Status Register: {9}.
esx.problem.application.core.dumped An application running on ESXi host has crashed and a core file was created. warning An application ({1}) running on ESXi host has crashed ({2} time(s) so far). A core file might have been created at {3}.
esx.problem.coredump.capacity.insufficient The storage capacity of the coredump targets is insufficient to capture a complete coredump. warning The storage capacity of the coredump targets is insufficient to capture a complete coredump. Recommended coredump capacity is {1} MiB. The storage capacity of the coredump targets is insufficient to capture a complete coredump. Recommended coredump capacity is {1} MiB.
esx.problem.coredump.copyspace The free space available in default coredump copy location is insufficient to copy new coredumps. warning The free space available in default coredump copy location is insufficient to copy new coredumps. Recommended free space is {1} MiB. The free space available in default coredump copy location is insufficient to copy new coredumps. Recommended free space is {1} MiB.
esx.problem.coredump.extraction.failed.nospace The given partition has insufficient amount of free space to extract the coredump. warning The given partition has insufficient amount of free space to extract the coredump. At least {1} MiB is required. The given partition has insufficient amount of free space to extract the coredump. At least {1} MiB is required.
esx.problem.cpu.smp.ht.invalid Disabling HyperThreading due to invalid configuration: Number of threads: {1}, Number of PCPUs: {2}. error Disabling HyperThreading due to invalid configuration: Number of threads: {1}, Number of PCPUs: {2}.
esx.problem.cpu.smp.ht.numpcpus.max Found {1} PCPUs, but only using {2} of them due to specified limit. error Found {1} PCPUs, but only using {2} of them due to specified limit.
esx.problem.cpu.smp.ht.partner.missing Disabling HyperThreading due to invalid configuration: HT partner {1} is missing from PCPU {2}. error Disabling HyperThreading due to invalid configuration: HT partner {1} is missing from PCPU {2}.
esx.problem.dhclient.lease.none Unable to obtain a DHCP lease. error Unable to obtain a DHCP lease on interface {1}.
esx.problem.dhclient.lease.offered.error No expiry time on offered DHCP lease. error No expiry time on offered DHCP lease from {1}.
esx.problem.esximage.install.error Could not install image profile. error Could not install image profile: {1}
esx.problem.esximage.install.invalidhardware Host doesn't meet image profile hardware requirements. error Host doesn't meet image profile '{1}' hardware requirements: {2}
esx.problem.esximage.install.stage.error Could not stage image profile. error Could not stage image profile '{1}': {2}
esx.problem.hardware.acpi.interrupt.routing.device.invalid Skipping interrupt routing entry with bad device number: {1}. This is a BIOS bug. error Skipping interrupt routing entry with bad device number: {1}. This is a BIOS bug.
esx.problem.hardware.acpi.interrupt.routing.pin.invalid Skipping interrupt routing entry with bad device pin: {1}. This is a BIOS bug. error Skipping interrupt routing entry with bad device pin: {1}. This is a BIOS bug.
esx.problem.hardware.ioapic.missing IOAPIC Num {1} is missing. Please check BIOS settings to enable this IOAPIC. error IOAPIC Num {1} is missing. Please check BIOS settings to enable this IOAPIC.
esx.problem.hostd.core.dumped Hostd crashed and a core file was created. warning {1} crashed ({2} time(s) so far) and a core file might have been created at {3}. This might have caused connections to the host to be dropped.
esx.problem.iorm.badversion Storage I/O Control version mismatch info Host {1} cannot participate in Storage I/O Control(SIOC) on datastore {2} because the version number {3} of the SIOC agent on this host is incompatible with number {4} of its counterparts on other hosts connected to this datastore.
esx.problem.iorm.nonviworkload Unmanaged workload detected on SIOC-enabled datastore info An unmanaged I/O workload is detected on a SIOC-enabled datastore: {1}.
esx.problem.migrate.vmotion.server.pending.cnx.listen.socket.shutdown Error with migration listen socket error The ESXi host's vMotion network server encountered an error while monitoring incoming network connections. Shutting down listener socket. vMotion might not be possible with this host until vMotion is manually re-enabled. Failure status: {1}
esx.problem.net.connectivity.lost Lost Network Connectivity error Lost network connectivity on virtual switch {1}. Physical NIC {2} is down. Affected portgroups:{3}.
esx.problem.net.dvport.connectivity.lost Lost Network Connectivity to DVPorts error Lost network connectivity on DVPorts: {1}. Physical NIC {2} is down.
esx.problem.net.dvport.redundancy.degraded Network Redundancy Degraded on DVPorts warning Uplink redundancy degraded on DVPorts: {1}. Physical NIC {2} is down.
esx.problem.net.dvport.redundancy.lost Lost Network Redundancy on DVPorts warning Lost uplink redundancy on DVPorts: {1}. Physical NIC {2} is down.
esx.problem.net.e1000.tso6.notsupported No IPv6 TSO support error Guest-initiated IPv6 TCP Segmentation Offload (TSO) packets ignored. Manually disable TSO inside the guest operating system in virtual machine {1}, or use a different virtual adapter.
esx.problem.net.fence.port.badfenceid Invalid fenceId configuration on dvPort error VMkernel failed to set fenceId {1} on distributed virtual port {2} on switch {3}. Reason: invalid fenceId.
esx.problem.net.fence.resource.limited Maximum number of fence networks or ports error Vmkernel failed to set fenceId {1} on distributed virtual port {2} on switch {3}. Reason: maximum number of fence networks or ports have been reached.
esx.problem.net.fence.switch.unavailable Switch fence property is not set error Vmkernel failed to set fenceId {1} on distributed virtual port {2} on switch {3}. Reason: dvSwitch fence property is not set.
esx.problem.net.firewall.config.failed Firewall configuration operation failed. The changes were not applied. error Firewall configuration operation '{1}' failed. The changes were not applied to rule set {2}.
esx.problem.net.firewall.port.hookfailed Adding port to Firewall failed. error Adding port {1} to Firewall failed.
esx.problem.net.gateway.set.failed Failed to set gateway error Cannot connect to the specified gateway {1}. Failed to set it.
esx.problem.net.heap.belowthreshold Network memory pool threshold warning {1} free size dropped below {2} percent.
esx.problem.net.lacp.lag.transition.down lag transition down warning LACP warning: LAG {1} on VDS {2} is down.
esx.problem.net.lacp.peer.noresponse No peer response error LACP error: No peer response on uplink {1} for VDS {2}.
esx.problem.net.lacp.policy.incompatible Current teaming policy is incompatible error LACP error: Current teaming policy on VDS {1} is incompatible, supported is IP hash only.
esx.problem.net.lacp.policy.linkstatus Current teaming policy is incompatible error LACP error: Current teaming policy on VDS {1} is incompatible, supported link failover detection is link status only.
esx.problem.net.lacp.uplink.blocked uplink is blocked warning LACP warning: uplink {1} on VDS {2} is blocked.
esx.problem.net.lacp.uplink.disconnected uplink is disconnected warning LACP warning: uplink {1} on VDS {2} got disconnected.
esx.problem.net.lacp.uplink.fail.duplex uplink duplex mode is different error LACP error: Duplex mode across all uplink ports must be full, VDS {1} uplink {2} has different mode.
esx.problem.net.lacp.uplink.fail.speed uplink speed is different error LACP error: Speed across all uplink ports must be same, VDS {1} uplink {2} has different speed.
esx.problem.net.lacp.uplink.inactive All uplinks must be active error LACP error: All uplinks on VDS {1} must be active.
esx.problem.net.lacp.uplink.transition.down uplink transition down warning LACP warning: uplink {1} on VDS {2} is moved out of link aggregation group.
esx.problem.net.migrate.bindtovmk Invalid vmknic specified in /Migrate/Vmknic warning The ESX advanced configuration option /Migrate/Vmknic is set to an invalid vmknic: {1}. /Migrate/Vmknic specifies a vmknic that vMotion binds to for improved performance. Update the configuration option with a valid vmknic. Alternatively, if you do not want vMotion to bind to a specific vmknic, remove the invalid vmknic and leave the option blank.
esx.problem.net.migrate.unsupported.latency Unsupported vMotion network latency detected warning ESXi has detected {1}ms round-trip vMotion network latency between host {2} and {3}. High latency vMotion networks are supported only if both ESXi hosts have been configured for vMotion latency tolerance.
esx.problem.net.portset.port.full Failed to apply for free ports error Portset {1} has reached the maximum number of ports ({2}). Cannot apply for any more free ports.
esx.problem.net.portset.port.vlan.invalidid Vlan ID of the port is invalid error {1} VLANID {2} is invalid. VLAN ID must be between 0 and 4095.
esx.problem.net.proxyswitch.port.unavailable Virtual NIC connection to switch failed warning Virtual NIC with hardware address {1} failed to connect to distributed virtual port {2} on switch {3}. There are no more ports available on the host proxy switch.
esx.problem.net.redundancy.degraded Network Redundancy Degraded warning Uplink redundancy degraded on virtual switch {1}. Physical NIC {2} is down. Affected portgroups:{3}.
esx.problem.net.redundancy.lost Lost Network Redundancy warning Lost uplink redundancy on virtual switch {1}. Physical NIC {2} is down. Affected portgroups:{3}.
esx.problem.net.uplink.mtu.failed Failed to set MTU on an uplink warning VMkernel failed to set the MTU value {1} on the uplink {2}.
esx.problem.net.vmknic.ip.duplicate A duplicate IP address was detected on a vmknic interface warning A duplicate IP address was detected for {1} on the interface {2}. The current owner is {3}.
esx.problem.net.vmnic.linkstate.down Link state down warning Physical NIC {1} linkstate is down.
esx.problem.net.vmnic.linkstate.flapping Link state unstable warning Taking down physical NIC {1} because the link is unstable.
esx.problem.net.vmnic.watchdog.reset Nic Watchdog Reset warning Uplink {1} has recovered from a transient failure due to watchdog timeout
esx.problem.ntpd.clock.correction.error NTP daemon stopped. Time correction out of bounds. error NTP daemon stopped. Time correction {1} > {2} seconds. Manually set the time and restart ntpd.
esx.problem.pageretire.platform.retire.request Memory page retirement requested by platform firmware. info Memory page retirement requested by platform firmware. FRU ID: {1}. Refer to System Hardware Log: {2}
esx.problem.pageretire.selectedmpnthreshold.host.exceeded Number of host physical memory pages selected for retirement exceeds threshold. warning Number of host physical memory pages that have been selected for retirement ({1}) exceeds threshold ({2}).
esx.problem.scratch.partition.size.small Size of scratch partition is too small. warning Size of scratch partition {1} is too small. Recommended scratch partition size is {2} MiB. Size of scratch partition {1} is too small. Recommended scratch partition size is {2} MiB.
esx.problem.scratch.partition.unconfigured No scratch partition has been configured. warning No scratch partition has been configured. Recommended scratch partition size is {} MiB. No scratch partition has been configured. Recommended scratch partition size is {} MiB.
esx.problem.scsi.device.close.failed Scsi Device close failed. warning Failed to close the device {1} properly, plugin {2}.
esx.problem.scsi.device.detach.failed Device detach failed warning Detach failed for device :{1}. Exceeded the number of devices that can be detached, please cleanup stale detach entries.
esx.problem.scsi.device.filter.attach.failed Failed to attach filter to device. warning Failed to attach filters to device '%s' during registration. Plugin load failed or the filter rules are incorrect.
esx.problem.scsi.device.io.bad.plugin.type Plugin trying to issue command to device does not have a valid storage plugin type. warning Bad plugin type for device {1}, plugin {2}
esx.problem.scsi.device.io.inquiry.failed Failed to obtain INQUIRY data from the device warning Failed to get standard inquiry for device {1} from Plugin {2}.
esx.problem.scsi.device.io.latency.high Scsi Device I/O Latency going high warning Device {1} performance has deteriorated. I/O latency increased from average value of {2} microseconds to {3} microseconds.
esx.problem.scsi.device.io.qerr.change.config QErr cannot be changed on device. Please change it manually on the device if possible. warning QErr set to 0x{1} for device {2}. This may cause unexpected behavior. The system is not configured to change the QErr setting of device. The QErr value supported by system is 0x{3}. Please check the SCSI ChangeQErrSetting configuration value for ESX.
esx.problem.scsi.device.io.qerr.changed Scsi Device QErr setting changed warning QErr set to 0x{1} for device {2}. This may cause unexpected behavior. The device was originally configured to the supported QErr setting of 0x{3}, but this has been changed and could not be changed back.
esx.problem.scsi.device.is.local.failed Plugin's isLocal entry point failed warning Failed to verify if the device {1} from plugin {2} is a local - not shared - device
esx.problem.scsi.device.is.pseudo.failed Plugin's isPseudo entry point failed warning Failed to verify if the device {1} from plugin {2} is a pseudo device
esx.problem.scsi.device.is.ssd.failed Plugin's isSSD entry point failed warning Failed to verify if the device {1} from plugin {2} is a Solid State Disk device
esx.problem.scsi.device.limitreached Maximum number of storage devices error The maximum number of supported devices of {1} has been reached. A device from plugin {2} could not be created.
esx.problem.scsi.device.state.off Device has been turned off administratively. info Device {1}, has been turned off administratively.
esx.problem.scsi.device.state.permanentloss Device has been removed or is permanently inaccessible. error Device {1} has been removed or is permanently inaccessible. Affected datastores (if any): {2}.
esx.problem.scsi.device.state.permanentloss.noopens Permanently inaccessible device has no more opens. info Permanently inaccessible device {1} has no more opens. It is now safe to unmount datastores (if any) {2} and delete the device.
esx.problem.scsi.device.state.permanentloss.pluggedback Device has been plugged back in after being marked permanently inaccessible. error Device {1} has been plugged back in after being marked permanently inaccessible. No data consistency guarantees.
esx.problem.scsi.device.state.permanentloss.withreservationheld Device has been removed or is permanently inaccessible. error Device {1} has been removed or is permanently inaccessible, while holding a reservation. Affected datastores (if any): {2}.
esx.problem.scsi.device.thinprov.atquota Thin Provisioned Device Nearing Capacity warning Space utilization on thin-provisioned device {1} exceeded configured threshold. Affected datastores (if any): {2}.
esx.problem.scsi.scsipath.badpath.unreachpe vVol PE path going out of vVol-incapable adapter error Sanity check failed for path {1}. The path is to a vVol PE, but it goes out of adapter {2} which is not PE capable. Path dropped.
esx.problem.scsi.scsipath.badpath.unsafepe Cannot safely determine vVol PE error Sanity check failed for path {1}. Could not safely determine if the path is to a vVol PE. Path dropped.
esx.problem.scsi.scsipath.limitreached Maximum number of storage paths error The maximum number of supported paths of {1} has been reached. Path {2} could not be added.
esx.problem.scsi.unsupported.plugin.type Storage plugin of unsupported type tried to register. warning Scsi Device Allocation not supported for plugin type {1}
esx.problem.storage.apd.start All paths are down warning Device or filesystem with identifier {1} has entered the All Paths Down state.
esx.problem.storage.apd.timeout All Paths Down timed out, I/Os will be fast failed warning Device or filesystem with identifier {1} has entered the All Paths Down Timeout state after being in the All Paths Down state for {2} seconds. I/Os will now be fast failed.
esx.problem.storage.connectivity.devicepor Frequent PowerOn Reset Unit Attention of Storage Path warning Frequent PowerOn Reset Unit Attentions are occurring on device {1}. This might indicate a storage problem. Affected datastores: {2}
esx.problem.storage.connectivity.lost Lost Storage Connectivity error Lost connectivity to storage device {1}. Path {2} is down. Affected datastores: {3}.
esx.problem.storage.connectivity.pathpor Frequent PowerOn Reset Unit Attention of Storage Path warning Frequent PowerOn Reset Unit Attentions are occurring on path {1}. This might indicate a storage problem. Affected device: {2}. Affected datastores: {3}
esx.problem.storage.connectivity.pathstatechanges Frequent State Changes of Storage Path info Frequent path state changes are occurring for path {1}. This might indicate a storage problem. Affected device: {2}. Affected datastores: {3}
esx.problem.storage.iscsi.discovery.connect.error iSCSI discovery target login connection problem error iSCSI discovery to {1} on {2} failed. The iSCSI Initiator could not establish a network connection to the discovery address.
esx.problem.storage.iscsi.discovery.login.error iSCSI Discovery target login error error iSCSI discovery to {1} on {2} failed. The Discovery target returned a login error of: {3}.
esx.problem.storage.iscsi.target.connect.error iSCSI Target login connection problem error Login to iSCSI target {1} on {2} failed. The iSCSI initiator could not establish a network connection to the target.
esx.problem.storage.iscsi.target.login.error iSCSI Target login error error Login to iSCSI target {1} on {2} failed. Target returned login error of: {3}.
esx.problem.storage.iscsi.target.permanently.lost iSCSI target permanently removed error The iSCSI target {2} was permanently removed from {1}.
esx.problem.storage.redundancy.degraded Degraded Storage Path Redundancy warning Path redundancy to storage device {1} degraded. Path {2} is down. Affected datastores: {3}.
esx.problem.storage.redundancy.lost Lost Storage Path Redundancy warning Lost path redundancy to storage device {1}. Path {2} is down. Affected datastores: {3}.
esx.problem.vfat.filesystem.full.other A VFAT filesystem is full. error The VFAT filesystem {1} (UUID {2}) is full.
esx.problem.vfat.filesystem.full.scratch A VFAT filesystem, being used as the host's scratch partition, is full. error The host's scratch partition, which is the VFAT filesystem {1} (UUID {2}), is full.
esx.problem.visorfs.inodetable.full The root filesystem's file table is full. error The root filesystem's file table is full. As a result, the file {1} could not be created by the application '{2}'.
esx.problem.visorfs.ramdisk.full A ramdisk is full. error The ramdisk '{1}' is full. As a result, the file {2} could not be written.
esx.problem.visorfs.ramdisk.inodetable.full A ramdisk's file table is full. error The file table of the ramdisk '{1}' is full. As a result, the file {2} could not be created by the application '{3}'.
esx.problem.vm.kill.unexpected.fault.failure A VM could not fault in the a page. The VM is terminated as further progress is impossible. error The VM using the config file {1} could not fault in a guest physical page from the hypervisor level swap file at {2}. The VM is terminated as further progress is impossible.
esx.problem.vm.kill.unexpected.forcefulPageRetire A VM did not respond to swap actions and is forcefully powered off to prevent system instability. error The VM using the config file {1} contains the host physical page {2} which was scheduled for immediate retirement. To avoid system instability the VM is forcefully powered off.
esx.problem.vm.kill.unexpected.noSwapResponse A VM did not respond to swap actions and is forcefully powered off to prevent system instability. error The VM using the config file {1} did not respond to {2} swap actions in {3} seconds and is forcefully powered off to prevent system instability.
esx.problem.vm.kill.unexpected.vmtrack A VM is allocating too many pages while system is critically low in free memory. It is forcefully terminated to prevent system instability. error The VM using the config file {1} is allocating too many pages while system is critically low in free memory. It is forcefully terminated to prevent system instability.
esx.problem.vmfs.ats.incompatibility.detected Multi-extent ATS-only VMFS Volume unable to use ATS error Multi-extent ATS-only volume '{1}' ({2}) is unable to use ATS because HardwareAcceleratedLocking is disabled on this host: potential for introducing filesystem corruption. Volume should not be used from other hosts.
esx.problem.vmfs.ats.support.lost Device Backing VMFS has lost ATS Support error ATS-Only VMFS volume '{1}' not mounted. Host does not support ATS or ATS initialization has failed.
esx.problem.vmfs.error.volume.is.locked VMFS Locked By Remote Host error Volume on device {1} is locked, possibly because some remote host encountered an error during a volume operation and could not recover.
esx.problem.vmfs.extent.offline Device backing an extent of a file system is offline. error An attached device {1} may be offline. The file system {2} is now in a degraded state. While the datastore is still available, parts of data that reside on the extent that went offline might be inaccessible.
esx.problem.vmfs.extent.online Device backing an extent of a file system came online info Device {1} backing file system {2} came online. This extent was previously offline. All resources on this device are now available.
esx.problem.vmfs.heartbeat.recovered VMFS Volume Connectivity Restored info Successfully restored access to volume {1} ({2}) following connectivity issues.
esx.problem.vmfs.heartbeat.timedout VMFS Volume Connectivity Degraded info Lost access to volume {1} ({2}) due to connectivity issues. Recovery attempt is in progress and outcome will be reported shortly.
esx.problem.vmfs.heartbeat.unrecoverable VMFS Volume Connectivity Lost error Lost connectivity to volume {1} ({2}) and subsequent recovery attempts have failed.
esx.problem.vmfs.journal.createfailed No Space To Create VMFS Journal error No space for journal on volume {1} ({2}). Volume will remain in read-only metadata mode with limited write support until journal can be created.
esx.problem.vmfs.lock.corruptondisk VMFS Lock Corruption Detected error At least one corrupt on-disk lock was detected on volume {1} ({2}). Other regions of the volume might be damaged too.
esx.problem.vmfs.lockmode.inconsistency.detected Inconsistent VMFS lockmode detected. error Inconsistent lockmode change detected for VMFS volume '{1} ({2})': volume was configured for {3} lockmode at time of open and now it is configured for {4} lockmode but this host is not using {5} lockmode. Protocol error during ATS transition. Volume descriptor refresh operations will fail until this host unmounts and remounts the volume. Inconsistent lockmode change detected for VMFS volume '{1} ({2})': volume was configured for {3} lockmode at time of open and now it is configured for {4} lockmode but this host is not using {5} lockmode. Protocol error during ATS transition. Volume descriptor refresh operations will fail until this host unmounts and remounts the volume. Inconsistent lockmode change detected for VMFS volume '{1} ({2})': volume was configured for {3} lockmode at time of open and now it is configured for {4} lockmode but this host is not using {5} lockmode. Protocol error during ATS transition. Volume descriptor refresh operations will fail until this host unmounts and remounts the volume.
esx.problem.vmfs.nfs.server.disconnect Lost connection to NFS server error Lost connection to server {1} mount point {2} mounted as {3} ({4}).
esx.problem.vmfs.nfs.server.restored Restored connection to NFS server info Restored connection to server {1} mount point {2} mounted as {3} ({4}).
esx.problem.vmfs.resource.corruptondisk VMFS Resource Corruption Detected error At least one corrupt resource metadata region was detected on volume {1} ({2}). Other regions of the volume might be damaged too.
esx.problem.vmfs.spanned.lockmode.inconsistency.detected Inconsistent VMFS lockmode detected on spanned volume. error Inconsistent lockmode change detected for spanned VMFS volume '{1} ({2})': volume was configured for {3} lockmode at time of open and now it is configured for {4} lockmode but this host is not using {5} lockmode. All operations on this volume will fail until this host unmounts and remounts the volume. Inconsistent lockmode change detected for spanned VMFS volume '{1} ({2})': volume was configured for {3} lockmode at time of open and now it is configured for {4} lockmode but this host is not using {5} lockmode. All operations on this volume will fail until this host unmounts and remounts the volume. Inconsistent lockmode change detected for spanned VMFS volume '{1} ({2})': volume was configured for {3} lockmode at time of open and now it is configured for {4} lockmode but this host is not using {5} lockmode. All operations on this volume will fail until this host unmounts and remounts the volume.
esx.problem.vmfs.spanstate.incompatibility.detected Incompatible VMFS span state detected. error Incompatible span change detected for VMFS volume '{1} ({2})': volume was not spanned at time of open but now it is, and this host is using ATS-only lockmode but the volume is not ATS-only. Volume descriptor refresh operations will fail until this host unmounts and remounts the volume. Incompatible span change detected for VMFS volume '{1} ({2})': volume was not spanned at time of open but now it is, and this host is using ATS-only lockmode but the volume is not ATS-only. Volume descriptor refresh operations will fail until this host unmounts and remounts the volume. Incompatible span change detected for VMFS volume '{1} ({2})': volume was not spanned at time of open but now it is, and this host is using ATS-only lockmode but the volume is not ATS-only. Volume descriptor refresh operations will fail until this host unmounts and remounts the volume.
esx.problem.vmsyslogd.remote.failure Remote logging host has become unreachable. error The host "{1}" has become unreachable. Remote logging to this host has stopped.
esx.problem.vmsyslogd.storage.logdir.invalid The configured log directory cannot be used. The default directory will be used instead. error The configured log directory {1} cannot be used. The default directory {2} will be used instead.
esx.problem.vmsyslogd.unexpected Log daemon has failed for an unexpected reason. error Log daemon has failed for an unexpected reason: {1}
esx.problem.vpxa.core.dumped Vpxa crashed and a core file was created. warning {1} crashed ({2} time(s) so far) and a core file might have been created at {3}. This might have caused connections to the host to be dropped.
hbr.primary.AppQuiescedDeltaCompletedEvent Application consistent sync completed. info Application consistent sync completed for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name}. Application consistent sync completed for virtual machine {vm.name} on host {host.name}. Application consistent sync completed for virtual machine {vm.name}. Application consistent sync completed. Application consistent sync completed for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name} ({bytes} bytes transferred)
hbr.primary.DeltaAbortedEvent Sync aborted. warning Sync aborted for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name}: {reason.@enum.hbr.primary.ReasonForDeltaAbort} Sync aborted for virtual machine {vm.name} on host {host.name}: {reason.@enum.hbr.primary.ReasonForDeltaAbort} Sync aborted for virtual machine {vm.name}: {reason.@enum.hbr.primary.ReasonForDeltaAbort} Sync aborted: {reason.@enum.hbr.primary.ReasonForDeltaAbort} Sync aborted for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}: {reason.@enum.hbr.primary.ReasonForDeltaAbort}
hbr.primary.DeltaCompletedEvent Sync completed. info Sync completed for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name}. Sync completed for virtual machine {vm.name} on host {host.name}. Sync completed for virtual machine {vm.name}. Sync completed. Sync completed for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name} ({bytes} bytes transferred).
hbr.primary.FSQuiescedDeltaCompletedEvent File system consistent sync completed. info File system consistent sync completed for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name}. File system consistent sync completed for virtual machine {vm.name} on host {host.name}. File system consistent sync completed for virtual machine {vm.name}. File system consistent sync completed. File system consistent sync completed for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name} ({bytes} bytes transferred)
hbr.primary.FailedToStartDeltaEvent Failed to start sync. error Failed to start sync for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name}: {reason.@enum.fault.ReplicationVmFault.ReasonForFault} Failed to start sync for virtual machine {vm.name} on host {host.name}: {reason.@enum.fault.ReplicationVmFault.ReasonForFault} Failed to start sync for virtual machine {vm.name}: {reason.@enum.fault.ReplicationVmFault.ReasonForFault} Failed to start sync: {reason.@enum.fault.ReplicationVmFault.ReasonForFault} Failed to start sync for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}: {reason.@enum.fault.ReplicationVmFault.ReasonForFault}
hbr.primary.FailedToStartSyncEvent Failed to start full sync. error Failed to start full sync for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name}: {reason.@enum.fault.ReplicationVmFault.ReasonForFault} Failed to start full sync for virtual machine {vm.name} on host {host.name}: {reason.@enum.fault.ReplicationVmFault.ReasonForFault} Failed to start full sync for virtual machine {vm.name}: {reason.@enum.fault.ReplicationVmFault.ReasonForFault} Failed to start full sync: {reason.@enum.fault.ReplicationVmFault.ReasonForFault} Failed to start full sync for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}: {reason.@enum.fault.ReplicationVmFault.ReasonForFault}
hbr.primary.InvalidDiskReplicationConfigurationEvent Disk replication configuration is invalid. error Replication configuration is invalid for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name}, disk {diskKey}: {reasonForFault.@enum.fault.ReplicationDiskConfigFault.ReasonForFault} Replication configuration is invalid for virtual machine {vm.name} on host {host.name} disk {diskKey}: {reasonForFault.@enum.fault.ReplicationDiskConfigFault.ReasonForFault} Replication configuration is invalid for virtual machine {vm.name} disk {diskKey}: {reasonForFault.@enum.fault.ReplicationDiskConfigFault.ReasonForFault} Replication configuration is invalid for disk {diskKey}: {reasonForFault.@enum.fault.ReplicationDiskConfigFault.ReasonForFault} Replication configuration is invalid for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}, disk {diskKey}: {reasonForFault.@enum.fault.ReplicationDiskConfigFault.ReasonForFault}
hbr.primary.InvalidVmReplicationConfigurationEvent Virtual machine replication configuration is invalid. error Replication configuration is invalid for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name}: {reasonForFault.@enum.fault.ReplicationVmConfigFault.ReasonForFault} Replication configuration is invalid for virtual machine {vm.name} on host {host.name}: {reasonForFault.@enum.fault.ReplicationVmConfigFault.ReasonForFault} Replication configuration is invalid for virtual machine {vm.name}: {reasonForFault.@enum.fault.ReplicationVmConfigFault.ReasonForFault} Replication configuration is invalid: {reasonForFault.@enum.fault.ReplicationVmConfigFault.ReasonForFault} Replication configuration is invalid for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}: {reasonForFault.@enum.fault.ReplicationVmConfigFault.ReasonForFault}
hbr.primary.NoConnectionToHbrServerEvent No connection to VR Server. warning No connection to VR Server for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name}: {reason.@enum.hbr.primary.ReasonForNoServerConnection} No connection to VR Server for virtual machine {vm.name} on host {host.name}: {reason.@enum.hbr.primary.ReasonForNoServerConnection} No connection to VR Server for virtual machine {vm.name}: {reason.@enum.hbr.primary.ReasonForNoServerConnection} No connection to VR Server: {reason.@enum.hbr.primary.ReasonForNoServerConnection} No connection to VR Server for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}: {reason.@enum.hbr.primary.ReasonForNoServerConnection}
hbr.primary.NoProgressWithHbrServerEvent VR Server error: {reason.@enum.hbr.primary.ReasonForNoServerProgress} error VR Server error for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name}: {reason.@enum.hbr.primary.ReasonForNoServerProgress} VR Server error for virtual machine {vm.name} on host {host.name}: {reason.@enum.hbr.primary.ReasonForNoServerProgress} VR Server error for virtual machine {vm.name}: {reason.@enum.hbr.primary.ReasonForNoServerProgress} VR Server error: {reason.@enum.hbr.primary.ReasonForNoServerProgress} VR Server error for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}: {reason.@enum.hbr.primary.ReasonForNoServerProgress}
hbr.primary.SyncCompletedEvent Full sync completed. info Full sync completed for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name}. Full sync completed for virtual machine {vm.name} on host {host.name}. Full sync completed for virtual machine {vm.name}. Full sync completed. Full sync completed for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name} ({bytes} bytes transferred).
hbr.primary.UnquiescedDeltaCompletedEvent Quiescing failed or the virtual machine is powered off. Unquiesced crash consistent sync completed. warning Quiescing failed or the virtual machine is powered off. Unquiesced crash consistent sync completed for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name}. Quiescing failed or the virtual machine is powered off. Unquiesced crash consistent sync completed for virtual machine {vm.name} on host {host.name}. Quiescing failed or the virtual machine is powered off. Unquiesced crash consistent sync completed for virtual machine {vm.name}. Quiescing failed or the virtual machine is powered off. Unquiesced crash consistent sync completed. Quiescing failed or the virtual machine is powered off. Unquiesced crash consistent sync completed for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name} ({bytes} bytes transferred).
hbr.primary.VmReplicationConfigurationChangedEvent Replication configuration changed. info Replication configuration changed for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} ({numDisks} disks, {rpo} minutes RPO, VR Server is {vrServerAddress}:{vrServerPort}). Replication configuration changed for virtual machine {vm.name} on host {host.name} ({numDisks} disks, {rpo} minutes RPO, VR Server is {vrServerAddress}:{vrServerPort}). Replication configuration changed for virtual machine {vm.name} ({numDisks} disks, {rpo} minutes RPO, VR Server is {vrServerAddress}:{vrServerPort}). Replication configuration changed ({numDisks} disks, {rpo} minutes RPO, VR Server is {vrServerAddress}:{vrServerPort}). Replication configuration changed for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name} ({numDisks} disks, {rpo} minutes RPO, VR Server is {vrServerAddress}:{vrServerPort}).
vim.event.LicenseDowngradedEvent License downgrade warning License downgrade License downgrade License downgrade License downgrade: {licenseKey} removes the following features: {lostFeatures}
vprob.net.connectivity.lost Lost Network Connectivity error Lost network connectivity on virtual switch {1}. Physical NIC {2} is down. Affected portgroups:{3}.
vprob.net.e1000.tso6.notsupported No IPv6 TSO support error Guest-initiated IPv6 TCP Segmentation Offload (TSO) packets ignored. Manually disable TSO inside the guest operating system in virtual machine {1}, or use a different virtual adapter.
vprob.net.migrate.bindtovmk Invalid vmknic specified in /Migrate/Vmknic warning The ESX advanced config option /Migrate/Vmknic is set to an invalid vmknic: {1}. /Migrate/Vmknic specifies a vmknic that vMotion binds to for improved performance. Please update the config option with a valid vmknic or, if you do not want vMotion to bind to a specific vmknic, remove the invalid vmknic and leave the option blank.
vprob.net.proxyswitch.port.unavailable Virtual NIC connection to switch failed warning Virtual NIC with hardware address {1} failed to connect to distributed virtual port {2} on switch {3}. There are no more ports available on the host proxy switch.
vprob.net.redundancy.degraded Network Redundancy Degraded warning Uplink redundancy degraded on virtual switch {1}. Physical NIC {2} is down. {3} uplinks still up. Affected portgroups:{4}.
vprob.net.redundancy.lost Lost Network Redundancy warning Lost uplink redundancy on virtual switch {1}. Physical NIC {2} is down. Affected portgroups:{3}.
vprob.scsi.device.thinprov.atquota Thin Provisioned Device Nearing Capacity warning Space utilization on thin-provisioned device {1} exceeded configured threshold.
vprob.storage.connectivity.lost Lost Storage Connectivity error Lost connectivity to storage device {1}. Path {2} is down. Affected datastores: {3}.
vprob.storage.redundancy.degraded Degraded Storage Path Redundancy warning Path redundancy to storage device {1} degraded. Path {2} is down. {3} remaining active paths. Affected datastores: {4}.
vprob.storage.redundancy.lost Lost Storage Path Redundancy warning Lost path redundancy to storage device {1}. Path {2} is down. Affected datastores: {3}.
vprob.vmfs.error.volume.is.locked VMFS Locked By Remote Host error Volume on device {1} is locked, possibly because some remote host encountered an error during a volume operation and could not recover.
vprob.vmfs.extent.offline Device backing an extent of a file system is offline. error An attached device {1} might be offline. The file system {2} is now in a degraded state. While the datastore is still available, parts of data that reside on the extent that went offline might be inaccessible.
vprob.vmfs.extent.online Device backing an extent of a file system is online. info Device {1} backing file system {2} came online. This extent was previously offline. All resources on this device are now available.
vprob.vmfs.heartbeat.recovered VMFS Volume Connectivity Restored info Successfully restored access to volume {1} ({2}) following connectivity issues.
vprob.vmfs.heartbeat.timedout VMFS Volume Connectivity Degraded info Lost access to volume {1} ({2}) due to connectivity issues. Recovery attempt is in progress and outcome will be reported shortly.
vprob.vmfs.heartbeat.unrecoverable VMFS Volume Connectivity Lost error Lost connectivity to volume {1} ({2}) and subsequent recovery attempts have failed.
vprob.vmfs.journal.createfailed No Space To Create VMFS Journal error No space for journal on volume {1} ({2}). Opening volume in read-only metadata mode with limited write support.
vprob.vmfs.lock.corruptondisk VMFS Lock Corruption Detected error At least one corrupt on-disk lock was detected on volume {1} ({2}). Other regions of the volume may be damaged too.
vprob.vmfs.nfs.server.disconnect Lost connection to NFS server error Lost connection to server {1} mount point {2} mounted as {3} ({4}).
vprob.vmfs.nfs.server.restored Restored connection to NFS server info Restored connection to server {1} mount point {2} mounted as {3} ({4}).
vprob.vmfs.resource.corruptondisk VMFS Resource Corruption Detected error At least one corrupt resource metadata region was detected on volume {1} ({2}). Other regions of the volume might be damaged too.
com.vmware.cl.CopyLibraryItemEvent Copied Library Item info Copied Library Item {targetLibraryItemName} to Library {targetLibraryName}({targetLibraryId}). Source Library Item {sourceLibraryItemName}({sourceLibraryItemId}), source Library {sourceLibraryName}({sourceLibraryId}). Copied Library Item {targetLibraryItemName} to Library {targetLibraryName}({targetLibraryId}). Source Library Item {sourceLibraryItemName}({sourceLibraryItemId}), source Library {sourceLibraryName}({sourceLibraryId}). Copied Library Item {targetLibraryItemName} to Library {targetLibraryName}({targetLibraryId}). Source Library Item {sourceLibraryItemName}({sourceLibraryItemId}), source Library {sourceLibraryName}({sourceLibraryId}). Copied Library Item {targetLibraryItemName} to Library {targetLibraryName}({targetLibraryId}). Source Library Item {sourceLibraryItemName}({sourceLibraryItemId}), source Library {sourceLibraryName}({sourceLibraryId}). Copied Library Item {targetLibraryItemName} to Library {targetLibraryName}({targetLibraryId}). Source Library Item {sourceLibraryItemName}({sourceLibraryItemId}), source Library {sourceLibraryName}({sourceLibraryId}).
com.vmware.cl.CopyLibraryItemFailEvent Failed to copy Library Item error Failed to copy Library Item {targetLibraryItemName}. Failed to copy Library Item {targetLibraryItemName}. Failed to copy Library Item {targetLibraryItemName}. Failed to copy Library Item {targetLibraryItemName}. Failed to copy Library Item {targetLibraryItemName}.
com.vmware.cl.CreateLibraryEvent Created Library info Created Library {libraryName} Created Library {libraryName} Created Library {libraryName} Created Library {libraryName} Created Library {libraryName}
com.vmware.cl.CreateLibraryFailEvent Failed to create Library error Failed to create Library {libraryName} Failed to create Library {libraryName} Failed to create Library {libraryName} Failed to create Library {libraryName} Failed to create Library {libraryName}
com.vmware.cl.CreateLibraryItemEvent Created Library Item info Created Library Item {libraryItemName} in Library {libraryName}({libraryId}). Created Library Item {libraryItemName} in Library {libraryName}({libraryId}). Created Library Item {libraryItemName} in Library {libraryName}({libraryId}). Created Library Item {libraryItemName} in Library {libraryName}({libraryId}). Created Library Item {libraryItemName} in Library {libraryName}({libraryId}).
com.vmware.cl.CreateLibraryItemFailEvent Failed to create Library Item error Failed to create Library Item {libraryItemName}. Failed to create Library Item {libraryItemName}. Failed to create Library Item {libraryItemName}. Failed to create Library Item {libraryItemName}. Failed to create Library Item {libraryItemName}.
com.vmware.cl.DeleteLibraryEvent Deleted Library info Deleted Library {libraryName} Deleted Library {libraryName} Deleted Library {libraryName} Deleted Library {libraryName} Deleted Library {libraryName}
com.vmware.cl.DeleteLibraryFailEvent Failed to delete Library error Failed to delete Library Failed to delete Library Failed to delete Library Failed to delete Library Failed to delete Library
com.vmware.cl.DeleteLibraryItemEvent Deleted Library Item info Deleted Library Item {libraryItemName} in Library {libraryName}({libraryId}). Deleted Library Item {libraryItemName} in Library {libraryName}({libraryId}). Deleted Library Item {libraryItemName} in Library {libraryName}({libraryId}). Deleted Library Item {libraryItemName} in Library {libraryName}({libraryId}). Deleted Library Item {libraryItemName} in Library {libraryName}({libraryId}).
com.vmware.cl.DeleteLibraryItemFailEvent Failed to delete Library Item error Failed to delete Library Item. Failed to delete Library Item. Failed to delete Library Item. Failed to delete Library Item. Failed to delete Library Item.
com.vmware.cl.UpdateLibraryEvent Updated Library info Updated Library {libraryName} Updated Library {libraryName} Updated Library {libraryName} Updated Library {libraryName} Updated Library {libraryName}
com.vmware.cl.UpdateLibraryFailEvent Failed to update Library error Failed to update Library Failed to update Library Failed to update Library Failed to update Library Failed to update Library
com.vmware.cl.UpdateLibraryItemEvent Updated Library Item info Updated Library Item {libraryItemName} in Library {libraryName}({libraryId}). Updated Library Item {libraryItemName} in Library {libraryName}({libraryId}). Updated Library Item {libraryItemName} in Library {libraryName}({libraryId}). Updated Library Item {libraryItemName} in Library {libraryName}({libraryId}). Updated Library Item {libraryItemName} in Library {libraryName}({libraryId}).
com.vmware.cl.UpdateLibraryItemFailEvent Failed to update Library Item error Failed to update Library Item. Failed to update Library Item. Failed to update Library Item. Failed to update Library Item. Failed to update Library Item.
com.vmware.rbd.activateRuleSet com.vmware.rbd.activateRuleSet info Activate Rule Set
com.vmware.rbd.fdmPackageMissing com.vmware.rbd.fdmPackageMissing warning A host in a HA cluster does not have the 'vmware-fdm' package in its image profile
com.vmware.rbd.hostProfileRuleAssocEvent com.vmware.rbd.hostProfileRuleAssocEvent warning A host profile associated with one or more active rules was deleted.
com.vmware.rbd.ignoreMachineIdentity com.vmware.rbd.ignoreMachineIdentity warning Ignoring the AutoDeploy.MachineIdentity event, since the host is already provisioned through Auto Deploy
com.vmware.rbd.pxeBootNoImageRule com.vmware.rbd.pxeBootNoImageRule info Unable to PXE boot host since it does not match any rules
com.vmware.rbd.pxeBootUnknownHost com.vmware.rbd.pxeBootUnknownHost info PXE Booting unknown host
com.vmware.rbd.pxeProfileAssoc com.vmware.rbd.pxeProfileAssoc info Attach PXE Profile
com.vmware.rbd.vmcaCertGenerationFailureEvent com.vmware.rbd.vmcaCertGenerationFailureEvent error Failed to generate host certificates using VMCA
com.vmware.vim.eam.agency.create Agency created info {agencyName} created by {ownerName}
com.vmware.vim.eam.agency.destroyed Agency destroyed info {agencyName} removed from the vSphere ESX Agent Manager
com.vmware.vim.eam.agency.goalstate Agency state changed info {agencyName} changed goal state from {oldGoalState} to {newGoalState}
com.vmware.vim.eam.agency.statusChanged Agency status changed info Agency status changed from {oldStatus} to {newStatus}
com.vmware.vim.eam.agency.updated Agency reconfigured info Configuration updated {agencyName}
com.vmware.vim.eam.agent.created Agent added to host info Agent added to host {host.name} ({agencyName})
com.vmware.vim.eam.agent.destroyed Agent removed from host info Agent removed from host {host.name} ({agencyName})
com.vmware.vim.eam.agent.destroyedNoHost Agent removed from host info Agent removed from host ({agencyName})
com.vmware.vim.eam.agent.markAgentVmAsAvailableAfterPowerOn Agent VM has been powered on and awaits a mark agent as available info Agent VM {vm.name} has been powered on. Mark agent as available to proceed agent workflow ({agencyName})
com.vmware.vim.eam.agent.markAgentVmAsAvailableAfterProvisioning Agent VM has been provisioned and awaits a mark agent as available info Agent VM {vm.name} has been provisioned. Mark agent as available to proceed agent workflow ({agencyName})
com.vmware.vim.eam.agent.statusChanged Agent status changed info Agent status changed from {oldStatus} to {newStatus}
com.vmware.vim.eam.agent.task.deleteVm Agent VM is deleted info Agent VM {vmName} is deleted on host {host.name} ({agencyName})
com.vmware.vim.eam.agent.task.deployVm Agent VM is provisioned info Agent VM {vm.name} is provisioned on host {host.name} ({agencyName})
com.vmware.vim.eam.agent.task.powerOffVm Agent VM powered off info Agent VM {vm.name} powered off, on host {host.name} ({agencyName})
com.vmware.vim.eam.agent.task.powerOnVm Agent VM powered on info Agent VM {vm.name} powered on, on host {host.name} ({agencyName})
com.vmware.vim.eam.agent.task.vibInstalled VIB installed info Agent installed VIB {vib} on host {host.name} ({agencyName})
com.vmware.vim.eam.agent.task.vibUninstalled VIB installed info Agent uninstalled VIB {vib} on host {host.name} ({agencyName})
com.vmware.vim.eam.issue.cannotAccessAgentOVF error Unable to access agent OVF package at {url} ({agencyName})
com.vmware.vim.eam.issue.cannotAccessAgentVib error Unable to access agent VIB module at {url} ({agencyName})
com.vmware.vim.eam.issue.hostInMaintenanceMode error Agent cannot complete an operation since the host {host.name} is in maintenance mode ({agencyName})
com.vmware.vim.eam.issue.hostInStandbyMode error Agent cannot complete an operation since the host {host.name} is in standby mode ({agencyName})
com.vmware.vim.eam.issue.hostPoweredOff error Agent cannot complete an operation since the host {host.name} is powered off ({agencyName})
com.vmware.vim.eam.issue.incompatibleHostVersion error Agent is not deployed due to incompatible host {host.name} ({agencyName})
com.vmware.vim.eam.issue.insufficientIpAddresses error Insufficient IP addresses in network protocol profile in agent's VM network ({agencyName})
com.vmware.vim.eam.issue.insufficientResources error Agent cannot be provisioned due to insufficient resources on host {host.name} ({agencyName})
com.vmware.vim.eam.issue.insufficientSpace error Agent on {host.name} cannot be provisioned due to insufficient space on datastore ({agencyName})
com.vmware.vim.eam.issue.missingAgentIpPool error No network protocol profile associated to agent's VM network ({agencyname})
com.vmware.vim.eam.issue.missingDvFilterSwitch error dvFilter switch is not configured on host {host.name} ({agencyname})
com.vmware.vim.eam.issue.noAgentVmDatastore error No agent datastore configuration on host {host.name} ({agencyName})
com.vmware.vim.eam.issue.noAgentVmNetwork error No agent network configuration on host {host.name} ({agencyName})
com.vmware.vim.eam.issue.noCustomAgentVmDatastore error Agent datastore(s) {customAgentVmDatastoreName} not available on host {host.name} ({agencyName})
com.vmware.vim.eam.issue.noCustomAgentVmNetwork error Agent network(s) {customAgentVmNetworkName} not available on host {host.name} ({agencyName})
com.vmware.vim.eam.issue.orphandedDvFilterSwitch error Unused dvFilter switch on host {host.name} ({agencyName})
com.vmware.vim.eam.issue.orphanedAgency error Orphaned agency found. ({agencyName})
com.vmware.vim.eam.issue.ovfInvalidFormat error OVF used to provision agent on host {host.name} has invalid format ({agencyName})
com.vmware.vim.eam.issue.ovfInvalidProperty error OVF environment used to provision agent on host {host.name} has one or more invalid properties ({agencyName})
com.vmware.vim.eam.issue.resolved info Issue {type} resolved (key {key})
com.vmware.vim.eam.issue.vibCannotPutHostInMaintenanceMode error Cannot put host into maintenance mode ({agencyName})
com.vmware.vim.eam.issue.vibInvalidFormat error Invalid format for VIB module at {url} ({agencyName})
com.vmware.vim.eam.issue.vibNotInstalled error VIB module for agent is not installed on host {host.name} ({agencyName})
com.vmware.vim.eam.issue.vibRequiresHostInMaintenanceMode error Host must be put into maintenance mode to complete agent VIB installation ({agencyName})
com.vmware.vim.eam.issue.vibRequiresHostReboot error Host {host.name} must be reboot to complete agent VIB installation ({agencyName})
com.vmware.vim.eam.issue.vibRequiresManualInstallation error VIB {vib} requires manual installation on host {host.name} ({agencyName})
com.vmware.vim.eam.issue.vibRequiresManualUninstallation error VIB {vib} requires manual uninstallation on host {host.name} ({agencyName})
com.vmware.vim.eam.issue.vmCorrupted error Agent VM {vm.name} on host {host.name} is corrupted ({agencyName})
com.vmware.vim.eam.issue.vmDeployed error Agent VM {vm.name} is provisioned on host {host.name} when it should be removed ({agencyName})
com.vmware.vim.eam.issue.vmMarkedAsTemplate error Agent VM {vm.name} on host {host.name} is marked as template ({agencyName})
com.vmware.vim.eam.issue.vmNotDeployed error Agent VM is missing on host {host.name} ({agencyName})
com.vmware.vim.eam.issue.vmOrphaned error Orphaned agent VM {vm.name} on host {host.name} detected ({agencyName})
com.vmware.vim.eam.issue.vmPoweredOff error Agent VM {vm.name} on host {host.name} is expected to be powered on ({agencyName})
com.vmware.vim.eam.issue.vmPoweredOn error Agent VM {vm.name} on host {host.name} is expected to be powered off ({agencyName})
com.vmware.vim.eam.issue.vmSuspended error Agent VM {vm.name} on host {host.name} is expected to be powered on but is suspended ({agencyName})
com.vmware.vim.eam.issue.vmWrongFolder error Agent VM {vm.name} on host {host.name} is in the wrong VM folder ({agencyName})
com.vmware.vim.eam.issue.vmWrongResourcePool error Agent VM {vm.name} on host {host.name} is in the resource pool ({agencyName})
com.vmware.vim.eam.login.succeeded Successful login to vSphere ESX Agent Manager info Successful login by {user} into vSphere ESX Agent Manager
com.vmware.vim.eam.logout User logged out of vSphere ESX Agent Manager info User {user} logged out of vSphere ESX Agent Manager by logging out of the vCenter server
com.vmware.vim.eam.task.setupDvFilter Setup dvFilter switch info DvFilter switch '{switchName}' is setup on host {host.name}
com.vmware.vim.eam.task.tearDownDvFilter Tear down dvFilter switch info DvFilter switch '{switchName}' is teared down on host {host.name}
com.vmware.vim.eam.unauthorized.access Unauthorized access in vSphere ESX Agent Manager warning Unauthorized access by {user} in vSphere ESX Agent Manager
com.vmware.vim.eam.vum.failedtouploadvib error Failed to upload {vibUrl} to VMware Update Manager ({agencyName})
ExitedStandbyModeEvent Exited standby mode info Exited standby mode The host {host.name} is no longer in standby mode
ExitingStandbyModeEvent Exiting standby mode info Exiting standby mode The host {host.name} is exiting standby mode
ExitMaintenanceModeEvent Exit maintenance mode info Host {host.name} has exited maintenance mode Host {host.name} has exited maintenance mode Exited maintenance mode Host {host.name} in {datacenter.name} has exited maintenance mode
ExitStandbyModeFailedEvent Cannot exit standby mode error Could not exit standby mode The host {host.name} could not exit standby mode
ad.event.ImportCertEvent Import certificate success info Import certificate succeeded. Import certificate succeeded. Import certificate succeeded. Import certificate succeeded. Import certificate succeeded.
ad.event.ImportCertFailedEvent Import certificate failure error Import certificate failed. Import certificate failed. Import certificate failed. Import certificate failed. Import certificate failed.
ad.event.JoinDomainEvent Join domain success info Join domain succeeded. Join domain succeeded. Join domain succeeded. Join domain succeeded. Join domain succeeded.
ad.event.JoinDomainFailedEvent Join domain failure error Join domain failed. Join domain failed. Join domain failed. Join domain failed. Join domain failed.
ad.event.LeaveDomainEvent Leave domain success info Leave domain succeeded. Leave domain succeeded. Leave domain succeeded. Leave domain succeeded. Leave domain succeeded.
ad.event.LeaveDomainFailedEvent Leave domain failure error Leave domain failed. Leave domain failed. Leave domain failed. Leave domain failed. Leave domain failed.
com.vmware.license.HostLicenseExpiredEvent Host license or evaluation period has expired warning Expired host license or evaluation period.
com.vmware.license.HostSubscriptionLicenseExpiredEvent Host time-limited license has expired warning Expired host time-limited license.
com.vmware.license.VcLicenseExpiredEvent vCenter Server license or evaluation period has expired warning Expired vCenter Server license or evaluation period.
com.vmware.license.VcSubscriptionLicenseExpiredEvent vCenter Server time-limited license has expired warning Expired vCenter Server time-limited license.
com.vmware.license.vsan.HostSsdOverUsageEvent Host flash capacity exceeds the licensed limit for Virtual SAN warning The capacity of the flash disks on the host exceeds the limit of the Virtual SAN license.
com.vmware.license.vsan.LicenseExpiryEvent Virtual SAN license or evaluation period has expired warning Expired Virtual SAN license or evaluation period.
com.vmware.license.vsan.SubscriptionLicenseExpiredEvent Virtual SAN time-limited license has expired warning Expired Virtual SAN time-limited license.
com.vmware.vc.HA.AllHostAddrsPingable vSphere HA agent can reach all cluster management addresses info The vSphere HA agent on the host {host.name} in cluster {computeResource.name} can reach all the cluster management addresses The vSphere HA agent on the host {host.name} can reach all the cluster management addresses The vSphere HA agent on this host can reach all the cluster management addresses The vSphere HA agent on the host {host.name} in cluster {computeResource.name} in {datacenter.name} can reach all the cluster management addresses
com.vmware.vc.HA.AllIsoAddrsPingable vSphere HA agent can reach all isolation addresses info All vSphere HA isolation addresses are reachable by host {host.name} in cluster {computeResource.name} All vSphere HA isolation addresses are reachable by this host All vSphere HA isolation addresses are reachable by host All vSphere HA isolation addresses are reachable by host {host.name} in cluster {computeResource.name} in {datacenter.name}
com.vmware.vc.HA.AnsweredVmLockLostQuestionEvent vSphere HA answered a lock-lost question on a virtual machine warning vSphere HA answered the lock-lost question on virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} vSphere HA answered the lock-lost question on virtual machine {vm.name} on host {host.name} vSphere HA answered the lock-lost question on virtual machine {vm.name} vSphere HA answered the lock-lost question on this virtual machine vSphere HA answered the lock-lost question on virtual machine {vm.name} on host {host.name} in cluster {computeResource.name}
com.vmware.vc.HA.AnsweredVmTerminatePDLEvent vSphere HA answered a question from the host about terminating a virtual machine warning vSphere HA answered a question from host {host.name} in cluster {computeResource.name} about terminating virtual machine {vm.name} vSphere HA answered a question from host {host.name} about terminating virtual machine {vm.name} vSphere HA answered a question from the host about terminating virtual machine {vm.name} vSphere HA answered a question from the host about terminating this virtual machine vSphere HA answered a question from host {host.name} in cluster {computeResource.name} about terminating virtual machine {vm.name}
com.vmware.vc.HA.AutoStartDisabled vSphere HA disabled the automatic VM Startup/Shutdown feature info vSphere HA disabled the automatic Virtual Machine Startup/Shutdown feature on host {host.name} in cluster {computeResource.name}. Automatic VM restarts will interfere with HA when reacting to a host failure. vSphere HA disabled the automatic Virtual Machine Startup/Shutdown feature on the host {host.name}. Automatic VM restarts will interfere with HA when reacting to a host failure. vSphere HA disabled the automatic Virtual Machine Startup/Shutdown feature. Automatic VM restarts will interfere with HA when reacting to a host failure. vSphere HA disabled the automatic Virtual Machine Startup/Shutdown feature on host {host.name} in cluster {computeResource.name} in {datacenter.name}. Automatic VM restarts will interfere with HA when reacting to a host failure.
com.vmware.vc.HA.CannotResetVmWithInaccessibleDatastore vSphere HA did not reset a VM which had files on inaccessible datastore(s) warning vSphere HA did not reset VM {vm.name} on host {host.name} in cluster {computeResource.name} because the VM had files on inaccessible datastore(s) vSphere HA did not reset VM {vm.name} on host {host.name} because the VM had files on inaccessible datastore(s) vSphere HA did not reset VM {vm.name} on this host because the VM had files on inaccessible datastore(s) vSphere HA did not reset this VM because the VM had file(s) on inaccessible datastore(s) vSphere HA did not reset VM {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name} because the VM had files on inaccessible datastore(s)
com.vmware.vc.HA.ClusterContainsIncompatibleHosts vSphere HA cluster contains incompatible hosts. warning vSphere HA Cluster {computeResource.name} contains ESX/ESXi 3.5 hosts and more recent host versions, which isn't fully supported. vSphere HA Cluster contains ESX/ESXi 3.5 hosts and more recent host versions, which isn't fully supported. vSphere HA Cluster {computeResource.name} in {datacenter.name} contains ESX/ESXi 3.5 hosts and more recent host versions, which isn't fully supported.
com.vmware.vc.HA.ClusterFailoverActionCompletedEvent vSphere HA completed a failover action info vSphere HA completed a virtual machine failover action in cluster {computeResource.name} vSphere HA completed a virtual machine failover action vSphere HA completed a virtual machine failover action in cluster {computeResource.name} in datacenter {datacenter.name}
com.vmware.vc.HA.ConnectedToMaster Host connected to a vSphere HA master info vSphere HA agent on host {host.name} connected to the vSphere HA master on host {masterHostName} in cluster {computeResource.name} vSphere HA agent on host {host.name} connected to the vSphere HA master on host {masterHostName} vSphere HA agent on host {host.name} connected to the vSphere HA master on host {masterHostName} vSphere HA agent on host {host.name} connected to the vSphere HA master on host {masterHostName} in cluster {computeResource.name} in datacenter {datacenter.name}
com.vmware.vc.HA.CreateConfigVvolFailedEvent vSphere HA failed to create a configuration vVol for this datastore and so will not be able to protect virtual machines on the datastore until the problem is resolved. Error: {fault} error vSphere HA failed to create a configuration vVol for this datastore and so will not be able to protect virtual machines on the datastore until the problem is resolved. Error: {fault} vSphere HA failed to create a configuration vVol for this datastore and so will not be able to protect virtual machines on the datastore until the problem is resolved. Error: {fault} vSphere HA failed to create a configuration vVol for this datastore and so will not be able to protect virtual machines on the datastore until the problem is resolved. Error: {fault} vSphere HA failed to create a configuration vVol for this datastore and so will not be able to protect virtual machines on the datastore until the problem is resolved. Error: {fault}
com.vmware.vc.HA.CreateConfigVvolSucceededEvent vSphere HA successfully created a configuration vVol after the previous failure info vSphere HA successfully created a configuration vVol after the previous failure vSphere HA successfully created a configuration vVol after the previous failure vSphere HA successfully created a configuration vVol after the previous failure vSphere HA successfully created a configuration vVol after the previous failure
com.vmware.vc.HA.DasAgentRunningEvent vSphere HA agent is running info vSphere HA agent on host {host.name} in cluster {computeResource.name} is running vSphere HA agent on host {host.name} is running vSphere HA agent is running vSphere HA agent on host {host.name} in cluster {computeResource.name} in datacenter {datacenter.name} is running
com.vmware.vc.HA.DasFailoverHostFailedEvent vSphere HA detected a failed failover host error vSphere HA detected a possible failure of failover host {host.name} in cluster {computeResource.name} vSphere HA detected a possible failure of failover host {host.name} vSphere HA detected a possible failure of this failover host vSphere HA detected a possible failure of failover host {host.name} in cluster {computeResource.name} in {datacenter.name}
com.vmware.vc.HA.DasFailoverHostIsolatedEvent vSphere HA detected a network-isolated failover host error vSphere HA detected that failover host {host.name} is network isolated from cluster {computeResource.name} vSphere HA detected that failover host {host.name} is network isolated from the cluster vSphere HA detected that this failover host is network isolated from the cluster Host {host.name} has been isolated from cluster {computeResource.name} in {datacenter.name}
com.vmware.vc.HA.DasFailoverHostPartitionedEvent vSphere HA detected a network-partitioned failover host warning vSphere HA detected that failover host {host.name} in {computeResource.name} is in a different network partition than the master to which vCenter Server is connected vSphere HA detected that failover host {host.name} is in a different network partition than the master to which vCenter Server is connected vSphere HA detected that this failover host is in a different network partition than the master Failover Host {host.name} in {computeResource.name} in {datacenter.name} is in a different network partition than the master
com.vmware.vc.HA.DasFailoverHostUnreachableEvent vSphere HA agent on a failover host is unreachable error The vSphere HA agent on the failover host {host.name} in {computeResource.name} is not reachable but host responds to ICMP pings The vSphere HA agent on the failover host {host.name} is not reachable but host responds to ICMP pings The vSphere HA agent on this failover host is not reachable but host responds to ICMP pings The vSphere HA agent on the failover host {host.name} in cluster {computeResource.name} in {datacenter.name} is not reachable but host responds to ICMP pings
com.vmware.vc.HA.DasHostFailedEvent vSphere HA detected a host failure error vSphere HA detected a possible host failure of host {host.name} in cluster {computeResource.name} vSphere HA detected a possible host failure of host {host.name} vSphere HA detected a possible host failure of this host vSphere HA detected a possible host failure of host {host.name} in cluster {computeResource.name} in datacenter {datacenter.name}
com.vmware.vc.HA.DasHostIsolatedEvent vSphere HA detected a network isolated host error vSphere HA detected that host {host.name} is network isolated from cluster {computeResource.name} vSphere HA detected that host {host.name} is network isolated from the cluster vSphere HA detected that this host is network isolated from the cluster vSphere HA detected that host {host.name} is isolated from cluster {computeResource.name} in {datacenter.name}
com.vmware.vc.HA.DasHostMonitoringDisabledEvent vSphere HA host monitoring is disabled warning vSphere HA host monitoring is disabled. No virtual machine failover will occur until Host Monitoring is re-enabled for cluster {computeResource.name} vSphere HA host monitoring is disabled. No virtual machine failover will occur until Host Monitoring is re-enabled vSphere HA host monitoring is disabled. No virtual machine failover will occur until Host Monitoring is re-enabled for cluster {computeResource.name} in {datacenter.name}
com.vmware.vc.HA.FailedRestartAfterIsolationEvent vSphere HA failed to restart a network isolated virtual machine error vSphere HA was unable to restart virtual machine {vm.name} in cluster {computeResource.name} after it was powered off in response to a network isolation event vSphere HA was unable to restart virtual machine {vm.name} after it was powered off in response to a network isolation event vSphere HA was unable to restart virtual machine {vm.name} after it was powered off in response to a network isolation event vSphere HA was unable to restart this virtual machine after it was powered off in response to a network isolation event vSphere HA was unable to restart virtual machine {vm.name} in cluster {computeResource.name} in datacenter {datacenter.name} after it was powered off in response to a network isolation event. The virtual machine should be manually powered back on.
com.vmware.vc.HA.HostDasAgentHealthyEvent vSphere HA agent is healthy info vSphere HA agent on host {host.name} in cluster {computeResource.name} is healthy vSphere HA agent on host {host.name} is healthy vSphere HA agent is healthy vSphere HA agent on host {host.name} in cluster {computeResource.name} in datacenter {datacenter.name} is healthy
com.vmware.vc.HA.HostDoesNotSupportVsan Unsupported vSphere HA and vCloud Distributed Storage configuration error vSphere HA cannot be configured on host {host.name} in cluster {computeResource.name} because vCloud Distributed Storage is enabled but the host does not support that feature vSphere HA cannot be configured on host {host.name} because vCloud Distributed Storage is enabled but the host does not support that feature vSphere HA cannot be configured because vCloud Distributed Storage is enabled but the host does not support that feature vSphere HA cannot be configured on host {host.name} in cluster {computeResource.name} in {datacenter.name} because vCloud Distributed Storage is enabled but the host does not support that feature vSphere HA cannot be configured on host {host.name} in cluster {computeResource.name} in {datacenter.name} because vCloud Distributed Storage is enabled but the host does not support that feature
com.vmware.vc.HA.HostHasNoIsolationAddrsDefined Host has no vSphere HA isolation addresses error Host {host.name} in cluster {computeResource.name} has no isolation addresses defined as required by vSphere HA Host {host.name} has no isolation addresses defined as required by vSphere HA This host has no isolation addresses defined as required by vSphere HA Host {host.name} in cluster {computeResource.name} in {datacenter.name} has no isolation addresses defined as required by vSphere HA.
com.vmware.vc.HA.HostHasNoMountedDatastores vSphere HA cannot be configured on this host because there are no mounted datastores. error vSphere HA cannot be configured on {host.name} in cluster {computeResource.name} because there are no mounted datastores. vSphere HA cannot be configured on {host.name} because there are no mounted datastores. vSphere HA cannot be configured on this host because there are no mounted datastores. vSphere HA cannot be configured on {host.name} in cluster {computeResource.name} in datacenter {datacenter.name} because there are no mounted datastores. vSphere HA cannot be configured on {host.name} in cluster {computeResource.name} in datacenter {datacenter.name} because there are no mounted datastores.
com.vmware.vc.HA.HostHasNoSslThumbprint vSphere HA requires a SSL Thumbprint for host error vSphere HA cannot be configured on host {host.name} in cluster {computeResource.name} because its SSL thumbprint has not been verified. Check that vCenter Server is configured to verify SSL thumbprints and that the thumbprint for {host.name} has been verified. vSphere HA cannot be configured on {host.name} because its SSL thumbprint has not been verified. Check that vCenter Server is configured to verify SSL thumbprints and that the thumbprint for {host.name} has been verified. vSphere HA cannot be configured on this host because its SSL thumbprint has not been verified. Check that vCenter Server is configured to verify SSL thumbprints and that the thumbprint for this host has been verified. vSphere HA cannot be configured on host {host.name} in cluster {computeResource.name} in datacenter {datacenter.name} because its SSL thumbprint has not been verified. Check that vCenter Server is configured to verify SSL thumbprints and that the thumbprint for {host.name} has been verified.
com.vmware.vc.HA.HostIncompatibleWithHA Host is incompatible with vSphere HA error The product version of host {host.name} in cluster {computeResource.name} is incompatible with vSphere HA. The product version of host {host.name} is incompatible with vSphere HA. The product version of this host is incompatible with vSphere HA. The product version of host {host.name} in cluster {computeResource.name} in {datacenter.name} is incompatible with vSphere HA.
com.vmware.vc.HA.HostPartitionedFromMasterEvent vSphere HA detected a network-partitioned host warning vSphere HA detected that host {host.name} is in a different network partition than the master to which vCenter Server is connected in {computeResource.name} vSphere HA detected that host {host.name} is in a different network partition than the master to which vCenter Server is connected vSphere HA detected that this host is in a different network partition than the master to which vCenter Server is connected vSphere HA detected that host {host.name} is in a different network partition than the master {computeResource.name} in {datacenter.name}
com.vmware.vc.HA.HostUnconfigureError vSphere HA agent unconfigure failed on host warning There was an error unconfiguring the vSphere HA agent on host {host.name} in cluster {computeResource.name}. To solve this problem, reconnect the host to vCenter Server. There was an error unconfiguring the vSphere HA agent on host {host.name}. To solve this problem, reconnect the host to vCenter Server. There was an error unconfiguring the vSphere HA agent on this host. To solve this problem, reconnect the host to vCenter Server. There was an error unconfiguring the vSphere HA agent on host {host.name} in cluster {computeResource.name} in {datacenter.name}. To solve this problem, reconnect the host to vCenter Server.
com.vmware.vc.HA.VMIsHADisabledIsolationEvent vSphere HA did not perform an isolation response for vm because its VM restart priority is Disabled info vSphere HA did not perform an isolation response for {vm.name} in cluster {computeResource.name} because its VM restart priorirty is Disabled vSphere HA did not perform an isolation response for {vm.name} because its VM restart priority is Disabled vSphere HA did not perform an isolation response for {vm.name} because its VM restart priority is Disabled" vSphere HA did not perform an isolation response because its VM restart priority is Disabled" vSphere HA did not perform an isolation response for {vm.name} in cluster {computeResource.name} in {datacenter.name} because its VM restart priority is Disabled
com.vmware.vc.HA.VMIsHADisabledRestartEvent vSphere HA did not attempt to restart vm because its VM restart priority is Disabled info vSphere HA did not attempt to restart {vm.name} in cluster {computeResource.name} because its VM restart priority is Disabled vSphere HA did not attempt to restart {vm.name} because its VM restart priority is Disabled vSphere HA did not attempt to restart {vm.name} because its VM restart priority is Disabled" vSphere HA did not attempt to restart vm because its VM restart priority is Disabled" vSphere HA did not attempt to restart {vm.name} in cluster {computeResource.name} in {datacenter.name} because its VM restart priority is Disabled
com.vmware.vc.HA.VcCannotFindMasterEvent vCenter Server is unable to find a master vSphere HA agent warning vCenter Server is unable to find a master vSphere HA agent in cluster {computeResource.name} vCenter Server is unable to find a master vSphere HA agent vCenter Server is unable to find a master vSphere HA agent in cluster {computeResource.name} in {datacenter.name}
com.vmware.vc.HA.VmDasResetAbortedEvent vSphere HA was unable to reset a VM after it exhausted the retries error vSphere HA was unable to reset VM {vm.name} on host {host.name} in cluster {computeResource.name} after {retryTimes} retries vSphere HA was unable to reset VM {vm.name} on host {host.name} after {retryTimes} retries vSphere HA was unable to reset VM {vm.name} on this host after {retryTimes} retries vSphere HA was unable to reset this VM after {retryTimes} retries vSphere HA was unable to reset VM {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name} after {retryTimes} retries
com.vmware.vc.HA.VmNotProtectedEvent Virtual machine failed to become vSphere HA Protected error Virtual machine {vm.name} in cluster {computeResource.name} failed to become vSphere HA Protected and HA may not attempt to restart it after a failure. Virtual machine {vm.name} failed to become vSphere HA Protected and HA may not attempt to restart it after a failure. Virtual machine {vm.name} failed to become vSphere HA Protected and HA may not attempt to restart it after a failure. This virtual machine failed to become vSphere HA Protected and HA may not attempt to restart it after a failure. Virtual machine {vm.name} in cluster {computeResource.name} in {datacenter.name} failed to become vSphere HA Protected and HA may not attempt to restart it after a failure.
com.vmware.vc.HA.VmProtectedEvent Virtual machine is vSphere HA protected info Virtual machine {vm.name} in cluster {computeResource.name} is vSphere HA Protected and HA will attempt to restart it after a failure. Virtual machine {vm.name} is vSphere HA Protected and HA will attempt to restart it after a failure. Virtual machine {vm.name} is vSphere HA Protected and HA will attempt to restart it after a failure. This virtual machine is vSphere HA Protected and HA will attempt to restart it after a failure. Virtual machine {vm.name} in cluster {computeResource.name} in {datacenter.name} is vSphere HA Protected and HA will attempt to restart it after a failure.
com.vmware.vc.HA.VmUnprotectedEvent Virtual machine is not vSphere HA Protected info Virtual machine {vm.name} in cluster {computeResource.name} is not vSphere HA Protected. Virtual machine {vm.name} is not vSphere HA Protected. Virtual machine {vm.name} is not vSphere HA Protected. This virtual machine is not vSphere HA Protected. Virtual machine {vm.name} in cluster {computeResource.name} in {datacenter.name} is not vSphere HA Protected.
com.vmware.vc.HA.VmUnprotectedOnDiskSpaceFull vSphere HA has unprotected out-of-disk-space VM info vSphere HA has unprotected virtual machine {vm.name} in cluster {computeResource.name} because it ran out of disk space vSphere HA has unprotected virtual machine {vm.name} because it ran out of disk space vSphere HA has unprotected virtual machine {vm.name} because it ran out of disk space vSphere HA has unprotected this virtual machine because it ran out of disk space vSphere HA has unprotected virtual machine {vm.name} in cluster {computeResource.name} in datacenter {datacenter.name} because it ran out of disk space
com.vmware.vc.HA.VmcpNotTerminateVmWithInaccessibleDatastore vSphere HA did not terminate a VM affected by an inaccessible datastore: {reason.@enum.com.vmware.vc.HA.VmcpNotTerminateVmWithInaccessibleDatastore} warning vSphere HA did not terminate VM {vm.name} affected by an inaccessible datastore on host {host.name} in cluster {computeResource.name}: {reason.@enum.com.vmware.vc.HA.VmcpNotTerminateVmWithInaccessibleDatastore} vSphere HA did not terminate VM {vm.name} affected by an inaccessible datastore on host {host.name}: {reason.@enum.com.vmware.vc.HA.VmcpNotTerminateVmWithInaccessibleDatastore} vSphere HA did not terminate VM {vm.name} affected by an inaccessible datastore: {reason.@enum.com.vmware.vc.HA.VmcpNotTerminateVmWithInaccessibleDatastore} vSphere HA did not terminate this VM affected by an inaccessible datastore: {reason.@enum.com.vmware.vc.HA.VmcpNotTerminateVmWithInaccessibleDatastore} vSphere HA did not terminate VM {vm.name} affected by an inaccessible datastore on host {host.name} in cluster {computeResource.name} in {datacenter.name}: {reason.@enum.com.vmware.vc.HA.VmcpNotTerminateVmWithInaccessibleDatastore}
com.vmware.vc.HA.VmcpStorageFailureCleared Datastore {ds.name} mounted on this host was inaccessible. vSphere HA detected that the condition was cleared and the datastore is now accessible info Datastore {ds.name} mounted on host {host.name} in cluster {computeResource.name} was inaccessible. vSphere HA detected that the condition was cleared and the datastore is now accessible Datastore {ds.name} mounted on host {host.name} was inaccessible. vSphere HA detected that the condition was cleared and the datastore is now accessible Datastore {ds.name} mounted on this host was inaccessible. vSphere HA detected that the condition was cleared and the datastore is now accessible Datastore {ds.name} mounted on host {host.name} was inaccessible. The condition was cleared and the datastore is now accessible
com.vmware.vc.HA.VmcpStorageFailureDetectedForVm vSphere HA detected that a datastore was inaccessible. This affected the VM with files on the datastore warning vSphere HA detected that a datastore mounted on host {host.name} in cluster {computeResource.name} was inaccessible due to {failureType.@enum.com.vmware.vc.HA.VmcpStorageFailureDetectedForVm}. This affected VM {vm.name} with files on the datastore vSphere HA detected that a datastore mounted on host {host.name} was inaccessible due to {failureType.@enum.com.vmware.vc.HA.VmcpStorageFailureDetectedForVm}. This affected VM {vm.name} with files on the datastore vSphere HA detected that a datastore mounted on this host was inaccessible due to {failureType.@enum.com.vmware.vc.HA.VmcpStorageFailureDetectedForVm}. This affected VM {vm.name} with files on the datastore vSphere HA detected that a datastore was inaccessible due to {failureType.@enum.com.vmware.vc.HA.VmcpStorageFailureDetectedForVm}. This affected the VM with files on the datastore vSphere HA detected that a datastore mounted on host {host.name} in cluster {computeResource.name} in {datacenter.name} was inaccessible due to {failureType.@enum.com.vmware.vc.HA.VmcpStorageFailureDetectedForVm}. This affected VM {vm.name} with files on the datastore
com.vmware.vc.HA.VmcpTerminateVmAborted vSphere HA was unable to terminate VM affected by an inaccessible datastore after it exhausted the retries error vSphere HA was unable to terminate VM {vm.name} affected by an inaccessible datastore on host {host.name} in cluster {computeResource.name} after {retryTimes} retries vSphere HA was unable to terminate VM {vm.name} affected by an inaccessible datastore on host {host.name} after {retryTimes} retries vSphere HA was unable to terminate VM {vm.name} affected by an inaccessible datastore on this host after {retryTimes} retries vSphere HA was unable to terminate this VM affected by an inaccessible datastore after {retryTimes} retries vSphere HA was unable to terminate VM {vm.name} affected by an inaccessible datastore on host {host.name} in cluster {computeResource.name} in {datacenter.name} after {retryTimes} retries
com.vmware.vc.HA.VmcpTerminatingVm vSphere HA attempted to terminate a VM affected by an inaccessible datastore warning vSphere HA attempted to terminate VM {vm.name} on host{host.name} in cluster {computeResource.name} because the VM was affected by an inaccessible datastore vSphere HA attempted to terminate VM {vm.name} on host{host.name} because the VM was affected by an inaccessible datastore vSphere HA attempted to terminate VM {vm.name} on this host because the VM was affected by an inaccessible datastore vSphere HA attempted to terminate this VM because the VM was affected by an inaccessible datastore vSphere HA attempted to terminate VM {vm.name} on host{host.name} in cluster {computeResource.name} in {datacenter.name} because the VM was affected by an inaccessible datastore
com.vmware.vc.VmDiskConsolidatedEvent Virtual machine disks consolidation succeeded. info Virtual machine {vm.name} disks consolidatation succeeded on {host.name} in cluster {computeResource.name}. Virtual machine {vm.name} disks consolidation succeeded on {host.name}. Virtual machine {vm.name} disks consolidation succeeded. Virtual machine disks consolidation succeeded. Virtual machine {vm.name} disks consolidated successfully on {host.name} in cluster {computeResource.name} in {datacenter.name}.
com.vmware.vc.VmDiskConsolidationNeeded Virtual machine disks consolidation needed. warning Virtual machine {vm.name} disks consolidatation is needed on {host.name} in cluster {computeResource.name}. Virtual machine {vm.name} disks consolidation is needed on {host.name}. Virtual machine {vm.name} disks consolidation is needed. Virtual machine disks consolidation is needed. Virtual machine {vm.name} disks consolidation is needed on {host.name} in cluster {computeResource.name} in {datacenter.name}.
com.vmware.vc.VmDiskConsolidationNoLongerNeeded Virtual machine disks consolidation no longer needed. info Virtual machine {vm.name} disks consolidatation is no longer needed on {host.name} in cluster {computeResource.name}. Virtual machine {vm.name} disks consolidation is no longer needed on {host.name}. Virtual machine {vm.name} disks consolidation is no longer needed. Virtual machine disks consolidation is no longer needed. Virtual machine {vm.name} disks consolidation is no longer needed on {host.name} in cluster {computeResource.name} in {datacenter.name}.
com.vmware.vc.VmDiskFailedToConsolidateEvent Virtual machine disks consolidation failed. warning Virtual machine {vm.name} disks consolidation failed on {host.name} in cluster {computeResource.name}. Virtual machine {vm.name} disks consolidation failed on {host.name}. Virtual machine {vm.name} disks consolidation failed. Virtual machine disks consolidation failed. Virtual machine {vm.name} disks consolidation failed on {host.name} in cluster {computeResource.name} in {datacenter.name}.
com.vmware.vc.certmgr.HostCertManagementModeChangedEvent Host Certificate Management Mode changed info Host Certificate Management Mode changed from {previousMode} to {presentMode}
com.vmware.vc.certmgr.HostCertMetadataChangedEvent Host Certificate Management Metadata changed info Host Certificate Management Metadata changed
com.vmware.vc.dvs.LacpConfigInconsistentEvent Link Aggregation Control Protocol configuration is inconsistent info Single Link Aggregation Control Group is enabled on Uplink Port Groups while enhanced LACP support is enabled. Single Link Aggregation Control Group is enabled on Uplink Port Groups while enhanced LACP support is enabled.
com.vmware.vc.ft.VmAffectedByDasDisabledEvent Fault Tolerance VM restart disabled warning vSphere HA has been disabled in cluster {computeResource.name}. vSphere HA will not restart VM {vm.name} or its Secondary VM after a failure. vSphere HA has been disabled. vSphere HA will not restart VM {vm.name} or its Secondary VM after a failure. vSphere HA has been disabled. vSphere HA will not restart VM {vm.name} or its Secondary VM after a failure. vSphere HA has been disabled. vSphere HA will not restart this VM or its Secondary VM after a failure. vSphere HA has been disabled in cluster {computeResource.name} of datacenter {datacenter.name}. vSphere HA will not restart VM {vm.name} or its Secondary VM after a failure.
com.vmware.vc.ha.VmRestartedByHAEvent vSphere HA restarted a virtual machine warning vSphere HA restarted virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} vSphere HA restarted virtual machine {vm.name} on host {host.name} vSphere HA restarted virtual machine {vm.name} vSphere HA restarted this virtual machine vSphere HA restarted virtual machine {vm.name} on host {host.name} in cluster {computeResource.name}
com.vmware.vc.host.AutoStartReconfigureFailedEvent Autostart rules reconfigure failed error Reconfiguring autostart rules for virtual machines on host {host.name} failed Reconfiguring autostart rules for virtual machines on host {host.name} failed Reconfiguring autostart rules for virtual machines on this host failed Reconfiguring autostart rules for virtual machines on {host.name} in datacenter {datacenter.name} failed
com.vmware.vc.host.clear.vFlashResource.inaccessible Host's virtual flash resource is accessible. info Host's virtual flash resource is restored to be accessible. Host's virtual flash resource is restored to be accessible. Host's virtual flash resource is restored to be accessible. Host's virtual flash resource is restored to be accessible.
com.vmware.vc.host.problem.DeprecatedVMFSVolumeFound Deprecated VMFS volume(s) found on the host. Please consider upgrading volume(s) to the latest version. warning Deprecated VMFS volume(s) found on the host. Please consider upgrading volume(s) to the latest version. Deprecated VMFS volume(s) found on the host. Please consider upgrading volume(s) to the latest version. Deprecated VMFS volume(s) found on the host. Please consider upgrading volume(s) to the latest version. Deprecated VMFS volume(s) found on the host. Please consider upgrading volume(s) to the latest version.
com.vmware.vc.host.problem.vFlashResource.inaccessible Host's virtual flash resource is inaccessible. warning Host's virtual flash resource is inaccessible. Host's virtual flash resource is inaccessible. Host's virtual flash resource is inaccessible. Host's virtual flash resource is inaccessible.
com.vmware.vc.host.vFlash.VFlashResourceCapacityExtendedEvent Virtual flash resource capacity is extended info Virtual flash resource capacity is extended Virtual flash resource capacity is extended Virtual flash resource capacity is extended Virtual flash resource capacity is extended
com.vmware.vc.host.vFlash.VFlashResourceConfiguredEvent Virtual flash resource is configured on the host info Virtual flash resource is configured on the host Virtual flash resource is configured on the host Virtual flash resource is configured on the host Virtual flash resource is configured on the host
com.vmware.vc.host.vFlash.VFlashResourceRemovedEvent Virtual flash resource is removed from the host info Virtual flash resource is removed from the host Virtual flash resource is removed from the host Virtual flash resource is removed from the host Virtual flash resource is removed from the host
com.vmware.vc.host.vFlash.modulesLoadedEvent Virtual flash modules are loaded or reloaded on the host info Virtual flash modules are loaded or reloaded on the host Virtual flash modules are loaded or reloaded on the host Virtual flash modules are loaded or reloaded on the host Virtual flash modules are loaded or reloaded on the host
com.vmware.vc.iofilter.FilterInstallationFailedEvent vSphere APIs for I/O Filters (VAIO) installation of filters has failed error vSphere APIs for I/O Filters (VAIO) installation of filters on cluster {computeResource.name} in datacenter {datacenter.name} has failed vSphere APIs for I/O Filters (VAIO) installation of filters on cluster {computeResource.name} has failed vSphere APIs for I/O Filters (VAIO) installation of filters on cluster {computeResource.name} in datacenter {datacenter.name} has failed
com.vmware.vc.iofilter.FilterInstallationSuccessEvent vSphere APIs for I/O Filters (VAIO) installation of filters is successful info vSphere APIs for I/O Filters (VAIO) installation of filters on cluster {computeResource.name} in datacenter {datacenter.name} is successful vSphere APIs for I/O Filters (VAIO) installation of filters on cluster {computeResource.name} is successful vSphere APIs for I/O Filters (VAIO) installation of filters on cluster {computeResource.name} in datacenter {datacenter.name} is successful
com.vmware.vc.iofilter.FilterUninstallationFailedEvent vSphere APIs for I/O Filters (VAIO) uninstallation of filters has failed error vSphere APIs for I/O Filters (VAIO) uninstallation of filters on cluster {computeResource.name} in datacenter {datacenter.name} has failed vSphere APIs for I/O Filters (VAIO) uninstallation of filters on cluster {computeResource.name} has failed vSphere APIs for I/O Filters (VAIO) uninstallation of filters on cluster {computeResource.name} in datacenter {datacenter.name} has failed
com.vmware.vc.iofilter.FilterUninstallationSuccessEvent vSphere APIs for I/O Filters (VAIO) uninstallation of filters is successful info vSphere APIs for I/O Filters (VAIO) uninstallation of filters on cluster {computeResource.name} in datacenter {datacenter.name} is successful vSphere APIs for I/O Filters (VAIO) uninstallation of filters on cluster {computeResource.name} are successful vSphere APIs for I/O Filters (VAIO) uninstallation of filters on cluster {computeResource.name} in datacenter {datacenter.name} is successful
com.vmware.vc.iofilter.FilterUpgradeFailedEvent vSphere APIs for I/O Filters (VAIO) upgrade of filters has failed error vSphere APIs for I/O Filters (VAIO) upgrade of filters on cluster {computeResource.name} and in datacenter {datacenter.name} has failed vSphere APIs for I/O Filters (VAIO) upgrade of filters on cluster {computeResource.name} has failed vSphere APIs for I/O Filters (VAIO) upgrade of filters on cluster {computeResource.name} in datacenter {datacenter.name} has failed
com.vmware.vc.iofilter.FilterUpgradeSuccessEvent vSphere APIs for I/O Filters (VAIO) upgrade of filters is successful info vSphere APIs for I/O Filters (VAIO) upgrade of filters on cluster {computeResource.name} in datacenter {datacenter.name} is successful vSphere APIs for I/O Filters (VAIO) upgrade of filters on cluster {computeResource.name} is successful vSphere APIs for I/O Filters (VAIO) upgrade of filters on cluster {computeResource.name} in datacenter {datacenter.name} has succeeded
com.vmware.vc.iofilter.HostVendorProviderRegistrationSuccessEvent vSphere APIs for I/O Filters (VAIO) host vendor provider has been successfully registered info vSphere APIs for I/O Filters (VAIO) vendor provider {host.name} has been successfully registered vSphere APIs for I/O Filters (VAIO) vendor provider {host.name} has been successfully registered vSphere APIs for I/O Filters (VAIO) vendor provider {host.name} has been successfully registered vSphere APIs for I/O Filters (VAIO) vendor provider {host.name} has been successfully registered
com.vmware.vc.iofilter.HostVendorProviderUnregistrationSuccessEvent Failed to unregister vSphere APIs for I/O Filters (VAIO) host vendor provider info Failed to unregister vSphere APIs for I/O Filters (VAIO) vendor provider {host.name} Failed to unregister vSphere APIs for I/O Filters (VAIO) vendor provider {host.name} Failed to unregister vSphere APIs for I/O Filters (VAIO) vendor provider {host.name} Failed to unregister vSphere APIs for I/O Filters (VAIO) vendor provider {host.name}
com.vmware.vc.profile.AnswerFileExportedEvent Answer file exported info Answer file for host {host.name} has been exported Answer file for host {host.name} has been exported Answer file exported Answer file for host {host.name} in datacenter {datacenter.name} has been exported
com.vmware.vc.profile.AnswerFileUpdatedEvent Host customization settings updated info Host customization settings for host {host.name} has been updated Host customization settings for host {host.name} has been updated Host customization settings updated Host customization settings for host {host.name} in datacenter {datacenter.name} has been updated
com.vmware.vc.sdrs.CanceledDatastoreMaintenanceModeEvent Datastore maintenance mode operation canceled info The datastore maintenance mode operation has been canceled The datastore maintenance mode operation has been canceled The datastore maintenance mode operation has been canceled The datastore maintenance mode operation has been canceled The datastore maintenance mode operation has been canceled
com.vmware.vc.sdrs.ConfiguredStorageDrsOnPodEvent Configured storage DRS info Configured storage DRS on datastore cluster {objectName} Configured storage DRS on datastore cluster {objectName} Configured storage DRS on datastore cluster {objectName} Configured storage DRS on datastore cluster {objectName} Configured storage DRS on datastore cluster {objectName}
com.vmware.vc.sdrs.ConsistencyGroupViolationEvent Datastore cluster has datastores that belong to different SRM Consistency Groups warning Datastore cluster {objectName} has datastores that belong to different SRM Consistency Groups Datastore cluster {objectName} has datastores that belong to different SRM Consistency Groups Datastore cluster {objectName} has datastores that belong to different SRM Consistency Groups Datastore cluster {objectName} has datastores that belong to different SRM Consistency Groups Datastore cluster {objectName} has datastores that belong to different SRM Consistency Groups
com.vmware.vc.sdrs.DatastoreEnteredMaintenanceModeEvent Datastore entered maintenance mode info Datastore {ds.name} has entered maintenance mode Datastore {ds.name} has entered maintenance mode Datastore {ds.name} has entered maintenance mode Datastore {ds.name} has entered maintenance mode Datastore {ds.name} has entered maintenance mode
com.vmware.vc.sdrs.DatastoreEnteringMaintenanceModeEvent Datastore is entering maintenance mode info Datastore {ds.name} is entering maintenance mode Datastore {ds.name} is entering maintenance mode Datastore {ds.name} is entering maintenance mode Datastore {ds.name} is entering maintenance mode Datastore {ds.name} is entering maintenance mode
com.vmware.vc.sdrs.DatastoreExitedMaintenanceModeEvent Datastore exited maintenance mode info Datastore {ds.name} has exited maintenance mode Datastore {ds.name} has exited maintenance mode Datastore {ds.name} has exited maintenance mode Datastore {ds.name} has exited maintenance mode Datastore {ds.name} has exited maintenance mode
com.vmware.vc.sdrs.DatastoreMaintenanceModeErrorsEvent Errors encountered while datastore entering into maintenance mode error Datastore {ds.name} encountered errors while entering maintenance mode Datastore {ds.name} encountered errors while entering maintenance mode Datastore {ds.name} encountered errors while entering maintenance mode Datastore {ds.name} encountered errors while entering maintenance mode Datastore {ds.name} encountered errors while entering maintenance mode
com.vmware.vc.sdrs.StorageDrsDisabledEvent Storage DRS disabled info Disabled storage DRS on datastore cluster {objectName} Disabled storage DRS on datastore cluster {objectName} Disabled storage DRS on datastore cluster {objectName} Disabled storage DRS on datastore cluster {objectName} Disabled storage DRS on datastore cluster {objectName}
com.vmware.vc.sdrs.StorageDrsInvocationFailedEvent Storage DRS invocation failed error Storage DRS invocation failed on datastore cluster {objectName} Storage DRS invocation failed on datastore cluster {objectName} Storage DRS invocation failed on datastore cluster {objectName} Storage DRS invocation failed on datastore cluster {objectName} Storage DRS invocation failed on datastore cluster {objectName}
com.vmware.vc.sdrs.StorageDrsNewRecommendationPendingEvent New storage DRS recommendation generated info A new storage DRS recommendation has been generated on datastore cluster {objectName} A new storage DRS recommendation has been generated on datastore cluster {objectName} A new storage DRS recommendation has been generated on datastore cluster {objectName} A new storage DRS recommendation has been generated on datastore cluster {objectName} A new storage DRS recommendation has been generated on datastore cluster {objectName}
com.vmware.vc.sdrs.StorageDrsRecommendationApplied Pending storage recommendations were applied info All pending recommendations on datastore cluster {objectName} were applied All pending recommendations on datastore cluster {objectName} were applied All pending recommendations on datastore cluster {objectName} were applied All pending recommendations on datastore cluster {objectName} were applied All pending recommendations on datastore cluster {objectName} were applied
com.vmware.vc.sms.VasaProviderRefreshCACertsAndCRLsSuccess Refreshing CA certificates and CRLs succeeded for all registered VASA providers. info Refreshing CA certificates and CRLs succeeded for all registered VASA providers.
com.vmware.vc.stats.HostQuickStatesNotUpToDateEvent Quick stats is not up-to-date info Quick stats on {host.name} in {computeResource.name} is not up-to-date Quick stats on {host.name} is not up-to-date Quick stats on {host.name} is not up-to-date Quick stats on {host.name} in {computeResource.name} in {datacenter.name} is not up-to-date
com.vmware.vc.vcp.FtDisabledVmTreatAsNonFtEvent FT Disabled VM protected as non-FT VM info HA VM Component Protection protects virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} as non-FT virtual machine because the FT state is disabled HA VM Component Protection protects virtual machine {vm.name} on host {host.name} as non-FT virtual machine because the FT state is disabled HA VM Component Protection protects virtual machine {vm.name} as non-FT virtual machine because the FT state is disabled HA VM Component Protection will protect this virtul machine as non-FT virtual machine because the FT state is disabled HA VM Component Protection protects virtual machine {vm.name} on {host.name} in cluster {computeResource.name} in datacenter {datacenter.name} as non-FT virtual machine because the FT state is disabled
com.vmware.vc.vcp.FtFailoverEvent Failover FT VM due to component failure info FT Primary VM {vm.name} on host {host.name} in cluster {computeResource.name} is going to fail over to Secondary VM due to component failure FT Primary VM {vm.name} on host {host.name} is going to fail over to Secondary VM due to component failure FT Primary VM {vm.name} is going to fail over to Secondary VM due to component failure FT Primary VM is going to fail over to Secondary VM due to component failure FT Primary VM {vm.name} on host {host.name} in cluster {computeResource.name} in datacenter {datacenter.name} is going to fail over to Secondary VM due to component failure
com.vmware.vc.vcp.FtFailoverFailedEvent FT VM failover failed error FT virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} failed to failover to secondary FT virtual machine {vm.name} on host {host.name} failed to failover to secondary FT virtual machine {vm.name} failed to failover to secondary FT virtual machine failed to failover to secondary FT virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in datacenter {datacenter.name} failed to failover to secondary
com.vmware.vc.vcp.FtSecondaryRestartEvent Restarting FT secondary due to component failure info HA VM Component Protection is restarting FT secondary virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} due to component failure HA VM Component Protection is restarting FT secondary virtual machine {vm.name} on host {host.name} due to component failure HA VM Component Protection is restarting FT secondary virtual machine {vm.name} due to component failure HA VM Component Protection is restarting FT secondary virtual machine due to component failure HA VM Component Protection is restarting FT secondary virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in datacenter {datacenter.name} due to component failure
com.vmware.vc.vcp.FtSecondaryRestartFailedEvent FT secondary VM restart failed error FT Secondary VM {vm.name} on host {host.name} in cluster {computeResource.name} failed to restart FT Secondary VM {vm.name} on host {host.name} failed to restart FT Secondary VM {vm.name} failed to restart FT Secondary VM failed to restart FT Secondary VM {vm.name} on host {host.name} in cluster {computeResource.name} in datacenter {datacenter.name} failed to restart
com.vmware.vc.vcp.NeedSecondaryFtVmTreatAsNonFtEvent Need secondary VM protected as non-FT VM info HA VM Component Protection protects virtual machine {vm.name} on host {host.name} as non-FT virtual machine since it has been in the needSecondary state too long HA VM Component Protection protects virtual machine {vm.name} on host {host.name} as non-FT virtual machine because it has been in the needSecondary state too long HA VM Component Protection protects virtual machine {vm.name} as non-FT virtual machine because it has been in the needSecondary state too long HA VM Component Protection protects this virtul machine as non-FT virtual machine because it has been in the needSecondary state too long HA VM Component Protection protects virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in datacenter {datacenter.name} as non-FT virtual machine because it has been in the needSecondary state too long
com.vmware.vc.vcp.VcpNoActionEvent No action on VM info HA VM Component Protection did not take action on virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} due to the feature configuration setting HA VM Component Protection did not take action on virtual machine {vm.name} on host {host.name} due to the feature configuration setting HA VM Component Protection did not take action on virtual machine {vm.name} due to the feature configuration setting HA VM Component Protection did not take action due to the feature configuration setting HA VM Component Protection did not take action on virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in datacenter {datacenter.name} due to the feature configuration setting
com.vmware.vc.vcp.VmRestartEvent Restarting VM due to component failure info HA VM Component Protection is restarting virtual machine {vm.name} due to component failure on host {host.name} in cluster {computeResource.name} HA VM Component Protection is restarting virtual machine {vm.name} due to component failure on host {host.name} HA VM Component Protection is restarting virtual machine {vm.name} due to component failure HA VM Component Protection is restarting virtual machine due to component failure HA VM Component Protection is restarting virtual machine {vm.name} due to component failure on host {host.name} in cluster {computeResource.name} in datacenter {datacenter.name}
com.vmware.vc.vcp.VmRestartFailedEvent Virtual machine affected by component failure failed to restart error Virtual machine {vm.name} affected by component failure on host {host.name} in cluster {computeResource.name} failed to restart Virtual machine {vm.name} affected by component failure on host {host.name} failed to restart Virtual machine {vm.name} affected by component failure failed to restart Virtual machine affected by component failure failed to restart Virtual machine {vm.name} affected by component failure on host {host.name} in cluster {computeResource.name} in datacenter {datacenter.name} failed to restart
com.vmware.vc.vm.PowerOnAfterCloneErrorEvent Virtual machine failed to power on after cloning. error Virtual machine {vm.name} failed to power on after cloning on host {host.name}. Virtual machine {vm.name} failed to power on after cloning on host {host.name}. Virtual machine {vm.name} failed to power on after performing cloning operation on this host. Virtual machine failed to power on after cloning. Virtual machine {vm.name} failed to power on after cloning on host {host.name} in datacenter {datacenter.name}
com.vmware.vc.vm.VmRegisterFailedEvent Virtual machine register failed error Virtual machine {vm.name} registration on host {host.name} failed Virtual machine {vm.name} registration on host {host.name} failed Virtual machine {vm.name} registration on this host failed Virtual machine registration failed Virtual machine {vm.name} registration on {host.name} in datacenter {datacenter.name} failed
com.vmware.vc.vmam.AppMonitoringNotSupported Application Monitoring Is Not Supported warning Application monitoring is not supported on {host.name} in cluster {computeResource.name} Application monitoring is not supported on {host.name} Application monitoring is not supported Application monitoring is not supported on {host.name} in cluster {computeResource.name} in {datacenter.name}
com.vmware.vc.vmam.VmDasAppHeartbeatFailedEvent vSphere HA detected application heartbeat failure warning vSphere HA detected application heartbeat failure for {vm.name} on {host.name} in cluster {computeResource.name} vSphere HA detected application heartbeat failure for {vm.name} on {host.name} vSphere HA detected application heartbeat failure for {vm.name} vSphere HA detected application heartbeat failure for this virtual machine vSphere HA detected application heartbeat failure for {vm.name} on {host.name} in cluster {computeResource.name} in {datacenter.name}
com.vmware.vc.vsan.ChecksumDisabledHostFoundEvent Found a checksum disabled host in a checksum protected cluster error Found a checksum disabled host {host.name} in a checksum protected vCenter Server cluster {computeResource.name} Found a checksum disabled host {host.name} in a checksum protected vCenter Server cluster Found a checksum disabled host in a checksum protected cluster Found a checksum disabled host {host.name} in a checksum protected vCenter Server cluster {computeResource.name} in datacenter {datacenter.name} Found a checksum disabled host {host.name} in a checksum protected vCenter Server cluster {computeResource.name} in datacenter {datacenter.name}
com.vmware.vc.vsan.HostNotInClusterEvent Host with Virtual SAN service enabled is not in the vCenter cluster error {host.name} with Virtual SAN service enabled is not in the vCenter cluster {computeResource.name} {host.name} with Virtual SAN service enabled is not in the vCenter cluster Host with Virtual SAN service enabled is not in the vCenter cluster {host.name} with Virtual SAN service enabled is not in the vCenter cluster {computeResource.name} in datacenter {datacenter.name} {host.name} with Virtual SAN service enabled is not in the vCenter cluster {computeResource.name} in datacenter {datacenter.name}
com.vmware.vc.vsan.HostNotInVsanClusterEvent Host is in a Virtual SAN cluster but does not have Virtual SAN service enabled error {host.name} is in a Virtual SAN cluster {computeResource.name} but does not have Virtual SAN service enabled {host.name} is in a Virtual SAN cluster but does not have Virtual SAN service enabled Host is in a Virtual SAN cluster but does not have Virtual SAN service enabled {host.name} is in a Virtual SAN enabled cluster {computeResource.name} in datacenter {datacenter.name} but does not have Virtual SAN service enabled {host.name} is in a Virtual SAN enabled cluster {computeResource.name} in datacenter {datacenter.name} but does not have Virtual SAN service enabled
com.vmware.vc.vsan.HostVendorProviderDeregistrationSuccessEvent Virtual SAN host vendor provider has been successfully unregistered info Virtual SAN vendor provider {host.name} has been successfully unregistered Virtual SAN vendor provider {host.name} has been successfully unregistered Virtual SAN vendor provider {host.name} has been successfully unregistered Virtual SAN vendor provider {host.name} has been successfully unregistered
com.vmware.vc.vsan.HostVendorProviderRegistrationSuccessEvent Virtual SAN host vendor provider registration succeeded info Virtual SAN vendor provider {host.name} has been successfully registered Virtual SAN vendor provider {host.name} has been successfully registered Virtual SAN vendor provider {host.name} has been successfully registered Virtual SAN vendor provider {host.name} has been successfully registered
com.vmware.vc.vsan.NetworkMisConfiguredEvent Virtual SAN network is not configured error Virtual SAN network is not configured on {host.name} in cluster {computeResource.name} Virtual SAN network is not configured on {host.name} Virtual SAN network is not configured Virtual SAN network is not configured on {host.name}, in cluster {computeResource.name}, and in datacenter {datacenter.name} Virtual SAN network is not configured on {host.name}, in cluster {computeResource.name}, and in datacenter {datacenter.name}
esx.audit.dcui.defaults.factoryrestore Restoring factory defaults through DCUI. warning The host has been restored to default factory settings. Please consult ESXi Embedded and vCenter Server Setup Guide or follow the Ask VMware link for more information.
esx.audit.dcui.disabled The DCUI has been disabled. info The DCUI has been disabled.
esx.audit.dcui.enabled The DCUI has been enabled. info The DCUI has been enabled.
esx.audit.dcui.host.reboot Rebooting host through DCUI. warning The host is being rebooted through the Direct Console User Interface (DCUI). Please consult ESXi Embedded and vCenter Server Setup Guide or follow the Ask VMware link for more information.
esx.audit.dcui.host.shutdown Shutting down host through DCUI. warning The host is being shut down through the Direct Console User Interface (DCUI). Please consult ESXi Embedded and vCenter Server Setup Guide or follow the Ask VMware link for more information.
esx.audit.dcui.hostagents.restart Restarting host agents through DCUI. info The management agents on the host are being restarted. Please consult ESXi Embedded and vCenter Server Setup Guide or follow the Ask VMware link for more information.
esx.audit.dcui.network.factoryrestore Factory network settings restored through DCUI. warning The host has been restored to factory network settings. Please consult ESXi Embedded and vCenter Server Setup Guide or follow the Ask VMware link for more information.
esx.audit.esximage.install.novalidation Attempting to install an image profile with validation disabled. warning Attempting to install an image profile with validation disabled. This may result in an image with unsatisfied dependencies, file or package conflicts, and potential security violations.
esx.audit.host.boot Host has booted. info Host has booted.
esx.audit.host.stop.reboot Host is rebooting. info Host is rebooting.
esx.audit.host.stop.shutdown Host is shutting down. info Host is shutting down.
esx.audit.lockdownmode.disabled Administrator access to the host has been enabled. info Administrator access to the host has been enabled.
esx.audit.lockdownmode.enabled Administrator access to the host has been disabled. info Administrator access to the host has been disabled.
esx.audit.lockdownmode.exceptions.changed List of lockdown exception users has been changed. info List of lockdown exception users has been changed.
esx.audit.maintenancemode.canceled The host has canceled entering maintenance mode. info The host has canceled entering maintenance mode.
esx.audit.maintenancemode.entered The host has entered maintenance mode. info The host has entered maintenance mode.
esx.audit.maintenancemode.entering The host has begun entering maintenance mode. info The host has begun entering maintenance mode.
esx.audit.maintenancemode.exited The host has exited maintenance mode. info The host has exited maintenance mode.
esx.audit.net.firewall.disabled Firewall has been disabled. warning Firewall has been disabled.
esx.audit.shell.disabled The ESXi command line shell has been disabled. info The ESXi command line shell has been disabled.
esx.audit.shell.enabled The ESXi command line shell has been enabled. info The ESXi command line shell has been enabled.
esx.audit.ssh.disabled SSH access has been disabled. info SSH access has been disabled.
esx.audit.ssh.enabled SSH access has been enabled. info SSH access has been enabled.
esx.audit.usb.config.changed USB configuration has changed. info USB configuration has changed on host {host.name} in cluster {computeResource.name}. USB configuration has changed on host {host.name}. USB configuration has changed. USB configuration has changed on host {host.name} in cluster {computeResource.name} in {datacenter.name}.
esx.audit.vmfs.lvm.device.discovered LVM device discovered. info One or more LVM devices have been discovered on this host.
esx.audit.vsan.clustering.enabled Virtual SAN clustering services have been enabled. info Virtual SAN clustering and directory services have been enabled. Virtual SAN clustering and directory services have been enabled.
esx.audit.vsan.net.vnic.added Virtual SAN virtual NIC has been added. info Virtual SAN virtual NIC has been added. Virtual SAN virtual NIC has been added.
esx.clear.coredump.configured A vmkcore disk partition is available and/or a network coredump server has been configured. Host core dumps will be saved. info A vmkcore disk partition is available and/or a network coredump server has been configured. Host core dumps will be saved. A vmkcore disk partition is available and/or a network coredump server has been configured. Host core dumps will be saved.
esx.clear.coredump.configured2 At least one coredump target has been configured. Host core dumps will be saved. info At least one coredump target has been configured. Host core dumps will be saved. At least one coredump target has been configured. Host core dumps will be saved.
esx.problem.coredump.unconfigured No vmkcore disk partition is available and no network coredump server has been configured. Host core dumps cannot be saved. warning No vmkcore disk partition is available and no network coredump server has been configured. Host core dumps cannot be saved. No vmkcore disk partition is available and no network coredump server has been configured. Host core dumps cannot be saved.
esx.problem.coredump.unconfigured2 No coredump target has been configured. Host core dumps cannot be saved. warning No coredump target has been configured. Host core dumps cannot be saved. No coredump target has been configured. Host core dumps cannot be saved.
esx.problem.cpu.amd.mce.dram.disabled DRAM ECC not enabled. Please enable it in BIOS. error DRAM ECC not enabled. Please enable it in BIOS.
esx.problem.cpu.intel.ioapic.listing.error Not all IO-APICs are listed in the DMAR. Not enabling interrupt remapping on this platform. error Not all IO-APICs are listed in the DMAR. Not enabling interrupt remapping on this platform.
esx.problem.cpu.mce.invalid MCE monitoring will be disabled as an unsupported CPU was detected. Please consult the ESX HCL for information on supported hardware. error MCE monitoring will be disabled as an unsupported CPU was detected. Please consult the ESX HCL for information on supported hardware.
esx.problem.host.coredump An unread host kernel core dump has been found. warning An unread host kernel core dump has been found.
esx.problem.migrate.vmotion.default.heap.create.failed Failed to create default migration heap warning Failed to create default migration heap. This might be the result of severe host memory pressure or virtual address space exhaustion. Migration might still be possible, but will be unreliable in cases of extreme host memory pressure.
esx.problem.scsi.apd.event.descriptor.alloc.failed No memory to allocate APD Event warning No memory to allocate APD (All Paths Down) event subsystem.
esx.problem.scsi.device.io.invalid.disk.qfull.value Scsi device queue parameters incorrectly set. warning QFullSampleSize should be bigger than QFullThreshold. LUN queue depth throttling algorithm will not function as expected. Please set the QFullSampleSize and QFullThreshold disk configuration values in ESX correctly.
esx.problem.syslog.config System logging is not configured. warning System logging is not configured on host {host.name}. System logging is not configured on host {host.name}. Please check Syslog options for the host under Configuration -> Software -> Advanced Settings in vSphere client.
esx.problem.syslog.nonpersistent System logs are stored on non-persistent storage. warning System logs on host {host.name} are stored on non-persistent storage. System logs on host {host.name} are stored on non-persistent storage. Consult product documentation to configure a syslog server or a scratch partition.
esx.problem.visorfs.failure An operation on the root filesystem has failed. error An operation on the root filesystem has failed.
esx.problem.vmsyslogd.storage.failure Logging to storage has failed. error Logging to storage has failed. Logs are no longer being stored locally on this host.
hbr.primary.ConnectionRestoredToHbrServerEvent Connection to VR Server restored. info Connection to VR Server restored for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name}. Connection to VR Server restored for virtual machine {vm.name} on host {host.name}. Connection to VR Server restored for virtual machine {vm.name}. Connection to VR Server restored. Connection to VR Server restored for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}.
hbr.primary.DeltaStartedEvent Sync started. info Sync started by {userName} for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name}. Sync started by {userName} for virtual machine {vm.name} on host {host.name}. Sync started by {userName} for virtual machine {vm.name}. Sync started by {userName}. Sync started by {userName} for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}.
hbr.primary.QuiesceNotSupported Quiescing is not supported for this virtual machine. warning Quiescing is not supported for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name}. Quiescing is not supported for virtual machine {vm.name} on host {host.name}. Quiescing is not supported for virtual machine {vm.name}. Quiescing is not supported for this virtual machine. Quiescing is not supported for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}.
hbr.primary.RpoOkForServerEvent VR Server is compatible with the configured RPO. info VR Server is compatible with support the configured RPO for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name}. VR Server is compatible with the configured RPO for virtual machine {vm.name} on host {host.name}. VR Server is compatible with the configured RPO for virtual machine {vm.name}. VR Server is compatible with the configured RPO. VR Server is compatible with support the configured RPO for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}.
hbr.primary.RpoTooLowForServerEvent VR Server does not support the configured RPO. warning VR Server does not support the configured RPO for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name}. VR Server does not support the configured RPO for virtual machine {vm.name} on host {host.name}. VR Server does not support the configured RPO for virtual machine {vm.name}. VR Server does not support the configured RPO. VR Server does not support the configured RPO for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}.
hbr.primary.SyncStartedEvent Full sync started. info Full sync started for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name}. Full sync started for virtual machine {vm.name} on host {host.name}. Full sync started for virtual machine {vm.name}. Full sync started. Full sync started by {userName} for virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}.
vim.event.SubscriptionLicenseExpiredEvent The time-limited license on the host has expired. warning The time-limited license on host {host.name} has expired. The time-limited license on host {host.name} has expired. The time-limited license on the host has expired. The time-limited license on host {host.name} has expired. To comply with the EULA, renew the license at http://my.vmware.com
com.vmware.vim.eam.issue.unknownAgentVm error Unknown agent VM {vm.name}
com.vmware.vim.eam.login.invalid Invalid login warning Failed login to vSphere ESX Agent Manager
com.vmware.vim.eam.task.scanForUnknownAgentVmsCompleted Scan for unknown agent VMs completed info Scan for unknown agent VMs completed
com.vmware.vim.eam.task.scanForUnknownAgentVmsInitiated Scan for unknown agent VMs initiated info Scan for unknown agent VMs initiated
FailoverLevelRestored vSphere HA failover resources are sufficient info Sufficient resources are available to satisfy vSphere HA failover level in cluster {computeResource.name} Sufficient resources are available to satisfy vSphere HA failover level Sufficient resources are available to satisfy vSphere HA failover level in cluster {computeResource.name} in {datacenter.name}
GeneralEvent General event info General event: {message}
GeneralHostErrorEvent Host error error Error detected on {host.name}: {message} Error detected on {host.name}: {message} {message} Error detected on {host.name} in {datacenter.name}: {message}
GeneralHostInfoEvent Host information info Issue detected on {host.name}: {message} Issue detected on {host.name}: {message} {message} Issue detected on {host.name} in {datacenter.name}: {message}
GeneralHostWarningEvent Host warning warning Issue detected on {host.name}: {message} Issue detected on {host.name}: {message} {message} Issue detected on {host.name} in {datacenter.name}: {message}
GeneralUserEvent User event user User logged event: {message}
GeneralVmErrorEvent VM error error Error detected for {vm.name} on {host.name} in {datacenter.name}: {message} Error detected for {vm.name} on {host.name} in {datacenter.name}: {message} Error detected for {vm.name}: {message} {message} on {host.name} Error detected for {vm.name} on {host.name} in {datacenter.name}: {message}
GeneralVmInfoEvent VM information info Issue detected for {vm.name} on {host.name} in {datacenter.name}: {message} Issue detected for {vm.name} on {host.name} in {datacenter.name}: {message} Issue detected for {vm.name}: {message} {message} on {host.name} Issue detected for {vm.name} on {host.name} in {datacenter.name}: {message}
GeneralVmWarningEvent VM warning warning Issue detected for {vm.name} on {host.name} in {datacenter.name}: {message} Issue detected for {vm.name} on {host.name} in {datacenter.name}: {message} Issue detected for {vm.name}: {message} {message} on {host.name} Issue detected for {vm.name} on {host.name} in {datacenter.name}: {message}
GhostDvsProxySwitchDetectedEvent The vSphere Distributed Switch corresponding to the proxy switches on the host does not exist in vCenter Server or does not contain this host. info The vSphere Distributed Switch corresponding to the proxy switches {switchUuid} on the host does not exist in vCenter Server or does not contain this host. The vSphere Distributed Switch corresponding to the proxy switches {switchUuid} on the host {host.name} does not exist in vCenter Server or does not contain this host.
GhostDvsProxySwitchRemovedEvent A ghost proxy switch on the host was resolved. info A ghost proxy switch {switchUuid} on the host was resolved. A ghost proxy switch {switchUuid} on the host {host.name} was resolved.
GlobalMessageChangedEvent Message changed info The message changed: {message}
HealthStatusChangedEvent Status change info {componentName} status changed from {oldStatus} to {newStatus}
HostAddedEvent Host Added info Added host {host.name} Added host {host.name} Added host {host.name} to datacenter {datacenter.name}
HostAddFailedEvent Cannot add host error Cannot add host {hostname} Cannot add host {hostname} Cannot add host {hostname} to datacenter {datacenter.name}
HostAdminDisableEvent Host administrator access disabled warning Administrator access to the host is disabled Administrator access to the host {host.name} is disabled
HostAdminEnableEvent Host administrator access enabled warning Administrator access to the host has been restored Administrator access to the host {host.name} has been restored
HostCnxFailedAccountFailedEvent Cannot connect host and configure management account error Cannot connect {host.name}: cannot configure management account Cannot connect {host.name}: cannot configure management account Cannot connect: cannot configure management account Cannot connect {host.name} in {datacenter.name}: cannot configure management account
HostCnxFailedAlreadyManagedEvent Cannot connect host - already managed error Cannot connect {host.name}: already managed by {serverName} Cannot connect {host.name}: already managed by {serverName} Cannot connect: already managed by {serverName} Cannot connect {host.name} in {datacenter.name}: already managed by {serverName}
HostCnxFailedBadCcagentEvent Cannot connect host - incorrect Ccagent error Cannot connect {host.name} : server agent is not responding Cannot connect {host.name} : server agent is not responding Cannot connect: server agent is not responding Cannot connect host {host.name} in {datacenter.name} : server agent is not responding
HostCnxFailedBadUsernameEvent Cannot connect host - incorrect user name error Cannot connect {host.name}: incorrect user name or password Cannot connect {host.name}: incorrect user name or password Cannot connect: incorrect user name or password Cannot connect {host.name} in {datacenter.name}: incorrect user name or password
HostCnxFailedBadVersionEvent Cannot connect host - incompatible version error Cannot connect {host.name}: incompatible version Cannot connect {host.name}: incompatible version Cannot connect: incompatible version Cannot connect {host.name} in {datacenter.name}: incompatible version
HostCnxFailedCcagentUpgradeEvent Cannot connect host - Ccagent upgrade error Cannot connect host {host.name}: did not install or upgrade vCenter agent service Cannot connect host {host.name}: did not install or upgrade vCenter agent service Cannot connect: did not install or upgrade vCenter agent service Cannot connect host {host.name} in {datacenter.name}. Did not install or upgrade vCenter agent service.
HostCnxFailedEvent Cannot connect host error Cannot connect host {host.name}: error connecting to host Cannot connect host {host.name}: error connecting to host Cannot connect: error connecting to host Cannot connect {host.name} in {datacenter.name}: error connecting to host
HostCnxFailedNetworkErrorEvent Cannot connect host - network error error Cannot connect {host.name}: network error Cannot connect {host.name}: network error Cannot connect: network error Cannot connect {host.name} in {datacenter.name}: network error
HostCnxFailedNoAccessEvent Cannot connect host - no access error Cannot connect {host.name}: account has insufficient privileges Cannot connect {host.name}: account has insufficient privileges Cannot connect: account has insufficient privileges Cannot connect host {host.name} in {datacenter.name}: account has insufficient privileges
HostCnxFailedNoConnectionEvent Cannot connect host - no connection error Cannot connect {host.name} Cannot connect {host.name} Cannot connect to host Cannot connect host {host.name} in {datacenter.name}
HostCnxFailedNoLicenseEvent Cannot connect host - no license error Cannot connect {host.name}: not enough CPU licenses Cannot connect {host.name}: not enough CPU licenses Cannot connect: not enough CPU licenses Cannot connect {host.name} in {datacenter.name}: not enough CPU licenses
HostCnxFailedNotFoundEvent Cannot connect host - host not found error Cannot connect {host.name}: incorrect host name Cannot connect {host.name}: incorrect host name Cannot connect: incorrect host name Cannot connect {host.name} in {datacenter.name}: incorrect host name
HostCnxFailedTimeoutEvent Cannot connect host - time-out error Cannot connect {host.name}: time-out waiting for host response Cannot connect {host.name}: time-out waiting for host response Cannot connect: time-out waiting for host response Cannot connect {host.name} in {datacenter.name}: time-out waiting for host response
HostComplianceCheckedEvent Checked host for compliance info Host {host.name} checked for compliance with profile {profile.name} Host {host.name} checked for compliance with profile {profile.name} Checked host for compliance with profile {profile.name} Host {host.name} checked for compliance.
HostCompliantEvent Host compliant with profile info Host is in compliance with the attached profile. Host {host.name} is in compliance with the attached profile
HostConfigAppliedEvent Host configuration changes applied to host info Host configuration changes applied to {host.name} Host configuration changes applied to {host.name} Host configuration changes applied. Host configuration changes applied.
HostConnectedEvent Host connected info Connected to {host.name} Connected to {host.name} Established a connection Connected to {host.name} in {datacenter.name}
HostConnectionLostEvent Host connection lost error Host {host.name} is not responding Host {host.name} is not responding Host is not responding Host {host.name} in {datacenter.name} is not responding
HostDasDisabledEvent vSphere HA agent disabled on host info vSphere HA agent on {host.name} in cluster {computeResource.name} is disabled vSphere HA agent on {host.name} is disabled vSphere HA agent on this host is disabled vSphere HA agent on {host.name} in cluster {computeResource.name} in {datacenter.name} is disabled
HostDasDisablingEvent Disabling vSphere HA info vSphere HA is being disabled on {host.name} vSphere HA is being disabled on {host.name} Disabling vSphere HA vSphere HA is being disabled on {host.name} in cluster {computeResource.name} in datacenter {datacenter.name}
HostDasEnabledEvent vSphere HA agent enabled on host info vSphere HA agent on {host.name} in cluster {computeResource.name} is enabled vSphere HA agent on {host.name} is enabled vSphere HA agent on this host is enabled vSphere HA agent on {host.name} in cluster {computeResource.name} in {datacenter.name} is enabled
HostDasEnablingEvent Enabling host vSphere HA agent warning Enabling vSphere HA agent on {host.name} Enabling vSphere HA agent on {host.name} Enabling vSphere HA agent Enabling vSphere HA agent on {host.name} in cluster {computeResource.name} in {datacenter.name}
HostDasErrorEvent vSphere HA agent error error vSphere HA agent on host {host.name} has an error {message} : {reason.@enum.HostDasErrorEvent.HostDasErrorReason} vSphere HA agent on host {host.name} has an error {message} : {reason.@enum.HostDasErrorEvent.HostDasErrorReason} vSphere HA agent has an error {message} : {reason.@enum.HostDasErrorEvent.HostDasErrorReason} vSphere HA agent on {host.name} in cluster {computeResource.name} in {datacenter.name} has an error {message}: {reason.@enum.HostDasErrorEvent.HostDasErrorReason}
HostDasOkEvent vSphere HA agent configured info vSphere HA agent on host {host.name} is configured correctly vSphere HA agent on host {host.name} is configured correctly vSphere HA agent is configured correctly vSphere HA agent on host {host.name} in cluster {computeResource.name} in {datacenter.name} is configured correctly
HostDisconnectedEvent Host disconnected info Disconnected from {host.name}. Reason: {reason.@enum.HostDisconnectedEvent.ReasonCode} Disconnected from {host.name}. Reason: {reason.@enum.HostDisconnectedEvent.ReasonCode} Disconnected from host. Reason: {reason.@enum.HostDisconnectedEvent.ReasonCode} Disconnected from {host.name} in {datacenter.name}. Reason: {reason.@enum.HostDisconnectedEvent.ReasonCode}
HostDVPortEvent dvPort connected to host changed status info dvPort connected to host {host.name} changed status dvPort connected to host {host.name} changed status dvPort changed status dvPort connected to host {host.name} in {datacenter.name} changed status
HostEnableAdminFailedEvent Cannot restore administrator permissions to host error Cannot restore some administrator permissions to the host Cannot restore some administrator permissions to the host {host.name}
HostExtraNetworksEvent Host has extra vSphere HA networks error Host {host.name} has the following extra networks not used by other hosts for vSphere HA communication:{ips}. Consider using vSphere HA advanced option das.allowNetwork to control network usage Host {host.name} has the following extra networks not used by other hosts for vSphere HA communication:{ips}. Consider using vSphere HA advanced option das.allowNetwork to control network usage
HostGetShortNameFailedEvent Cannot get short host name error Cannot complete command 'hostname -s' or returned incorrect name format Cannot complete command 'hostname -s' on host {host.name} or returned incorrect name format
HostInAuditModeEvent Host is in audit mode. info Host is running in audit mode. Host {host.name} is running in audit mode. The host's configuration will not be persistent across reboots.
HostInventoryFullEvent Host inventory full error Maximum ({capacity}) number of hosts allowed for this edition of vCenter Server has been reached
HostInventoryUnreadableEvent Host Inventory Unreadable info The virtual machine inventory file is damaged or unreadable. The virtual machine inventory file on host {host.name} is damaged or unreadable.
HostIpChangedEvent Host IP changed info IP address changed from {oldIP} to {newIP} IP address of the host {host.name} changed from {oldIP} to {newIP}
HostIpInconsistentEvent Host IP inconsistent error Configuration of host IP address is inconsistent: address resolved to {ipAddress} and {ipAddress2} Configuration of host IP address is inconsistent on host {host.name}: address resolved to {ipAddress} and {ipAddress2}
HostIpToShortNameFailedEvent Host IP to short name not completed error Cannot resolve IP address to short name Cannot resolve IP address to short name on host {host.name}
HostIsolationIpPingFailedEvent vSphere HA isolation address unreachable error vSphere HA agent on host {host.name} in cluster {computeResource.name} could not reach isolation address: {isolationIp} vSphere HA agent on host {host.name} could not reach isolation address: {isolationIp} vSphere HA agent on this host could not reach isolation address: {isolationIp} vSphere HA agent on host {host.name} in cluster {computeResource.name} in {datacenter.name} could not reach isolation address: {isolationIp}
HostLicenseExpiredEvent Host license expired error A host license for {host.name} has expired
HostLocalPortCreatedEvent A host local port is created to recover from management network connectivity loss. info A host local port {hostLocalPort.portKey} is created on vSphere Distributed Switch {hostLocalPort.switchUuid} to recover from management network connectivity loss on virtual NIC device {hostLocalPort.vnic}. A host local port {hostLocalPort.portKey} is created on vSphere Distributed Switch {hostLocalPort.switchUuid} to recover from management network connectivity loss on virtual NIC device {hostLocalPort.vnic} on the host {host.name}.
HostMissingNetworksEvent Host is missing vSphere HA networks error Host {host.name} does not have the following networks used by other hosts for vSphere HA communication:{ips}. Consider using vSphere HA advanced option das.allowNetwork to control network usage Host {host.name} does not have the following networks used by other hosts for vSphere HA communication:{ips}. Consider using vSphere HA advanced option das.allowNetwork to control network usage
HostMonitoringStateChangedEvent vSphere HA host monitoring state changed info vSphere HA host monitoring state in {computeResource.name} changed to {state.@enum.DasConfigInfo.ServiceState} vSphere HA host monitoring state changed to {state.@enum.DasConfigInfo.ServiceState} vSphere HA host monitoring state in {computeResource.name} in {datacenter.name} changed to {state.@enum.DasConfigInfo.ServiceState}
HostNoAvailableNetworksEvent Host has no available networks for vSphere HA communication error Host {host.name} in cluster {computeResource.name} currently has no available networks for vSphere HA Communication. The following networks are currently used by HA: {ips} Host {host.name} currently has no available networks for vSphere HA Communication. The following networks are currently used by HA: {ips} This host currently has no available networks for vSphere HA Communication. The following networks are currently used by HA: {ips} Host {host.name} in cluster {computeResource.name} in {datacenter.name} currently has no available networks for vSphere HA Communication. The following networks are currently used by HA: {ips}
HostNoHAEnabledPortGroupsEvent Host has no port groups enabled for vSphere HA error Host {host.name} in cluster {computeResource.name} has no port groups enabled for vSphere HA communication. Host {host.name} has no port groups enabled for vSphere HA communication. This host has no port groups enabled for vSphere HA communication. Host {host.name} in cluster {computeResource.name} in {datacenter.name} has no port groups enabled for vSphere HA communication.
HostNonCompliantEvent Host non-compliant with profile error Host is not in compliance with the attached profile. Host {host.name} is not in compliance with the attached profile
HostNoRedundantManagementNetworkEvent No redundant management network for host warning Host {host.name} in cluster {computeResource.name} currently has no management network redundancy Host {host.name} currently has no management network redundancy This host currently has no management network redundancy Host {host.name} in cluster {computeResource.name} in {datacenter.name} currently has no management network redundancy
HostNotInClusterEvent Host not in cluster error Not a cluster member in {datacenter.name} Host {host.name} is not a cluster member in {datacenter.name}
HostOvercommittedEvent Host resource overcommitted error Insufficient capacity in host {computeResource.name} to satisfy resource configuration Insufficient capacity to satisfy resource configuration Insufficient capacity in host {computeResource.name} to satisfy resource configuration in {datacenter.name}
HostPrimaryAgentNotShortNameEvent Host primary agent not specified as short name error Primary agent {primaryAgent} was not specified as a short name Primary agent {primaryAgent} was not specified as a short name to host {host.name}
HostProfileAppliedEvent Host profile applied info Profile configuration applied to the host Profile is applied on the host {host.name}
HostReconnectionFailedEvent Cannot reconnect host error Cannot reconnect to {host.name} Cannot reconnect to {host.name} Cannot reconnect Cannot reconnect to {host.name} in {datacenter.name}
HostRemovedEvent Host removed info Removed host {host.name} Removed host {host.name} Removed from inventory Removed host {host.name} in {datacenter.name}
HostShortNameInconsistentEvent Host short name inconsistent error Host names {shortName} and {shortName2} both resolved to the same IP address. Check the host's network configuration and DNS entries
HostShortNameToIpFailedEvent Host short name to IP not completed error Cannot resolve short name {shortName} to IP address Cannot resolve short name {shortName} to IP address on host {host.name}
HostShutdownEvent Host shut down info Shut down of {host.name}: {reason} Shut down of {host.name}: {reason} Shut down of host: {reason} Shut down of {host.name} in {datacenter.name}: {reason}
HostStatusChangedEvent Host status changed info Configuration status on host {computeResource.name} changed from {oldStatus.@enum.ManagedEntity.Status} to {newStatus.@enum.ManagedEntity.Status} Configuration status changed from {oldStatus.@enum.ManagedEntity.Status} to {newStatus.@enum.ManagedEntity.Status} Configuration status on host {computeResource.name} changed from {oldStatus.@enum.ManagedEntity.Status} to {newStatus.@enum.ManagedEntity.Status} in {datacenter.name}
HostSyncFailedEvent Cannot synchronize host error Cannot synchronize host {host.name}. {reason.msg} Cannot synchronize host {host.name}. {reason.msg} Cannot synchronize host {host.name}. {reason.msg} Cannot synchronize host {host.name}. {reason.msg}
HostUpgradeFailedEvent Host upgrade failed error Cannot install or upgrade vCenter agent service on {host.name} Cannot install or upgrade vCenter agent service on {host.name} Cannot install or upgrade vCenter agent service on {host.name} in {datacenter.name} Cannot install or upgrade vCenter agent service on {host.name} in {datacenter.name}
HostUserWorldSwapNotEnabledEvent The userworld swap is not enabled on the host warning The userworld swap is not enabled on the host The userworld swap is not enabled on the host {host.name}
HostVnicConnectedToCustomizedDVPortEvent Some host vNICs were reconfigured to use dvPorts with port level configuration, which might be different from the dvPort group. info Host vNIC {vnic.vnic} was reconfigured to use dvPort {vnic.port.portKey} with port level configuration, which might be different from the dvPort group. Host {host.name} vNIC {vnic.vnic} was reconfigured to use dvPort {vnic.port.portKey} with port level configuration, which might be different from the dvPort group.
HostWwnChangedEvent Host WWN changed warning WWNs are changed WWNs are changed for {host.name}
HostWwnConflictEvent Host WWN conflict error The WWN ({wwn}) conflicts with the currently registered WWN The WWN ({wwn}) of {host.name} conflicts with the currently registered WWN
IncorrectHostInformationEvent Incorrect host information error Information needed to acquire the correct set of licenses not provided Host {host.name} did not provide the information needed to acquire the correct set of licenses
InfoUpgradeEvent Information upgrade info {message}
InsufficientFailoverResourcesEvent vSphere HA failover resources are insufficient error Insufficient resources to satisfy vSphere HA failover level on cluster {computeResource.name} Insufficient resources to satisfy vSphere HA failover level Insufficient resources to satisfy vSphere HA failover level on cluster {computeResource.name} in {datacenter.name}
InvalidEditionEvent Invalid edition error The license edition '{feature}' is invalid
IScsiBootFailureEvent Boot from iSCSI failed. warning Booting from iSCSI failed. Booting from iSCSI failed with an error. See the VMware Knowledge Base for information on configuring iBFT networking.
LicenseExpiredEvent License expired error License {feature.featureName} has expired
LicenseNonComplianceEvent Insufficient licenses. error License inventory is not compliant. Licenses are overused
LicenseRestrictedEvent Unable to acquire licenses due to a restriction on the license server error Unable to acquire licenses due to a restriction in the option file on the license server.
LicenseServerAvailableEvent License server available info License server {licenseServer} is available
LicenseServerUnavailableEvent License server unavailable error License server {licenseServer} is unavailable
LocalDatastoreCreatedEvent Local datastore created info Created local datastore {datastore.name} on {host.name} Created local datastore {datastore.name} on {host.name} Created local datastore {datastore.name} Created local datastore {datastore.name} on {host.name} in {datacenter.name}
LocalTSMEnabledEvent ESXi Shell is enabled info ESXi Shell for the host has been enabled ESXi Shell for the host {host.name} has been enabled
LockerMisconfiguredEvent Locker misconfigured warning Datastore {datastore} which is configured to back the locker does not exist
LockerReconfiguredEvent Locker reconfigured info Locker was reconfigured from {oldDatastore} to {newDatastore} datastore
MigrationErrorEvent Migration error error Unable to migrate {vm.name} from {host.name}: {fault.msg} Unable to migrate {vm.name}: {fault.msg} Unable to migrate {vm.name}: {fault.msg} Unable to migrate from {host.name}: {fault.msg} Unable to migrate {vm.name} from {host.name} in {datacenter.name}: {fault.msg}
MigrationHostErrorEvent Migration host error error Unable to migrate {vm.name} from {host.name} to {dstHost.name}: {fault.msg} Unable to migrate {vm.name} to host {dstHost.name}: {fault.msg} Unable to migrate {vm.name} to {dstHost.name}: {fault.msg} Unable to migrate from {host.name} to {dstHost.name}: {fault.msg} Unable to migrate {vm.name} from {host.name} to {dstHost.name} in {datacenter.name}: {fault.msg}
MigrationHostWarningEvent Migration host warning warning Migration of {vm.name} from {host.name} to {dstHost.name}: {fault.msg} Migration of {vm.name} to {dstHost.name}: {fault.msg} Migration of {vm.name} to {dstHost.name}: {fault.msg} Migration from {host.name} to {dstHost.name}: {fault.msg} Migration of {vm.name} from {host.name} to {dstHost.name} in {datacenter.name}: {fault.msg}
MigrationResourceErrorEvent Migration resource error error Unable to migrate {vm.name} from {host.name} to {dstHost.name} and resource pool {dstPool.name}: {fault.msg} Unable to migrate {vm.name} to {dstHost.name} and resource pool {dstPool.name}: {fault.msg} Unable to migrate {vm.name} to {dstHost.name} and resource pool {dstPool.name}: {fault.msg} Unable to migrate from {host.name} to {dstHost.name} and resource pool {dstPool.name}: {fault.msg} Cannot migrate {vm.name} from {host.name} to {dstHost.name} and resource pool {dstPool.name} in {datacenter.name}: {fault.msg}
MigrationResourceWarningEvent Migration resource warning warning Migration of {vm.name} from {host.name} to {dstHost.name} and resource pool {dstPool.name}: {fault.msg} Migration of {vm.name} to {dstHost.name} and resource pool {dstPool.name}: {fault.msg} Migration of {vm.name} to {dstHost.name} and resource pool {dstPool.name}: {fault.msg} Migration from {host.name} to {dstHost.name} and resource pool {dstPool.name}: {fault.msg} Migration of {vm.name} from {host.name} to {dstHost.name} and resource pool {dstPool.name} in {datacenter.name}: {fault.msg}
MigrationWarningEvent Migration warning warning Migration of {vm.name} from {host.name}: {fault.msg} Migration of {vm.name}: {fault.msg} Migration of {vm.name}: {fault.msg} Migration from {host.name}: {fault.msg} Migration of {vm.name} from {host.name} in {datacenter.name}: {fault.msg}
MtuMatchEvent The MTU configured in the vSphere Distributed Switch matches the physical switch connected to the physical NIC. info The MTU configured in the vSphere Distributed Switch matches the physical switch connected to uplink port {healthResult.uplinkPortKey} in vSphere Distributed Switch {dvs.name} on host {host.name} The MTU configured in the vSphere Distributed Switch matches the physical switch connected to uplink port {healthResult.uplinkPortKey} in vSphere Distributed Switch {dvs.name} The MTU configured in the vSphere Distributed Switch matches the physical switch connected to uplink port {healthResult.uplinkPortKey} in vSphere Distributed Switch {dvs.name} on host {host.name} in {datacenter.name}
MtuMismatchEvent The MTU configured in the vSphere Distributed Switch does not match the physical switch connected to the physical NIC. error The MTU configured in the vSphere Distributed Switch does not match the physical switch connected to uplink port {healthResult.uplinkPortKey} in vSphere Distributed Switch {dvs.name} on host {host.name} The MTU configured in the vSphere Distributed Switch does not match the physical switch connected to uplink port {healthResult.uplinkPortKey} in vSphere Distributed Switch {dvs.name} The MTU configured in the vSphere Distributed Switch does not match the physical switch connected to uplink port {healthResult.uplinkPortKey} in vSphere Distributed Switch {dvs.name} on host {host.name} in {datacenter.name}
NASDatastoreCreatedEvent NAS datastore created info Created NAS datastore {datastore.name} on {host.name} Created NAS datastore {datastore.name} on {host.name} Created NAS datastore {datastore.name} Created NAS datastore {datastore.name} on {host.name} in {datacenter.name}
NetworkRollbackEvent Network configuration on the host {host.name} is rolled back as it disconnects the host from vCenter server. error Network configuration on the host {host.name} is rolled back as it disconnects the host from vCenter server. Network configuration on the host {host.name} is rolled back as it disconnects the host from vCenter server. Network configuration on the host {host.name} is rolled back as it disconnects the host from vCenter server. Network configuration on the host {host.name} is rolled back as it disconnects the host from vCenter server.
NoAccessUserEvent No access for user error Cannot login user {userName}@{ipAddress}: no permission
NoDatastoresConfiguredEvent No datastores configured info No datastores have been configured No datastores have been configured on the host {host.name}
NoLicenseEvent No license error A required license {feature.featureName} is not reserved
NoMaintenanceModeDrsRecommendationForVM No maintenance mode DRS recommendation for the VM info Unable to automatically migrate {vm.name} Unable to automatically migrate from {host.name} Unable to automatically migrate {vm.name} from {host.name}
NonVIWorkloadDetectedOnDatastoreEvent Unmanaged workload detected on SIOC-enabled datastore info An unmanaged I/O workload is detected on a SIOC-enabled datastore: {datastore.name}. An unmanaged I/O workload is detected on a SIOC-enabled datastore: {datastore.name}. An unmanaged I/O workload is detected on a SIOC-enabled datastore: {datastore.name}. An unmanaged I/O workload is detected on a SIOC-enabled datastore: {datastore.name}. An unmanaged I/O workload is detected on a SIOC-enabled datastore: {datastore.name}.
NotEnoughResourcesToStartVmEvent Insufficient resources for vSphere HA to start the VM. Reason: {reason.@enum.fdm.placementFault} warning Insufficient resources to fail over {vm.name} in {computeResource.name}. vSphere HA will retry the fail over when enough resources are available. Reason: {reason.@enum.fdm.placementFault} Insufficient resources to fail over {vm.name}. vSphere HA will retry the fail over when enough resources are available. Reason: {reason.@enum.fdm.placementFault} Insufficient resources to fail over {vm.name}. vSphere HA will retry the fail over when enought resources are available. Reason: {reason.@enum.fdm.placementFault} Insufficient resources to fail over this virtual machine. vSphere HA will retry the fail over when enough resources are available. Reason: {reason.@enum.fdm.placementFault} Insufficient resources to fail over {vm.name} in {computeResource.name} that recides in {datacenter.name}. vSphere HA will retry the fail over when enough resources are available. Reason: {reason.@enum.fdm.placementFault}
OutOfSyncDvsHost The vSphere Distributed Switch configuration on some hosts differed from that of the vCenter Server. warning The vSphere Distributed Switch configuration on some hosts differed from that of the vCenter Server. The vSphere Distributed Switch configuration on some hosts differed from that of the vCenter Server.
PermissionAddedEvent Permission added info Permission created for {principal} on {entity.name}, role is {role.name}, propagation is {propagate.@enum.auth.Permission.propagate}
PermissionRemovedEvent Permission removed info Permission rule removed for {principal} on {entity.name}
PermissionUpdatedEvent Permission updated info Permission changed for {principal} on {entity.name}, role is {role.name}, propagation is {propagate.@enum.auth.Permission.propagate}
ProfileAssociatedEvent Profile attached to host info Profile {profile.name} has been attached. Profile {profile.name} has been attached. Profile {profile.name} has been attached with the host. Profile {profile.name} attached.
ProfileChangedEvent Profile was changed info Profile {profile.name} was changed. Profile {profile.name} was changed. Profile {profile.name} was changed. Profile {profile.name} was changed.
ProfileCreatedEvent Profile created info Profile is created.
ProfileDissociatedEvent Profile detached from host info Profile {profile.name} has been detached. Profile {profile.name} has been detached. Profile {profile.name} has been detached from the host. Profile {profile.name} detached.
ProfileReferenceHostChangedEvent The profile reference host was changed info The profile {profile.name} reference host was changed to {referenceHost.name}. The profile {profile.name} reference host was changed to {referenceHost.name}. The profile {profile.name} reference host was changed to {referenceHost.name}. Profile {profile.name} reference host changed.
ProfileRemovedEvent Profile removed info Profile {profile.name} was removed. Profile {profile.name} was removed. Profile was removed.
RecoveryEvent Recovery completed on the host. info The host {hostName} network connectivity was recovered on the virtual management NIC {vnic}. A new port {portKey} was created on vSphere Distributed Switch {dvsUuid}. The host {hostName} network connectivity was recovered on the virtual management NIC {vnic}. A new port {portKey} was created on vSphere Distributed Switch {dvsUuid}. The host {hostName} network connectivity was recovered on the management virtual NIC {vnic} by connecting to a new port {portKey} on the vSphere Distributed Switch {dvsUuid}.
RemoteTSMEnabledEvent SSH is enabled info SSH for the host has been enabled SSH for the host {host.name} has been enabled
ResourcePoolCreatedEvent Resource pool created info Created resource pool {resourcePool.name} in compute-resource {computeResource.name} Created resource pool {resourcePool.name} Created resource pool {resourcePool.name} in compute-resource {computeResource.name} in {datacenter.name}
ResourcePoolDestroyedEvent Resource pool deleted info Removed resource pool {resourcePool.name} on {computeResource.name} Removed resource pool {resourcePool.name} Removed resource pool {resourcePool.name} on {computeResource.name} in {datacenter.name}
ResourcePoolMovedEvent Resource pool moved info Moved resource pool {resourcePool.name} from {oldParent.name} to {newParent.name} on {computeResource.name} Moved resource pool {resourcePool.name} from {oldParent.name} to {newParent.name} Moved resource pool {resourcePool.name} from {oldParent.name} to {newParent.name} on {computeResource.name} in {datacenter.name}
ResourcePoolReconfiguredEvent Resource pool reconfigured info Updated configuration for {resourcePool.name} in compute-resource {computeResource.name} Updated configuration on {resourcePool.name} Updated configuration for {resourcePool.name} in compute-resource {computeResource.name} in {datacenter.name}
ResourceViolatedEvent Resource usage exceeds configuration error Resource usage exceeds configuration for resource pool {resourcePool.name} in compute-resource {computeResource.name}' Resource usage exceeds configuration on resource pool {resourcePool.name} Resource usage exceeds configuration for resource pool {resourcePool.name} in compute-resource {computeResource.name} in {datacenter.name}
RoleAddedEvent Role added info New role {role.name} created
RoleRemovedEvent Role removed info Role {role.name} removed
RoleUpdatedEvent Role updated info Modified role {role.name}
RollbackEvent Host Network operation rolled back info The Network API {methodName} on this entity caused the host {hostName} to be disconnected from the vCenter Server. The configuration change was rolled back on the host. The operation {methodName} on the host {hostName} disconnected the host and was rolled back . The Network API {methodName} on this entity caused the host {hostName} to be disconnected from the vCenter Server. The configuration change was rolled back on the host.
ScheduledTaskCompletedEvent Scheduled task completed info Task {scheduledTask.name} on {entity.name} completed successfully Task {scheduledTask.name} on {entity.name} completed successfully Task {scheduledTask.name} on {entity.name} completed successfully Task {scheduledTask.name} completed successfully Task {scheduledTask.name} on {entity.name} in datacenter {datacenter.name} completed successfully
ScheduledTaskCreatedEvent Scheduled task created info Created task {scheduledTask.name} on {entity.name} Created task {scheduledTask.name} on {entity.name} Created task {scheduledTask.name} on {entity.name} Created task {scheduledTask.name} Created task {scheduledTask.name} on {entity.name} in datacenter {datacenter.name}
ScheduledTaskEmailCompletedEvent Sent scheduled task email info Task {scheduledTask.name} on {entity.name} sent email to {to} Task {scheduledTask.name} on {entity.name} sent email to {to} Task {scheduledTask.name} on {entity.name} sent email to {to} Task {scheduledTask.name} on {entity.name} sent email to {to} Task {scheduledTask.name} on {entity.name} in datacenter {datacenter.name} sent email to {to}
ScheduledTaskEmailFailedEvent Scheduled task email not sent error Task {scheduledTask.name} on {entity.name} cannot send email to {to}: {reason.msg} Task {scheduledTask.name} on {entity.name} cannot send email to {to}: {reason.msg} Task {scheduledTask.name} on {entity.name} cannot send email to {to}: {reason.msg} Task {scheduledTask.name} cannot send email to {to}: {reason.msg} Task {scheduledTask.name} on {entity.name} in datacenter {datacenter.name} cannot send email to {to}: {reason.msg}
ScheduledTaskFailedEvent Cannot complete scheduled task error Task {scheduledTask.name} on {entity.name} cannot be completed: {reason.msg} Task {scheduledTask.name} on {entity.name} cannot be completed: {reason.msg} Task {scheduledTask.name} on {entity.name} cannot be completed: {reason.msg} Task {scheduledTask.name} cannot be completed: {reason.msg} Task {scheduledTask.name} on {entity.name} in datacenter {datacenter.name} cannot be completed: {reason.msg}
ScheduledTaskReconfiguredEvent Scheduled task reconfigured info Reconfigured task {scheduledTask.name} on {entity.name} Reconfigured task {scheduledTask.name} on {entity.name} Reconfigured task {scheduledTask.name} on {entity.name} Reconfigured task {scheduledTask.name} Reconfigured task {scheduledTask.name} on {entity.name} in datacenter {datacenter.name}
ScheduledTaskRemovedEvent Scheduled task removed info Removed task {scheduledTask.name} on {entity.name} Removed task {scheduledTask.name} on {entity.name} Removed task {scheduledTask.name} on {entity.name} Removed task {scheduledTask.name} Removed task {scheduledTask.name} on {entity.name} in datacenter {datacenter.name}
ScheduledTaskStartedEvent Scheduled task started info Running task {scheduledTask.name} on {entity.name} Running task {scheduledTask.name} on {entity.name} Running task {scheduledTask.name} on {entity.name} Running task {scheduledTask.name} Running task {scheduledTask.name} on {entity.name} in datacenter {datacenter.name}
ServerLicenseExpiredEvent Server license expired error A vCenter Server license has expired
ServerStartedSessionEvent Server started session info vCenter started
SessionTerminatedEvent Session stopped info A session for user '{terminatedUsername}' has stopped
TaskEvent Task event info Task: {info.descriptionId}
TaskTimeoutEvent Task time-out info Task: {info.descriptionId} time-out
TeamingMatchEvent Teaming configuration in the vSphere Distributed Switch matches the physical switch configuration info Teaming configuration in the vSphere Distributed Switch {dvs.name} on host {host.name} matches the physical switch configuration. Detail: {healthResult.summary.@enum.dvs.VmwareDistributedVirtualSwitch.TeamingMatchStatus} Teaming configuration in the vSphere Distributed Switch {dvs.name} matches the physical switch configuration. Detail: {healthResult.summary.@enum.dvs.VmwareDistributedVirtualSwitch.TeamingMatchStatus} Teaming configuration in the vSphere Distributed Switch {dvs.name} on host {host.name} matches the physical switch configuration in {datacenter.name}. Detail: {healthResult.summary.@enum.dvs.VmwareDistributedVirtualSwitch.TeamingMatchStatus}
TeamingMisMatchEvent Teaming configuration in the vSphere Distributed Switch does not match the physical switch configuration error Teaming configuration in the vSphere Distributed Switch {dvs.name} on host {host.name} does not match the physical switch configuration. Detail: {healthResult.summary.@enum.dvs.VmwareDistributedVirtualSwitch.TeamingMatchStatus} Teaming configuration in the vSphere Distributed Switch {dvs.name} does not match the physical switch configuration. Detail: {healthResult.summary.@enum.dvs.VmwareDistributedVirtualSwitch.TeamingMatchStatus} Teaming configuration in the vSphere Distributed Switch {dvs.name} on host {host.name} does not match the physical switch configuration in {datacenter.name}. Detail: {healthResult.summary.@enum.dvs.VmwareDistributedVirtualSwitch.TeamingMatchStatus}
TemplateBeingUpgradedEvent Upgrading template info Upgrading template {legacyTemplate}
TemplateUpgradedEvent Template upgraded info Template {legacyTemplate} upgrade completed
TemplateUpgradeFailedEvent Cannot upgrade template info Cannot upgrade template {legacyTemplate} due to: {reason.msg}
TimedOutHostOperationEvent Host operation timed out warning The operation performed on host {host.name} timed out The operation performed on host {host.name} timed out The operation timed out The operation performed on {host.name} in {datacenter.name} timed out
UnlicensedVirtualMachinesEvent Unlicensed virtual machines info There are {unlicensed} unlicensed virtual machines on host {host} - there are only {available} licenses available
UnlicensedVirtualMachinesFoundEvent Unlicensed virtual machines found info {unlicensed} unlicensed virtual machines found on host {host}
UpdatedAgentBeingRestartedEvent Restarting updated agent info The agent is updated and will soon restart The agent on host {host.name} is updated and will soon restart
UplinkPortMtuNotSupportEvent Not all VLAN MTU settings on the external physical switch allow the vSphere Distributed Switch maximum MTU size packets to pass. error Not all VLAN MTU settings on the external physical switch allow the vSphere Distributed Switch maximum MTU size packets to pass on the uplink port {healthResult.uplinkPortKey} in vSphere Distributed Switch {dvs.name} on host {host.name}. Not all VLAN MTU settings on the external physical switch allow the vSphere Distributed Switch maximum MTU size packets to pass on the uplink port {healthResult.uplinkPortKey} in vSphere Distributed Switch {dvs.name}. Not all VLAN MTU settings on the external physical switch allow the vSphere Distributed Switch maximum MTU size packets to pass on the uplink port {healthResult.uplinkPortKey} in vSphere Distributed Switch {dvs.name} on host {host.name} in {datacenter.name}.
UplinkPortMtuSupportEvent All VLAN MTU settings on the external physical switch allow the vSphere Distributed Switch maximum MTU size packets to pass. info All VLAN MTU settings on the external physical switch allow the vSphere Distributed Switch maximum MTU size packets to pass on uplink port {healthResult.uplinkPortKey} in vSphere Distributed Switch {dvs.name} on host {host.name}. All VLAN MTU setting on the external physical switch allows the vSphere Distributed Switch max MTU size packets passing on uplink port {healthResult.uplinkPortKey} in vSphere Distributed Switch {dvs.name} All VLAN MTU settings on the external physical switch allow the vSphere Distributed Switch maximum MTU size packets to pass on the uplink port {healthResult.uplinkPortKey} in vSphere Distributed Switch {dvs.name} on host {host.name} in {datacenter.name}.
UplinkPortVlanTrunkedEvent The configured VLAN in the vSphere Distributed Switch was trunked by the physical switch. info The configured VLAN in the vSphere Distributed Switch was trunked by the physical switch connected to uplink port {healthResult.uplinkPortKey} in vSphere Distributed Switch {dvs.name} on host {host.name}. The configured VLAN in the vSphere Distributed Switch was trunked by the physical switch connected to uplink port {healthResult.uplinkPortKey} in vSphere Distributed Switch {dvs.name}. The configured VLAN in the vSphere Distributed Switch was trunked by the physical switch connected to uplink port {healthResult.uplinkPortKey} in vSphere Distributed Switch {dvs.name} on host {host.name} in {datacenter.name}.
UplinkPortVlanUntrunkedEvent Not all the configured VLANs in the vSphere Distributed Switch were trunked by the physical switch. error Not all the configured VLANs in the vSphere Distributed Switch were trunked by the physical switch connected to uplink port {healthResult.uplinkPortKey} in vSphere Distributed Switch {dvs.name} on host {host.name}. Not all the configured VLANs in the vSphere Distributed Switch were trunked by the physical switch connected to uplink port {healthResult.uplinkPortKey} in vSphere Distributed Switch {dvs.name}. Not all the configured VLANs in the vSphere Distributed Switch were trunked by the physical switch connected to uplink port {healthResult.uplinkPortKey} in vSphere Distributed Switch {dvs.name} on host {host.name} in {datacenter.name}.
UserAssignedToGroup User assigned to group info User {userLogin} was added to group {group}
UserLoginSessionEvent User login info User {userName}@{ipAddress} logged in as {userAgent}
UserLogoutSessionEvent User logout info User {userName}@{ipAddress} logged out (login time: {loginTime}, number of API invocations: {callCount}, user agent: {userAgent})
UserPasswordChanged User password changed info Password was changed for account {userLogin} Password was changed for account {userLogin} on host {host.name}
UserUnassignedFromGroup User removed from group info User {userLogin} removed from group {group}
UserUpgradeEvent User upgrade user {message}
VcAgentUninstalledEvent vCenter agent uninstalled info vCenter agent has been uninstalled from {host.name} vCenter agent has been uninstalled from {host.name} vCenter agent has been uninstalled vCenter agent has been uninstalled from {host.name} in {datacenter.name}
VcAgentUninstallFailedEvent Cannot uninstall vCenter agent error Cannot uninstall vCenter agent from {host.name}. {reason.@enum.fault.AgentInstallFailed.Reason} Cannot uninstall vCenter agent from {host.name}. {reason.@enum.fault.AgentInstallFailed.Reason} Cannot uninstall vCenter agent. {reason.@enum.fault.AgentInstallFailed.Reason} Cannot uninstall vCenter agent from {host.name} in {datacenter.name}. {reason.@enum.fault.AgentInstallFailed.Reason}
VcAgentUpgradedEvent vCenter agent upgraded info vCenter agent has been upgraded on {host.name} vCenter agent has been upgraded on {host.name} vCenter agent has been upgraded vCenter agent has been upgraded on {host.name} in {datacenter.name}
VcAgentUpgradeFailedEvent Cannot complete vCenter agent upgrade error Cannot upgrade vCenter agent on {host.name}. {reason.@enum.fault.AgentInstallFailed.Reason} Cannot upgrade vCenter agent on {host.name}. {reason.@enum.fault.AgentInstallFailed.Reason} Cannot upgrade vCenter agent. {reason.@enum.fault.AgentInstallFailed.Reason} Cannot upgrade vCenter agent on {host.name} in {datacenter.name}. {reason.@enum.fault.AgentInstallFailed.Reason}
VimAccountPasswordChangedEvent VIM account password changed info VIM account password changed VIM account password was changed on host {host.name}
VmAcquiredMksTicketEvent VM acquired MKS ticket info Remote console to {vm.name} on {host.name} has been opened Remote console to {vm.name} on {host.name} has been opened Remote console to {vm.name} has been opened Remote console has been opened for this virtual machine on {host.name} Remote console to {vm.name} on {host.name} in {datacenter.name} has been opened
VmAcquiredTicketEvent VM acquired ticket info A ticket for {vm.name} of type {ticketType.@enum.VirtualMachine.TicketType} has been acquired A ticket for {vm.name} of type {ticketType.@enum.VirtualMachine.TicketType} has been acquired A ticket for {vm.name} of type {ticketType.@enum.VirtualMachine.TicketType} has been acquired A ticket of type {ticketType.@enum.VirtualMachine.TicketType} has been acquired. A ticket for {vm.name} of type {ticketType.@enum.VirtualMachine.TicketType} on {host.name} in {datacenter.name} has been acquired
VmAutoRenameEvent VM auto rename info Invalid name for {vm.name} on {host.name}. Renamed from {oldName} to {newName} Invalid name for {vm.name} on {host.name}. Renamed from {oldName} to {newName} Invalid name for {vm.name}. Renamed from {oldName} to {newName} Conflicting or invalid virtual machine name detected. Renamed from {oldName} to {newName} Invalid name for {vm.name} on {host.name} in {datacenter.name}. Renamed from {oldName} to {newName}
VmBeingClonedEvent VM being cloned info Cloning {vm.name} on {host.name} to {destName} on {destHost.name} Cloning {vm.name} on {host.name} to {destName} on {destHost.name} Cloning {vm.name} to {destName} on {destHost.name} Being cloned to {destName} on {destHost.name} Cloning {vm.name} on host {host.name} in {datacenter.name} to {destName} on host {destHost.name}
VmBeingClonedNoFolderEvent VM being cloned to a vApp info Cloning {vm.name} on {host.name} to {destName} on {destHost.name} to a vApp Cloning {vm.name} on {host.name} to {destName} on {destHost.name} to a vApp Cloning {vm.name} to {destName} on {destHost.name} to a vApp Being cloned to {destName} on {destHost.name} to a vApp Cloning {vm.name} on host {host.name} in {datacenter.name} to {destName} on host {destHost.name} to a vApp
VmBeingCreatedEvent Creating VM info Creating {vm.name} on host {host.name} Creating {vm.name} on host {host.name} Creating {vm.name} Creating VM on host {host.name} Creating {vm.name} on host {host.name} in {datacenter.name}
VmBeingDeployedEvent Deploying VM info Deploying {vm.name} on host {host.name} from template {srcTemplate.name} Deploying {vm.name} on host {host.name} from template {srcTemplate.name} Deploying {vm.name} from template {srcTemplate.name} Deploying VM on host {host.name} from template {srcTemplate.name} Deploying {vm.name} on host {host.name} in {datacenter.name} from template {srcTemplate.name}
VmBeingHotMigratedEvent VM is hot migrating info Migrating {vm.name} from {host.name}, {ds.name} to {destHost.name}, {destDatastore.name} Migrating {vm.name} from {host.name}, {ds.name} to {destHost.name}, {destDatastore.name} Migrating {vm.name} from {ds.name} to {destHost.name}, {destDatastore.name} Migrating VM from {host.name}, {ds.name} to {destHost.name}, {destDatastore.name} Migrating {vm.name} from {host.name}, {ds.name} to {destHost.name}, {destDatastore.name} in {datacenter.name}
VmBeingMigratedEvent VM migrating info Relocating {vm.name} from {host.name}, {ds.name} to {destHost.name}, {destDatastore.name} Relocating {vm.name} from {host.name}, {ds.name} to {destHost.name}, {destDatastore.name} Relocating {vm.name} to {destHost.name} Relocating VM from {host.name} to {destHost.name} Relocating {vm.name} from {host.name}, {ds.name} in {datacenter.name} to {destHost.name}, {destDatastore.name} in {destDatacenter.name}
VmBeingRelocatedEvent VM relocating info Relocating {vm.name} from {host.name}, {ds.name} to {destHost.name}, {destDatastore.name} Relocating {vm.name} from {host.name}, {ds.name} to {destHost.name}, {desDatastore.name} Relocating {vm.name} from {ds.name} to {destHost.name}, {destDatastore.name} Relocating from {host.name}, {ds.name} to {destHost.name}, {destDatastore.name} Relocating {vm.name} in {datacenter.name} from {host.name}, {ds.name} to {destHost.name}, {destDatastore.name}
VmClonedEvent VM cloned info Clone of {sourceVm.name} completed
VmCloneFailedEvent Cannot complete VM clone error Cannot clone {vm.name}: {reason.msg}
VmConfigMissingEvent VM configuration missing info Configuration file for {vm.name} on {host.name} cannot be found Configuration file for {vm.name} on {host.name} cannot be found Configuration file for {vm.name} cannot be found Configuration file cannot be found Configuration file for {vm.name} on {host.name} in {datacenter.name} cannot be found
VmConnectedEvent VM connected info Host is connected Virtual machine {vm.name} is connected
VmCreatedEvent VM created info New virtual machine {vm.name} created on {host.name} New virtual machine {vm.name} created on {host.name} New virtual machine {vm.name} created Virtual machine created Created virtual machine {vm.name} on {host.name} in {datacenter.name}
VmDasBeingResetEvent vSphere HA is resetting VM info {vm.name} on {host.name} in cluster {computeResource.name} reset by vSphere HA. Reason: {reason.@enum.VmDasBeingResetEvent.ReasonCode} {vm.name} on {host.name} reset by vSphere HA. Reason: {reason.@enum.VmDasBeingResetEvent.ReasonCode}. {vm.name} reset by vSphere HA. Reason: {reason.@enum.VmDasBeingResetEvent.ReasonCode}. This virtual machine reset by vSphere HA. Reason: {reason.@enum.VmDasBeingResetEvent.ReasonCode}. {vm.name} on {host.name} in cluster {computeResource.name} in {datacenter.name} reset by vSphere HA. Reason: {reason.@enum.VmDasBeingResetEvent.ReasonCode}
VmDasBeingResetWithScreenshotEvent vSphere HA enabled VM reset with screenshot info {vm.name} on {host.name} in cluster {computeResource.name} reset by vSphere HA. Reason: {reason.@enum.VmDasBeingResetEvent.ReasonCode}. A screenshot is saved at {screenshotFilePath}. {vm.name} on {host.name} reset by vSphere HA. Reason: {reason.@enum.VmDasBeingResetEvent.ReasonCode}. A screenshot is saved at {screenshotFilePath}. {vm.name} reset by vSphere HA. Reason: {reason.@enum.VmDasBeingResetEvent.ReasonCode}. A screenshot is saved at {screenshotFilePath} This virtual machine reset by vSphere HA. Reason: {reason.@enum.VmDasBeingResetEvent.ReasonCode}. A screenshot is saved at {screenshotFilePath} {vm.name} on {host.name} in cluster {computeResource.name} in {datacenter.name} reset by vSphere HA. Reason: {reason.@enum.VmDasBeingResetEvent.ReasonCode}. A screenshot is saved at {screenshotFilePath}.
VmDasResetFailedEvent vSphere HA cannot reset VM warning vSphere HA cannot reset {vm.name} on {host.name} in cluster {computeResource.name} vSphere HA cannot reset {vm.name} on {host.name} vSphere HA cannot reset {vm.name} vSphere HA cannot reset this virtual machine vSphere HA cannot reset {vm.name} on {host.name} in cluster {computeResource.name} in {datacenter.name}
VmDasUpdateErrorEvent VM vSphere HA update error error Unable to update vSphere HA agents given the state of {vm.name}
VmDasUpdateOkEvent Completed VM DAS update info vSphere HA agents have been updated with the current state of the virtual machine
VmDateRolledBackEvent VM date rolled back error Disconnecting all hosts as the date of virtual machine {vm.name} has been rolled back
VmDeployedEvent VM deployed info Template {srcTemplate.name} deployed Template {srcTemplate.name} deployed on host {host.name}
VmDeployFailedEvent Cannot deploy VM error Cannot deploy template: {reason.msg}
VmDisconnectedEvent VM disconnected info {vm.name} on host {host.name} is disconnected {vm.name} on host {host.name} is disconnected {vm.name} is disconnected {host.name} is disconnected {vm.name} on host {host.name} in {datacenter.name} is disconnected
VmDiscoveredEvent VM discovered info Discovered {vm.name} on {host.name} Discovered {vm.name} on {host.name} Discovered {vm.name} Discovered on {host.name} Discovered {vm.name} on {host.name} in {datacenter.name}
VmDiskFailedEvent Cannot create VM disk error Cannot create virtual disk {disk}
VmDVPortEvent dvPort connected to VM changed status info dvPort connected to VM {vm.name} on {host.name} changed status dvPort connected to VM {vm.name} changed status dvPort connected to VM {vm.name} changed status dvPort changed status dvPort connected to VM {vm.name} on {host.name} in {datacenter.name} changed status
VmEmigratingEvent VM emigrating info Migrating {vm.name} off host {host.name} Migrating {vm.name} off host {host.name} Migrating {vm.name} off host Migrating off host {host.name} Migrating {vm.name} off host {host.name} in {datacenter.name}
VmEndRecordingEvent End a recording session info End a recording session End a recording session on {vm.name}
VmEndReplayingEvent End a replay session info End a replay session End a replay session on {vm.name}
VmFailedMigrateEvent Cannot migrate VM error Cannot migrate {vm.name} from {host.name}, {ds.name} to {destHost.name}, {destDatastore.name} Cannot migrate {vm.name} from {host.name}, {ds.name} to {destHost.name}, {destDatastore.name} Cannot migrate {vm.name} to {destHost.name}, {destDatastore.name} Cannot migrate to {destHost.name}, {destDatastore.name} Cannot migrate {vm.name} from {host.name}, {ds.name} to {destHost.name}, {destDatastore.name} in {datacenter.name}
VmFailedRelayoutEvent Cannot complete VM relayout. error Cannot complete relayout {vm.name} on {host.name}: {reason.msg} Cannot complete relayout {vm.name} on {host.name}: {reason.msg} Cannot complete relayout {vm.name}: {reason.msg} Cannot complete relayout for this virtual machine on {host.name}: {reason.msg} Cannot complete relayout {vm.name} on {host.name} in {datacenter.name}: {reason.msg}
VmFailedRelayoutOnVmfs2DatastoreEvent Cannot complete VM relayout on Vmfs2 datastore error Cannot complete relayout due to disks on a VMFS2 volume Cannot complete relayout for virtual machine {vm.name} which has disks on a VMFS2 volume.
VmFailedStartingSecondaryEvent vCenter cannot start the Fault Tolerance secondary VM error vCenter cannot start the Fault Tolerance secondary VM for {vm.name} on host {host.name} in cluster {computeResource.name}. Reason: {reason.@enum.VmFailedStartingSecondaryEvent.FailureReason} vCenter cannot start the Fault Tolerance secondary VM for {vm.name} on host {host.name}. Reason: {reason.@enum.VmFailedStartingSecondaryEvent.FailureReason} vCenter cannot start the Fault Tolerance secondary VM for {vm.name}. Reason: {reason.@enum.VmFailedStartingSecondaryEvent.FailureReason} vCenter cannot start the Fault Tolerance secondary VM. Reason: {reason.@enum.VmFailedStartingSecondaryEvent.FailureReason} vCenter cannot start the Fault Tolerance secondary VM for {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}. Reason: {reason.@enum.VmFailedStartingSecondaryEvent.FailureReason}
VmFailedToPowerOffEvent Cannot power off the VM. error Cannot power off {vm.name} on {host.name}. {reason.msg} Cannot power off {vm.name} on {host.name}. {reason.msg} Cannot power off {vm.name}. {reason.msg} Cannot power off: {reason.msg} Cannot power off {vm.name} on {host.name} in {datacenter.name}: {reason.msg}
VmFailedToPowerOnEvent Cannot power on the VM. error Cannot power on {vm.name} on {host.name}. {reason.msg} Cannot power on {vm.name} on {host.name}. {reason.msg} Cannot power on {vm.name}. {reason.msg} Cannot power on {vm.name} on {host.name}. {reason.msg} Cannot power on {vm.name} on {host.name} in {datacenter.name}. {reason.msg}
VmFailedToRebootGuestEvent VM cannot reboot the guest OS. error Cannot reboot Guest OS. {reason.msg} Cannot reboot Guest OS. {reason.msg} Cannot reboot Guest OS. {reason.msg} Cannot reboot Guest OS. {reason.msg} Cannot reboot the guest OS for {vm.name} on {host.name} in {datacenter.name}. {reason.msg}
VmFailedToResetEvent Cannot reset VM error Cannot suspend {vm.name} on {host.name}: {reason.msg} Cannot suspend {vm.name} on {host.name}: {reason.msg} Cannot suspend {vm.name}: {reason.msg} Cannot suspend {host.name}: {reason.msg} Cannot suspend {vm.name} on {host.name} in {datacenter.name}: {reason.msg}
VmFailedToShutdownGuestEvent Cannot shut down the guest OS error Cannot shut down the guest OS. {reason.msg} Cannot shut down the guest OS. {reason.msg} Cannot shut down the guest OS. {reason.msg} Cannot shut down the guest OS. {reason.msg} {vm.name} cannot shut down the guest OS on {host.name} in {datacenter.name}: {reason.msg}
VmFailedToStandbyGuestEvent VM cannot standby the guest OS error Cannot standby the guest OS. {reason.msg} Cannot standby the guest OS. {reason.msg} Cannot standby the guest OS. {reason.msg} Cannot standby the guest OS. {reason.msg} {vm.name} cannot standby the guest OS on {host.name} in {datacenter.name}: {reason.msg}
VmFailedToSuspendEvent Cannot suspend VM error Cannot suspend {vm.name} on {host.name}: {reason.msg} Cannot suspend {vm.name} on {host.name}: {reason.msg} Cannot suspend {vm.name}: {reason.msg} Cannot suspend {host.name}: {reason.msg} Cannot suspend {vm.name} on {host.name} in {datacenter.name}: {reason.msg}
VmFailedUpdatingSecondaryConfig vCenter cannot update the Fault Tolerance secondary VM configuration error vCenter cannot update the Fault Tolerance secondary VM configuration for {vm.name} on host {host.name} in cluster {computeResource.name} vCenter cannot update the Fault Tolerance secondary VM configuration for {vm.name} on host {host.name} vCenter cannot update the Fault Tolerance secondary VM configuration for {vm.name} vCenter cannot update the Fault Tolerance secondary VM configuration vCenter cannot update the Fault Tolerance secondary VM configuration for {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}
VmFailoverFailed vSphere HA virtual machine failover unsuccessful warning vSphere HA unsuccessfully failed over {vm.name} on {host.name} in cluster {computeResource.name}. vSphere HA will retry if the maximum number of attempts has not been exceeded. Reason: {reason.msg} vSphere HA unsuccessfully failed over {vm.name} on {host.name}. vSphere HA will retry if the maximum number of attempts has not been exceeded. Reason: {reason.msg} vSphere HA unsuccessfully failed over {vm.name}. vSphere HA will retry if the maximum number of attempts has not been exceeded. Reason: {reason.msg} vSphere HA unsuccessfully failed over this virtual machine. vSphere HA will retry if the maximum number of attempts has not been exceeded. Reason: {reason.msg} vSphere HA unsuccessfully failed over {vm.name} on {host.name} in cluster {computeResource.name} in {datacenter.name}. vSphere HA will retry if the maximum number of attempts has not been exceeded. Reason: {reason.msg}
VmFaultToleranceStateChangedEvent VM Fault Tolerance state changed info Fault Tolerance state of {vm.name} on host {host.name} in cluster {computeResource.name} changed from {oldState.@enum.VirtualMachine.FaultToleranceState} to {newState.@enum.VirtualMachine.FaultToleranceState} Fault Tolerance state on {vm.name} on host {host.name} changed from {oldState.@enum.VirtualMachine.FaultToleranceState} to {newState.@enum.VirtualMachine.FaultToleranceState} Fault Tolerance state of {vm.name} changed from {oldState.@enum.VirtualMachine.FaultToleranceState} to {newState.@enum.VirtualMachine.FaultToleranceState} Fault Tolerance state changed from {oldState.@enum.VirtualMachine.FaultToleranceState} to {newState.@enum.VirtualMachine.FaultToleranceState} Fault Tolerance state of {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name} changed from {oldState.@enum.VirtualMachine.FaultToleranceState} to {newState.@enum.VirtualMachine.FaultToleranceState}
VmFaultToleranceTurnedOffEvent VM Fault Tolerance turned off info Fault Tolerance protection has been turned off for {vm.name} on host {host.name} in cluster {computeResource.name} Fault Tolerance protection has been turned off for {vm.name} on host {host.name} Fault Tolerance protection has been turned off for {vm.name} Fault Tolerance protection has been turned off for this virtual machine Fault Tolerance protection has been turned off for {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}
VmFaultToleranceVmTerminatedEvent Fault Tolerance VM terminated info The Fault Tolerance VM {vm.name} on host {host.name} in cluster {computeResource.name} has been terminated. {reason.@enum.VmFaultToleranceVmTerminatedEvent.TerminateReason} The Fault Tolerance VM {vm.name} on host {host.name} has been terminated. {reason.@enum.VmFaultToleranceVmTerminatedEvent.TerminateReason} The Fault Tolerance VM {vm.name} has been terminated. {reason.@enum.VmFaultToleranceVmTerminatedEvent.TerminateReason} The Fault Tolerance VM has been terminated. {reason.@enum.VmFaultToleranceVmTerminatedEvent.TerminateReason} The Fault Tolerance VM {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name} has been terminated. {reason.@enum.VmFaultToleranceVmTerminatedEvent.TerminateReason}
VMFSDatastoreCreatedEvent VMFS datastore created info Created VMFS datastore {datastore.name} on {host.name} Created VMFS datastore {datastore.name} on {host.name} Created VMFS datastore {datastore.name} Created VMFS datastore {datastore.name} on {host.name} in {datacenter.name}
VMFSDatastoreExpandedEvent VMFS datastore expanded info Expanded VMFS datastore {datastore.name} on {host.name} Expanded VMFS datastore {datastore.name} on {host.name} Expanded VMFS datastore {datastore.name} Expanded VMFS datastore {datastore.name} on {host.name} in {datacenter.name}
VMFSDatastoreExtendedEvent VMFS datastore extended info Extended VMFS datastore {datastore.name} on {host.name} Extended VMFS datastore {datastore.name} on {host.name} Extended VMFS datastore {datastore.name} Extended VMFS datastore {datastore.name} on {host.name} in {datacenter.name}
VmGuestOSCrashedEvent Guest operating system crashed error {vm.name} on {host.name}: Guest operating system has crashed. {vm.name} on {host.name}: Guest operating system has crashed. {vm.name}: Guest operating system has crashed. This virtual machine's guest operating system has crashed. {vm.name} on {host.name}: Guest operating system has crashed.
VmGuestRebootEvent Guest reboot info Guest OS reboot for {vm.name} on {host.name} Guest OS reboot for {vm.name} on {host.name} Guest OS reboot for {vm.name} Guest OS reboot Guest OS reboot for {vm.name} on {host.name} in {datacenter.name}
VmGuestShutdownEvent Guest OS shut down info Guest OS shut down for {vm.name} on {host.name} Guest OS shut down for {vm.name} on {host.name} Guest OS shut down for {vm.name} Guest OS shut down Guest OS shut down for {vm.name} on {host.name} in {datacenter.name}
VmGuestStandbyEvent Guest standby info Guest OS standby for {vm.name} on {host.name} Guest OS standby for {vm.name} on {host.name} Guest OS standby for {vm.name} Guest OS standby Guest OS standby for {vm.name} on {host.name} in {datacenter.name}
VmHealthMonitoringStateChangedEvent vSphere HA VM monitoring state changed info vSphere HA VM monitoring state in {computeResource.name} changed to {state.@enum.DasConfigInfo.VmMonitoringState} vSphere HA VM monitoring state changed to {state.@enum.DasConfigInfo.VmMonitoringState} vSphere HA VM monitoring state in {computeResource.name} in {datacenter.name} changed to {state.@enum.DasConfigInfo.VmMonitoringState}
VmInstanceUuidAssignedEvent Assign a new instance UUID info Assign a new instance UUID ({instanceUuid}) Assign a new instance UUID ({instanceUuid}) to {vm.name}
VmInstanceUuidChangedEvent Instance UUID Changed info The instance UUID has been changed from ({oldInstanceUuid}) to ({newInstanceUuid}) The instance UUID of {vm.name} has been changed from ({oldInstanceUuid}) to ({newInstanceUuid})
VmInstanceUuidConflictEvent Instance UUIDs conflict error The instance UUID ({instanceUuid}) conflicts with the instance UUID assigned to {conflictedVm.name} The instance UUID ({instanceUuid}) of {vm.name} conflicts with the instance UUID assigned to {conflictedVm.name}
VmMacAssignedEvent VM MAC assigned info New MAC address ({mac}) assigned to adapter {adapter} New MAC address ({mac}) assigned to adapter {adapter} for {vm.name}
VmMacChangedEvent VM MAC changed warning Changed MAC address from {oldMac} to {newMac} for adapter {adapter} Changed MAC address from {oldMac} to {newMac} for adapter {adapter} for {vm.name}
VmMacConflictEvent VM MAC conflict error The MAC address ({mac}) conflicts with MAC assigned to {conflictedVm.name} The MAC address ({mac}) of {vm.name} conflicts with MAC assigned to {conflictedVm.name}
VmMaxFTRestartCountReached vSphere HA reached maximum Secondary VM restart count. warning vSphere HA stopped trying to restart Secondary VM {vm.name} on {host.name} in cluster {computeResource.name} because the maximum VM restart count was reached vSphere HA stopped trying to restart Secondary VM {vm.name} on {host.name} because the maximum VM restart count was reached vSphere HA stopped trying to restart Secondary VM {vm.name} because the maximum VM restart count was reached vSphere HA stopped trying to restart Secondary VM because the maximum VM restart count was reached vSphere HA stopped trying to restart Secondary VM {vm.name} on {host.name} in cluster {computeResource.name} in {datacenter.name} because the maximum VM restart count was reached
VmMaxRestartCountReached vSphere HA reached maximum VM restart count warning vSphere HA stopped trying to restart {vm.name} on {host.name} in cluster {computeResource.name}because the maximum VM restart count was reached vSphere HA stopped trying to restart {vm.name} on {host.name} because the maximum VM restart count was reached vSphere HA stopped trying to restart {vm.name} because the maximum VM restart count was reached vSphere HA stopped trying to restart this VM because the maximum VM restart count was reached vSphere HA stopped trying to restart {vm.name} on {host.name} in cluster {computeResource.name} in {datacenter.name} because the maximum VM restart count was reached
VmMessageErrorEvent VM error message error Error message on {vm.name} on {host.name}: {message} Error message on {vm.name} on {host.name}: {message} Error message on {vm.name}: {message} Error message from {host.name}: {message} Error message on {vm.name} on {host.name} in {datacenter.name}: {message}
VmMessageEvent VM information message info Message on {vm.name} on {host.name}: {message} Message on {vm.name} on {host.name}: {message} Message on {vm.name}: {message} Message from {host.name}: {message} Message on {vm.name} on {host.name} in {datacenter.name}: {message}
VmMessageWarningEvent VM warning message warning Warning message on {vm.name} on {host.name}: {message} Warning message on {vm.name} on {host.name}: {message} Warning message on {vm.name}: {message} Warning message from {host.name}: {message} Warning message on {vm.name} on {host.name} in {datacenter.name}: {message}
VmMigratedEvent VM migrated info Migration of virtual machine {vm.name} from host {sourceHost.name}, {sourceDatastore.name} completed Migration from host {sourceHost.name}, {sourceDatastore.name} completed Migration of virtual machine {vm.name} from {sourceHost.name}, {sourceDatastore.name} to {host.name}, {ds.name} completed
VmNoCompatibleHostForSecondaryEvent No compatible host for the Fault Tolerance secondary VM error No compatible host for the Fault Tolerance secondary VM {vm.name} on host {host.name} in cluster {computeResource.name} No compatible host for the Fault Tolerance secondary VM {vm.name} on host {host.name} No compatible host for the Fault Tolerance secondary VM {vm.name} No compatible host for the Fault Tolerance secondary VM No compatible host for the Fault Tolerance secondary VM {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}
VmNoNetworkAccessEvent VM No Network Access warning Not all networks are accessible by {destHost.name} Not all networks for {vm.name} are accessible by {destHost.name}
VmOrphanedEvent VM orphaned warning {vm.name} does not exist on {host.name} {vm.name} does not exist on {host.name} {vm.name} does not exist Virtual machine does not exist on {host.name} {vm.name} does not exist on {host.name} in {datacenter.name}
VMotionLicenseExpiredEvent vMotion license expired error A vMotion license for {host.name} has expired
VmPoweredOffEvent VM powered off info {vm.name} on {host.name} is powered off {vm.name} on {host.name} is powered off {vm.name} is powered off Virtual machine on {host.name} is powered off {vm.name} on {host.name} in {datacenter.name} is powered off
VmPoweredOnEvent VM powered on info {vm.name} on {host.name} is powered on {vm.name} on {host.name} is powered on {vm.name} is powered on Virtual machine on {host.name} is powered on {vm.name} on {host.name} in {datacenter.name} is powered on
VmPoweringOnWithCustomizedDVPortEvent Virtual machine powered on with vNICs connected to dvPorts that have a port level configuration, which might be different from the dvPort group configuration. info Virtual machine powered On with vNICs connected to dvPorts that have a port level configuration, which might be different from the dvPort group configuration. Virtual machine {vm.name} powered On with vNICs connected to dvPorts that have a port level configuration, which might be different from the dvPort group configuration.
VmPowerOffOnIsolationEvent vSphere HA powered off VM on isolated host info vSphere HA powered off {vm.name} on the isolated host {isolatedHost.name} in cluster {computeResource.name} vSphere HA powered off {vm.name} on the isolated host {isolatedHost.name} vSphere HA powered off {vm.name} on the isolated host {isolatedHost.name} vSphere HA powered off this virtual machine on the isolated host {isolatedHost.name} vSphere HA powered off {vm.name} on the isolated host {isolatedHost.name} in cluster {computeResource.name} in {datacenter.name}
VmPrimaryFailoverEvent Fault Tolerance VM failover error Fault Tolerance VM ({vm.name}) failed over to {host.name} in cluster {computeResource.name}. {reason.@enum.VirtualMachine.NeedSecondaryReason} Fault Tolerance VM ({vm.name}) failed over to {host.name}. {reason.@enum.VirtualMachine.NeedSecondaryReason} Fault Tolerance VM ({vm.name}) failed over to {host.name}. {reason.@enum.VirtualMachine.NeedSecondaryReason} Fault Tolerance VM failed over to {host.name}. {reason.@enum.VirtualMachine.NeedSecondaryReason} Fault Tolerance VM ({vm.name}) failed over to {host.name} in cluster {computeResource.name} in {datacenter.name}. {reason.@enum.VirtualMachine.NeedSecondaryReason}
VmReconfiguredEvent VM reconfigured info Reconfigured {vm.name} on {host.name} Reconfigured {vm.name} on {host.name} Reconfigured {vm.name} Reconfigured virtual machine Reconfigured {vm.name} on {host.name} in {datacenter.name}
VmRegisteredEvent VM registered info Registered {vm.name} on {host.name} Registered {vm.name} on {host.name} Registered {vm.name} Registered with vCenter Registered {vm.name} on {host.name} in {datacenter.name}
VmRelayoutSuccessfulEvent VM relayout completed info Relayout of {vm.name} on {host.name} completed Relayout of {vm.name} on {host.name} completed Relayout of {vm.name} completed Relayout of the virtual machine completed Relayout of {vm.name} on {host.name} in {datacenter.name} completed
VmRelayoutUpToDateEvent VM relayout up-to-date info {vm.name} on {host.name} is in the correct format and relayout is not neccessary {vm.name} on {host.name} is in the correct format and relayout is not neccessary {vm.name} is in the correct format and relayout is not neccessary In the correct format and relayout is not neccessary {vm.name} on {host.name} in {datacenter.name} is in the correct format and relayout is not necessary
VmReloadFromPathEvent Virtual machine reloaded from path info {vm.name} on {host.name} reloaded from new configuration {configPath}. {vm.name} on {host.name} reloaded from new configuration {configPath}. {vm.name} reloaded from new configuration {configPath}. Virtual machine reloaded from new configuration {configPath}. {vm.name} on {host.name} reloaded from new configuration {configPath}.
VmReloadFromPathFailedEvent Virtual machine not reloaded from path error {vm.name} on {host.name} could not be reloaded from {configPath}. {vm.name} on {host.name} could not be reloaded from path {configPath}. {vm.name} could not be reloaded from {configPath}. This virtual machine could not be reloaded from {configPath}. {vm.name} on {host.name} could not be reloaded from {configPath}.
VmRelocatedEvent VM relocated info Completed the relocation of the virtual machine
VmRelocateFailedEvent Cannot relocate VM error Cannot relocate virtual machine Cannot relocate virtual machine '{vm.name}' in {datacenter.name}
VmRemoteConsoleConnectedEvent VM remote console connected info Remote console connected to {vm.name} on host {host.name} Remote console connected to {vm.name} on host {host.name} Remote console connected to {vm.name} Remote console connected Remote console connected to {vm.name} on host {host.name}
VmRemoteConsoleDisconnectedEvent VM remote console disconnected info Remote console disconnected from {vm.name} on host {host.name} Remote console disconnected from {vm.name} on host {host.name} Remote console disconnected from {vm.name} Remote console connected Remote console disconnected from {vm.name} on host {host.name}
VmRemovedEvent VM removed info Removed {vm.name} on {host.name} Removed {vm.name} on {host.name} Removed {vm.name} Removed Removed {vm.name} on {host.name} from {datacenter.name}
VmRenamedEvent VM renamed warning Renamed {vm.name} from {oldName} to {newName} Renamed {vm.name} from {oldName} to {newName} Renamed {vm.name} from {oldName} to {newName} Renamed from {oldName} to {newName} Renamed {vm.name} from {oldName} to {newName} in {datacenter.name}
VmRequirementsExceedCurrentEVCModeEvent Virtual machine is using features that exceed the capabilities of the host's current EVC mode. warning Feature requirements of {vm.name} exceed capabilities of {host.name}'s current EVC mode. Feature requirements of {vm.name} exceed capabilities of {host.name}'s current EVC mode. Feature requirements of {vm.name} exceed capabilities of this host's current EVC mode. Feature requirements of this virtual machine exceed capabilities of this host's current EVC mode. Feature requirements of {vm.name} exceed capabilities of {host.name}'s current EVC mode.
VmResettingEvent VM resetting info {vm.name} on {host.name} is reset {vm.name} on {host.name} is reset {vm.name} is reset Virtual machine on {host.name} is reset {vm.name} on {host.name} in {datacenter.name} is reset
VmResourcePoolMovedEvent VM resource pool moved info Moved {vm.name} from resource pool {oldParent.name} to {newParent.name} Moved {vm.name} from resource pool {oldParent.name} Moved {vm.name} from resource pool {oldParent.name} to {newParent.name} Moved from resource pool {oldParent.name} to {newParent.name} Moved {vm.name} from resource pool {oldParent.name} to {newParent.name} in {datacenter.name}
VmResourceReallocatedEvent VM resource reallocated info Resource allocation changed Changed resource allocation for {vm.name}
VmRestartedOnAlternateHostEvent VM restarted on alternate host info Virtual machine {vm.name} was restarted on this host since {sourceHost.name} failed Virtual machine was restarted on {host.name} since {sourceHost.name} failed Virtual machine {vm.name} was restarted on {host.name} since {sourceHost.name} failed
VmResumingEvent VM resuming info {vm.name} on {host.name} is resumed {vm.name} on {host.name} is resumed {vm.name} is resumed Virtual machine on {host.name} is resumed {vm.name} on {host.name} in {datacenter.name} is resumed
VmSecondaryAddedEvent Fault Tolerance secondary VM added info A Fault Tolerance secondary VM has been added for {vm.name} on host {host.name} in cluster {computeResource.name} A Fault Tolerance secondary VM has been added for {vm.name} on host {host.name} A Fault Tolerance secondary VM has been added for {vm.name} A Fault Tolerance secondary VM has been added for this VM A Fault Tolerance secondary VM has been added for {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}
VmSecondaryDisabledBySystemEvent vCenter disabled Fault Tolerance error vCenter disabled Fault Tolerance on VM {vm.name} on host {host.name} in cluster {computeResource.name} because the Secondary VM could not be powered On. vCenter disabled Fault Tolerance on VM {vm.name} on host {host.name} because the Secondary VM could not be powered On. vCenter disabled Fault Tolerance on VM {vm.name} because the Secondary VM could not be powered On. vCenter disabled Fault Tolerance because the Secondary VM could not be powered On. vCenter disabled Fault Tolerance on VM {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name} because the Secondary VM could not be powered On.
VmSecondaryDisabledEvent Disabled Fault Tolerance secondary VM info Disabled Fault Tolerance secondary VM for {vm.name} on host {host.name} in cluster {computeResource.name} Disabled Fault Tolerance secondary VM for {vm.name} on host {host.name} Disabled Fault Tolerance secondary VM for {vm.name} Disabled Fault Tolerance secondary VM for this virtual machine Disabled Fault Tolerance secondary VM for {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}
VmSecondaryEnabledEvent Enabled Fault Tolerance secondary VM info Enabled Fault Tolerance secondary VM for {vm.name} on host {host.name} in cluster {computeResource.name} Enabled Fault Tolerance secondary VM for {vm.name} on host {host.name} Enabled Fault Tolerance secondary VM for {vm.name} Enabled Fault Tolerance secondary VM for this VM Enabled Fault Tolerance secondary VM for {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}
VmSecondaryStartedEvent Started Fault Tolerance secondary VM info Started Fault Tolerance secondary VM for {vm.name} on host {host.name} in cluster {computeResource.name} Started Fault Tolerance secondary VM for {vm.name} on host {host.name} Started Fault Tolerance secondary VM for {vm.name} Started Fault Tolerance secondary VM for this virtual machine Started Fault Tolerance secondary VM for {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}
VmShutdownOnIsolationEvent vSphere HA shut down VM on isolated host info vSphere HA shut down {vm.name} on the isolated host {isolatedHost.name} in cluster {computeResource.name}: {shutdownResult.@enum.VmShutdownOnIsolationEvent.Operation} vSphere HA shut down {vm.name} on the isolated host {isolatedHost.name}: {shutdownResult.@enum.VmShutdownOnIsolationEvent.Operation} vSphere HA shut down {vm.name} on the isolated host {isolatedHost.name}: {shutdownResult.@enum.VmShutdownOnIsolationEvent.Operation} vSphere HA shut down this virtual machine on the isolated host {isolatedHost.name}: {shutdownResult.@enum.VmShutdownOnIsolationEvent.Operation} vSphere HA shut down {vm.name} was shut down on the isolated host {isolatedHost.name} in cluster {computeResource.name} in {datacenter.name}: {shutdownResult.@enum.VmShutdownOnIsolationEvent.Operation}
VmStartingEvent VM starting info {vm.name} on host {host.name} is starting {vm.name} on host {host.name} is starting {vm.name} is starting Virtual machine is starting {vm.name} on host {host.name} in {datacenter.name} is starting
VmStartingSecondaryEvent Starting Fault Tolerance secondary VM info Starting Fault Tolerance secondary VM for {vm.name} on host {host.name} in cluster {computeResource.name} Starting Fault Tolerance secondary VM for {vm.name} on host {host.name} in cluster Starting Fault Tolerance secondary VM for {vm.name} Starting Fault Tolerance secondary VM for this virtual machine Starting Fault Tolerance secondary VM for {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name}
VmStartRecordingEvent Start a recording session info Start a recording session Start a recording session on {vm.name}
VmStartReplayingEvent Start a replay session info Start a replay session Start a replay session on {vm.name}
VmStaticMacConflictEvent VM static MAC conflict error The static MAC address ({mac}) conflicts with MAC assigned to {conflictedVm.name} The static MAC address ({mac}) of {vm.name} conflicts with MAC assigned to {conflictedVm.name}
VmStoppingEvent VM stopping info {vm.name} on {host.name} is stopping {vm.name} on {host.name} is stopping {vm.name} is stopping Virtual machine is stopping {vm.name} on {host.name} in {datacenter.name} is stopping
VmSuspendedEvent VM suspended info {vm.name} on {host.name} is suspended {vm.name} on {host.name} is suspended {vm.name} is suspended Virtual machine is suspended {vm.name} on {host.name} in {datacenter.name} is suspended
VmSuspendingEvent VM being suspended info {vm.name} on {host.name} is being suspended {vm.name} on {host.name} is being suspended {vm.name} is being suspended Virtual machine is being suspended {vm.name} on {host.name} in {datacenter.name} is being suspended
VmTimedoutStartingSecondaryEvent Starting the Fault Tolerance secondary VM timed out error Starting the Fault Tolerance secondary VM {vm.name} on host {host.name} in cluster {computeResource.name} timed out within {timeout} ms Starting the Fault Tolerance secondary VM {vm.name} on host {host.name} timed out within {timeout} ms Starting the Fault Tolerance secondary VM {vm.name} timed out within {timeout} ms Starting the Fault Tolerance secondary VM timed out within {timeout} ms Starting the Fault Tolerance secondary VM {vm.name} on host {host.name} in cluster {computeResource.name} in {datacenter.name} timed out within {timeout} ms
VmUnsupportedStartingEvent VM unsupported guest OS is starting warning Unsupported guest OS {guestId} for {vm.name} Unsupported guest OS {guestId} for {vm.name} on {host.name} Unsupported guest OS {guestId} for {vm.name} on {host.name} in {datacenter.name} Unsupported guest OS {guestId} Unsupported guest OS {guestId} for {vm.name} on {host.name} in {datacenter.name}
VmUpgradeCompleteEvent VM upgrade complete info Virtual machine compatibility upgraded to {version.@enum.vm.hwVersion}
VmUpgradeFailedEvent Cannot upgrade VM error Cannot upgrade virtual machine compatibility.
VmUpgradingEvent Upgrading VM info Upgrading virtual machine compatibility of {vm.name} to {version.@enum.vm.hwVersion} Upgrading virtual machine compatibility of {vm.name} to {version.@enum.vm.hwVersion} Upgrading virtual machine compatibility of {vm.name} to {version.@enum.vm.hwVersion} Upgrading virtual machine compatibility to {version.@enum.vm.hwVersion} Upgrading virtual machine compatibility of {vm.name} in {datacenter.name} to {version.@enum.vm.hwVersion}
VmUuidAssignedEvent VM UUID assigned info Assigned new BIOS UUID ({uuid}) to {vm.name} on {host.name} Assigned new BIOS UUID ({uuid}) to {vm.name} on {host.name} Assigned new BIOS UUID ({uuid}) to {vm.name} Assigned new BIOS UUID ({uuid}) Assigned new BIOS UUID ({uuid}) to {vm.name} on {host.name} in {datacenter.name}
VmUuidChangedEvent VM UUID Changed warning Changed BIOS UUID from {oldUuid} to {newUuid} for {vm.name} on {host.name} Changed BIOS UUID from {oldUuid} to {newUuid} for {vm.name} on {host.name} Changed BIOS UUID from {oldUuid} to {newUuid} for {vm.name} BIOS UUID was changed from {oldUuid} to {newUuid} Changed BIOS UUID from {oldUuid} to {newUuid} for {vm.name} on {host.name} in {datacenter.name}
VmUuidConflictEvent VM UUID Conflict error BIOS ID ({uuid}) conflicts with that of {conflictedVm.name} BIOS ID ({uuid}) of {vm.name} conflicts with that of {conflictedVm.name}
VmVnicPoolReservationViolationClearEvent Virtual NIC Network Resource Pool Reservation Violation Clear event info The reservation violation on the virtual NIC network resource pool {vmVnicResourcePoolName} with key {vmVnicResourcePoolKey} on {dvs.name} is cleared The reservation violation on the virtual NIC network resource pool {vmVnicResourcePoolName} with key {vmVnicResourcePoolKey} on {dvs.name} is cleared
VmVnicPoolReservationViolationRaiseEvent Virtual NIC Network Resource Pool Reservation Violation event info The reservation allocated to the virtual NIC network resource pool {vmVnicResourcePoolName} with key {vmVnicResourcePoolKey} on {dvs.name} is violated The reservation allocated to the virtual NIC network resource pool {vmVnicResourcePoolName} with key {vmVnicResourcePoolKey} on {dvs.name} is violated
VmWwnAssignedEvent VM WWN assigned info New WWNs assigned New WWNs assigned to {vm.name}
VmWwnChangedEvent VM WWN changed warning WWNs are changed WWNs are changed for {vm.name}
VmWwnConflictEvent VM WWN conflict error The WWN ({wwn}) conflicts with the currently registered WWN The WWN ({wwn}) of {vm.name} conflicts with the currently registered WWN