---
title: "VmNoCompatibleHostForSecondaryEvent"
description: "This event records that no compatible host was found to place a secondary VM. A default alarm will be triggered upon this event, which by default will trigger a SNMP trap. No compatible host for the secondary VM."
canonical: "https://helpcenter.veeam.com/docs/mp/kb/vmnocompatiblehostforsecondaryevent_em.html"
breadcrumb: "Veeam MP for VMware Online Knowledge Base > vCenter Server Alarms > Veeam VMware: No Compatible Host for Secondary VM Alarm > VmNoCompatibleHostForSecondaryEvent"
dateModified: "2026-09-10"
---

# VmNoCompatibleHostForSecondaryEvent

## Summary

This event records that no compatible host was found to place a secondary VM. A default alarm will be triggered upon this event, which by default will trigger a SNMP trap.

## Causes

No compatible host for the secondary VM.

This can occur for a variety of reasons including that there are no other hosts in the cluster, there are no other hosts with HV enabled, data stores are inaccessible, there is no available capacity, or hosts are in maintenance mode.

## Resolutions

If there are not enough hosts, you can add more hosts to the cluster.

If there are enough hosts in the cluster, ensure the hosts support HV and that HV is enabled.

Check that the hosts have sufficient capacity and that the hosts are not in the maintenance mode.

See the [vSphere Availability Guide](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.avail.doc/GUID-63F459B7-8884-4818-8872-C9753B2E0215.html) for more information.

## External

Refer to the [VMware Online Documentation](https://techdocs.broadcom.com/) for more information.