How to Solve Module monitorloop Power on Failed Problem?
There are instances when you switch on your VM and an error occurs, this type of error is nothing but a module MonitorLoop power failures problem. This article will help you to fix the module MonitorLoop power failure problem in very few steps.
List of content you will read in this article:
- 1. How to Solve Module ‘monitorloop’ Power on Failed Problem?
- 2. Reason
- 3. Solution
- 4. Final words
There are instances when you switch on your VM and an error occurs, this type of error is nothing but a module MonitorLoop power failures problem. This article will help you to fix the module MonitorLoop power failure problem in very few steps.
How to Solve Module ‘monitorloop’ Power on Failed Problem?
To start follow the below-listed steps:
First of all, if you receive this message on your screen, don’t worry, you have landed at the right place. Take a look.

Next, the details of this message are mentioned here:
Now, why does this happen? What is the prominent reason why such a failure occurs? Let us analyze.
Reason
Technically, the source Virtual Machine’s configuration is utilized by VM replication. The purpose is to replicate it completely like the target host. Now, this issue occurs when sometimes there are source resources with the destination host in comparison to the Source Virtual Machine.
You may wonder, what kind of resources! For instance, memory, storage, or the number of cores. Another prominent reason related to the failure is the availability of less storage space in the Virtual machine. Meaning, that when you want to use the MonitorLoop module, there should be enough space on your device to access it.
For more clarity, here is an example: Suppose, the source virtual machine imbibes more cores as compared to your destination host. Now, this factor surely creates an issue and leads to failure. Moving on, how can you fix the Module monitorloop Power on Failed error and continue working on the VM?
Solution
On witnessing the error message, head on to the vSphere client. It tells you about that particular resource that is responsible for the VM failure. Once you follow this step, your screen displays the following window. Have a look.

The next target is to make specific changes in the VM. Try to power on your system manually. This step assists you in temporarily utilising the replicated VM.
Final words
This was a quick and step-by-step guide to getting rid of your module MonitorLoop power failures problem error. We hope that this article helped you in the best way possible. If you have any kind of feedback related to this guide, let us know in the comments box listed below.
People Are Also Reading:

Nisal N
Computers has always fascinated me since I was a kid and here we are. I love travelling for 2 reasons: the first one to see a new part of the world and second (the most important one) to experience the rich culture hidden among the country and people. I'm pretty good at cooking but very poor when it comes to baking.
Module MonitorLoop power on failed error when powering on VM on vSphere
I was playing in the lab for our upcoming vSphere Clustering Deepdive book and I ran in to this error when powering on a VM. I had never seen it before myself, so I was kind of surprised when I figured out what it was referring to. The error message is the following:
Module MonitorLoop power on failed when powering on VM
Think about that for a second, if you have never seen it I bet you don’t know what it is about? Not strange as the message doesn’t give a clue.

