"Module MonitorLoop Power On Failed" Error during VM Failover and Failback
KB ID: 105964
Issue:
The error message "Module Monitor-loop Power On Failed" appears in reports when attempting to power on a replicated Virtual Machine (VM) on the destination host after reverting a snapshot during failover. This error may also occur after performing a failback and trying to power on the Virtual Machine.
Cause:
The "Module Monitor-Loop Power On Failed" error is triggered due to the following reasons:
1. Insufficient Resources: VM replication involves copying the configuration from the Source VM to the target host. If the destination host has fewer resources, such as a lower number of cores or inadequate memory, compared to the Source VM, this issue may arise.2. Space Constraints: Another possible cause is the absence of sufficient space in the residing datastore of the Virtual Machine on the destination host.
Solution:
To resolve the "Module MonitorLoop Power On Failed" error, follow these steps:
1. Check Error Message:Review the vSphere client or web client for the specific error message, as it will indicate the resource causing the VM to fail to power on.2. Edit VM Settings:a) Manually edit the VM settings, adjusting the number of cores and memory as needed, to match the capabilities of the destination host.b) Try powering on the Virtual Machine again after making the necessary adjustments. This will enable the use of the replicated Virtual Machine temporarily until the next scheduled replication job.3. Contact Support:To retain the changes made during the VM failover and perform a failback, get in touch with BDRSuite Support for further assistance.
Note: It is essential to ensure that the destination host has sufficient resources and datastore space to accommodate the VM's configuration during failover and failback operations. Failure to do so may result in the recurrence of the "Module MonitorLoop Power On Failed" error.
Related Articles
Replica Failover and Failback
Sometimes businesses may require a substitute of the Virtual Machine that is being used for their business-critical function in times of disaster. In such cases, they will want to avoid downtime and have the VM in a ready-to-use format so that their ...Failover
If your primary server/VM has crashed due to a disaster, switch over to the replicated VM to continue with production. When your source machine is down, you can use the Failover process to switch the operations from the source VM to its replica in ...What is VM Failover and Failback?
Failover is the process of switching to a backup system or VM when the primary system fails. This ensures minimal downtime and continuity of services. Failback is the process of returning operations from the backup system to the primary system once ...Resolving 'Failed to Create VM' Error in BDRSuite
KB ID: 44 Issue: Instant boot encounters a failure with the error message "Failed to create VM," accompanied by "The application encountered an error while attempting to change the state of VMMachineName." This problem arises when BDRSuite is not ...VMware Module Exception - Failed with BDRSuite
KB ID: 105950 Issue: Encountering the error message: "Failed with VMware Module Exception." Cause: VMware backup/replication jobs configured under BDRSuite v3.6 may fail with the specified error due to the following reasons: The datacenter name under ...