vCenter has logged a warning event for this virtual machine. Additional Knowledge Base data is available using the links below. Click the relevant link for the [EventID] as seen in the alert description to search the Veeam MP Online Help Center for further troubleshooting assistance.
Additional events can be added to this rule using overrides; if the EventID is not in the list below, use the Help Center Search Page to locate the article for the event.
The rule is enabled by default. You can override the following parameters:
Name | Default Value | Description |
Include Events | Dummy.Event.Id.1 | Allows you to include one or several vCenter Server events for monitoring, in addition to events monitored by this rule. For the list of vCenter Server events, see Veeam MP Reference. To separate multiple event IDs, use pipes. |
Exclude Events | Dummy.Event.Id.3 | Allows you to exclude one or several vCenter Server events from monitoring. The list of events that can be excluded is provided in the 'Causes' section. To separate multiple event IDs, use pipes. |
Exclude Text | Insufficient video RAM | Allows you to suppress alerts that this event rule can raise, based on a keyword or text string from the alert description. For example, when an alert is triggered, the name of the affected object is inserted into the alert description. If you specify the name of the object in the override for this rule, the rule will not raise alerts for this object. |
Note: If you have configured several overrides of the same type, select the Enforced check box for an override that should have priority over all other overrides.
The event IDs and details are:
vCenter Event | Description |
VMware HA has been disabled in cluster {computeResource.name} of datacenter {datacenter.name}. HA will not restart VM {vm.name} or its secondary VM after a failure. | |
Guest operation authentication failed for operation {[email protected]} on Virtual machine {vm.name}. | |
Lock-lost question on virtual machine {vm.name} on host {host.name} in cluster {computeResource.name} was answered by vSphere HA. | |
vSphere HA answered a question from host {host.name} in cluster {computeResource.name} about terminating virtual machine {vm.name} | |
VM {vm.name} in cluster {computeResource.name} in {datacenter.name} failed to become vSphere HA Protected and vSphere HA may not attempt to restart it after a failure. | |
Virtual machine {vm.name} was restarted on host {host.name} in cluster {computeResource.name} by vSphere HA. Note: Monitoring of this event is disabled by default. | |
VM {vm.name} in cluster {computeResource.name} in {datacenter.name} is not vSphere HA Protected. | |
vSphere HA detected that the application state changed to {[email protected]} for {vm.name} on {host.name} in cluster {computeResource.name} in {datacenter.name}. | |
Application heartbeat failed for {vm.name} on {host.name} in cluster {computeResource.name} in {datacenter.name}. | |
{vm.name} on {host.name} in {datacenter.name} is violating a DRS VM-host affinity rule. | |
Issue detected for {vm.name} on {host.name} in {datacenter.name}: {message}. Note: Monitoring of this event is disabled by default. | |
{vm.name} on {host.name} in cluster {computeResource.name} in {datacenter.name} reset due to a guest OS error. Note: Monitoring of this event is disabled by default. | |
{vm.name} on {host.name} in cluster {computeResource.name} in {datacenter.name} reset due to a guest OS error. Screenshot is saved at {screenshotFilePath}. Note: Monitoring of this event is disabled by default. | |
Failover unsuccessful for {vm.name} on {host.name} in cluster {computeResource.name} in {datacenter.name}. Note: Monitoring of this event is disabled by default. | |
Reached maximum Secondary VM (with FT turned On) restart count for {vm.name} on {host.name} in cluster {computeResource.name} in {datacenter.name}. | |
Reached maximum VM restart count for {vm.name} on {host.name} in cluster {computeResource.name} in {datacenter.name}. | |
Warning message on {vm.name} on {host.name} in {datacenter.name}: {message}. | |
No compatible host for the secondary VM {vm.name}. Note: Monitoring of this event is disabled by default. | |
Not all networks for {vm.name} are accessible by {destHost.name}. | |
{vm.name} does not exist on {host.name} in {datacenter.name}. Note: Monitoring of this event is disabled by default. | |
Feature requirements of {vm.name} exceed capabilities of {host.name}'s current EVC mode. | |
Unsupported guest OS {guestId} for {vm.name} on {host.name} in {datacenter.name}. | |
WWNs are changed for {vm.name}. |
Resolution is dependent on the nature of the event. Use the EventID KB links above to search for more information.
Note that this rule will suppress multiple events, even those with different IDs, in order to prevent unnecessary multiple alerts. However all underlying events will be collected. Check the Repeat Count on this alert to understand if multiple events have been suppressed.
Use the Alerts View to see all current open issues for this object. Use the Events View to review any error and warning events for this object. Open a Performance View to see the performance metrics for this object and all contained objects. Open a Diagram View to analyze the relationships of this object to other components.
For further details on high-availability errors see the vSphere HA and FT Error Messages article.
See the Help Center for more information including reference lists of all Rules and Monitors and full set of User Guides for the Veeam MP for VMware.
See the VMware Online Documentation for more information on VMware vSphere, in particular:
| Target | Veeam.Virt.Extensions.VMware.VMGUEST | ||
| Category | EventCollection | ||
| Enabled | False | ||
| Alert Generate | True | ||
| Alert Severity | Warning | ||
| Alert Priority | High | ||
| Remotable | True | ||
| Alert Message |
|
| ID | Module Type | TypeId | RunAs |
|---|---|---|---|
| DS | DataSource | Veeam.Virt.Extensions.VMware.FilteredEventProvider | Default |
| Alert | WriteAction | System.Health.GenerateAlert | Default |
Home
<Rule ID="Veeam.Virt.Extensions.VMware.GroupEvents.VM.Warning" Enabled="false" Target="VeeamVEVMwareLib!Veeam.Virt.Extensions.VMware.VMGUEST" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">
<Category>EventCollection</Category>
<DataSources>
<DataSource ID="DS" TypeID="VeeamVEVMwareLib!Veeam.Virt.Extensions.VMware.FilteredEventProvider">
<Expression>
<And>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="Integer">EventLevel</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="Integer">2</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">Params/Param[8]</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">$Target/Property[Type="VeeamVEVMwareLib!Veeam.Virt.Extensions.VMware.VMGUEST"]/id$</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</Expression>
<EventGroup>VirtualMachine</EventGroup>
<IncludeEvents>Dummy.Event.Id.1|Dummy.Event.Id.2</IncludeEvents>
<ExcludeEvents>VmDasBeingResetEvent|VmDasBeingResetWithScreenshotEvent|VmNoCompatibleHostForSecondaryEvent|VmFailoverFailed|com.vmware.vc.ha.VmRestartedByHAEvent|VmOrphanedEvent|GeneralVmWarningEvent</ExcludeEvents>
<ExcludeText>Insufficient video RAM|DummyEventText2|DummyEventText3</ExcludeText>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="Alert" TypeID="SystemHealth!System.Health.GenerateAlert">
<Priority>2</Priority>
<Severity>1</Severity>
<AlertOwner/>
<AlertMessageId>$MPElement[Name="Veeam.Virt.Extensions.VMware.GroupEvents.VM.Warning.AlertMessage"]$</AlertMessageId>
<AlertParameters>
<AlertParameter1>[$Data/Params/Param[1]$] $Data/Params/Param[11]$</AlertParameter1>
</AlertParameters>
<Suppression>
<SuppressionValue>$Data/Params/Param[1]$</SuppressionValue>
</Suppression>
</WriteAction>
</WriteActions>
</Rule>