f you go to the event however there’s a big clue right there, and that is that the swap file can’t be extended from 0KB to whatever it needs to be. In other words, you are probably running out of disk space on the device the VM is stored on. In this case I removed some obsolete VMs and then powered on the VM that had the issue without any problems. So if you see this “Module MonitorLoop power on failed when powering on VM” error, check your free capacity on the datastore the VM sits on!
More details: 
Strange error message, for a simple problem. Yes, I will file a request to get this changed.
Related
Reader Interactions
Comments
I got this same error when doing a PoC of VVOL using Hitachi’s VASA provider version 3.3.
It showed when doing lots of operations simultaneously.
The solution was to upgrade to 3.4 where Hitachi had changed the queuing mechanism.
So it seems like some sort of generic error msg..
Solution worked for me, thanks!
Thanks! Good info. In my case, my VM was on a 3PAR VMWare VVOL and I had started replication of it from one location to another. The VM crashed because it couldn’t quiesce. I removed the replication. I went to power it on and got the error. I checked and had VMWare snapshots for the VM. I removed the snapshots and I was able to power on the VM.
Paul L Mekelburg says
Ive seen this error recently when the RAM allocation was set too high on a new VM.
Ran into this one today. Thanks Duncan!
Hello, I had this error yesterday. I had two VM’s with 16 gigs of RAM each, both configured exactly the same, except one difference. On one of the VM’s I had enabled “Reserve all guest memory (All locked). I added 64 GB of RAM. Worked ok when I powered it on. On the second one, the option to Reserve all guest memory was unchecked. I added 64 GB and I was getting the exact error message on this thread. After I selected “Reserve all guest memory (All locked) it powered on with out any issues. I’m nut sure why it was not able to boot up when memory was shared, but this resolved my issue for now. Hope this helps.
We just ran into this error message today. Trying to power it up and the got an error in the error stack that says “Could not power on virtual machine: CPU min outside valid range.”
It appears the VM had a CPU reservation set, and once I put that back to zero it was able to power on.
storage problems here. same error message
thx for the hint.
Storage Problem.
Reconfigure VM Power On ssuccessfully done.
Thank You.
Primary Sidebar
About the author
Duncan Epping is a Chief Technologist in the Office of CTO of the Cloud Platform BU at VMware. He is a VCDX (# 007), the author of the «vSAN Deep Dive», the “vSphere Clustering Technical Deep Dive” series, and the host of the «Unexplored Territory» podcast.
Upcoming Events
Aug 21st – VMware Explore
Sept – VMUG Slovenia (virtual)
Oct 12th – VMUG Sweden
Nov 6th – VMware Explore
Nov 23rd – UK VMUG
Dec 7th – Swiss German VMUG
Module monitorloop power on failed что делать
Reddit and its partners use cookies and similar technologies to provide you with a better experience.
By accepting all cookies, you agree to our use of cookies to deliver and maintain our services and site, improve the quality of Reddit, personalize Reddit content and advertising, and measure the effectiveness of advertising.
By rejecting non-essential cookies, Reddit may still use certain cookies to ensure the proper functionality of our platform.
For more information, please see our Cookie Notice and our Privacy Policy .
Get the Reddit app
The officially unofficial VMware community on Reddit. Please read the rules prior to posting!
I moved some VMs around to different storage manually not a migration, and i cannot get the VMs to boot giving this error:
Key haTask-10-vim.VirtualMachine.powerOn-199208051
Description Power On this virtual machine
Virtual machine: Veeam
State Failed — Module 'MonitorLoop' power on failed.
Errors Module 'MonitorLoop' power on failed.
File system specific implementation of Lookup[file] failed
Failed to create swap file '//Veeam-284c7083.vswp' : Bad parameter
Could not power on virtual machine: Bad parameter.
Failed to power on VM.
Failed to start the virtual machine.
Not knowing how to troubleshoot this i looked into the vmx file and saw a reference to a swap file on the old storage that i just moved from, so i modified that to reflect the new storage volume:
The file was actually not there, so i created the file and the VM still fails to boot with the same error message.
Am i completed hosed on this VM or is there a way to possibly recreate the files it needs to get it booting again?
What are my options for recovering this VM?
I actually have several that are doing this, but i figured id just restore them with Veeam. but its happening to my Veeam server as well 🙁
Failed to power on virtual machine SVR1. Module 'Monitor Loop' power on failed.
Updated Esxi to 7 and now one of the Linux machine is not booting up with.
Failed — Module ‘MonitorLoop’ power on failed.

Enter to win a Yeti Crossover Backpack

JasonValentine 
- check 147 Best Answers
- thumb_up 467 Helpful Votes
Well , the error specifically says that you have an invalid CPU allocation.
The question is where this is coming from.
Do you have any Resource Pools? Are you using Reservations or Limits on the virtual machines themselves?
Does your cluster use «Host Admission Control» ?
Googling your error message provides a number of discussions. Perhaps that one will start you down the right path.
3 Replies

JasonValentine 
- check 147 Best Answers
- thumb_up 467 Helpful Votes
Well , the error specifically says that you have an invalid CPU allocation.
The question is where this is coming from.
Do you have any Resource Pools? Are you using Reservations or Limits on the virtual machines themselves?
Does your cluster use «Host Admission Control» ?
Googling your error message provides a number of discussions. Perhaps that one will start you down the right path.

So right after I posted this question I started playing around with the resources as stated. Notice I have a reservation on the CPU, I removed that and it finally let me boot up the machine. Appreciate the reply! JasonValentine
- local_offer Tagged Items
JasonValentine

JasonValentine 
- check 147 Best Answers
- thumb_up 467 Helpful Votes
Nice! Glad you got it sorted out
This topic has been locked by an administrator and is no longer open for commenting.
To continue this discussion, please ask a new question.
Read these next.
Accessing Camera on Another Router
Hello!I know this will probably be easy, but, I figured I'd get some expert advice on exactly how to do this. I have a wireless Eufy Floodlight 2 Pro camera (Camera 1) located at the bridge that crosses our creek. I have a directional antenna broadcasti.
My First Network Design Task
Hi All,I've been hoping to get into Network/WiFi design and my boss has decided to give me a shot. He's set me the following task which seems very general to me. I think what he's looking for is a general understanding of the type of kit needed r.
Snap! — SysAdmin Praise, Toad-Mageddon, ATV with 18 Wheels, Nuclear Rockets
Your daily dose of tech news, in brief. Welcome to the Snap! Flashback: July 26, 1989: Robert Morris becomes first person indicted under the 1986 US Computer Fraud and Abuse Act (Read more HERE.) Bonus Flashback: July 26, 1963: World’s Fi.
Windows Imaging for FPP/Retail and Evaluation Licenses
I want to create Windows image to deploy on multiple machines. During sysprep, I will not be applying/activating Windows. Sysprep will include installation of free softwares /inactivated software we use in company and some changes to Windows configur.
How to get servers to stop trying to install Windows Defender Updates
Hi,We don't use Windows Defender, but some of our machines are trying to install updates for it and they are failing. This is spamming their System Event logs which is in turn spamming our alerting system. Does anyone know how I can get these servers to.
