Vmware monitor loop ошибка

@jcha7965 Greetings — I humbly and possibly ignorantly suggest fully listing your physical available resources, your desired VM resources, and your current VM resources.

@RSchuddinh @RPUL @sudheee02 @KazuXee 

Thank you for the thread, all. It helped me save my job and get my VM back online quickly, although not as fully desired.

I fully believe it is my lack of understanding and knowledge to blame for the struggles I’m having getting to the desired server and VM configuration.

Physical Server Resources available:

Dell R740XD

2x Intel(R) Xeon(R) Gold 6148 CPU @ 2.40GHz

24x 32GB 2400MT/s — 768GB ECC RAM

Dell BOSS card, 2x micron 480ish nvme

PERC H730 Adapter, 4x HUC101212CSS600 HGST 1.2TB

H730 controlling «backplane» (which is actually front of server, love that we can’t say «frontplane» lol)

BOSS in PCIe slot. I read it was supposed to default to RAID 1, but it did not, or at least, I can’t find where it for sure tells me that is operating correctly in RAID 1, which I desire to verify

Predeployment phase

Currently only 1 VM

VM Status:

256GB of nvme

32 GB of RAM

12 cores
Windows Server ’16

I desire VM to get to:

OS only on nvme, and BOSS verified and running in RAID1

Be able to understand this enough that some smaller programs, but needed fast operations, will also run on nvme

other programs will be setup to run on the disk drives in raid 10, OR i might find compatible sas ssd

The Raid10 is not setup yet, i believe it is currently running in jbod mode as i have 4TB of storage available to assign to the VM

I desire ability to assign up to 128GB of RAM to the VM, likely only 32-64GB will be required, but until that is known for sure and I will monitor for usage, I need to allow certain programs within the VM to «stretch their legs» a little bit as we’re testing some settings and hosts.

I desire ability to get 10G networking to the server for use by all VMs. Can this be done securely? I want to understand this all well enough that a financial program can run in its own VM and be completely secure into the network from the other VMs…is that possible or is a 2 or 4 port 10g nic required?

Thank you so much, I will update here and below with information as I find it elsewhere or you helpful people reply.

ITYungn

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:

Power On VM
Key                haTask-2-vim.VirtualMachine.powerOn-164454246
Description        Power On this virtual machine
Virtual machine
State              Failed - Module 'MonitorLoop' power on failed.
Errors
    Module 'MonitorLoop' power on failed.
    File system specific implementation of Lookup[file] failed
    File system specific implementation of LookupAndOpen[file] failed
    Failed to extend swap file from 0 KB to 67108864 KB.
    Current swap file size is 0 KB.
    Failed to extend the virtual machine swap file
    Could not power on virtual machine: No space left on device.
    Failed to power on VM.
    Failed to start the virtual machine.

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:

• Fix KMODE_EXCEPTION_NOT_HANDLED Error on Windows 10
• KVM vs. VMware
• VMware vs HyperV
• How to solve DNS server not responding Error

 When you are powering on the VM and getting below error what do you need to do?

Error code

Module ‘Monitorloop’ power on failed

Failed to extend the virtual machine swap file

Current swap file size is 0 KB

Failed to extend swap file /vmfs/volumes/******

Login to ESXI host where you are getting above error 

Run below command to check list of VM VMs on the ESXi host

vim-cmd vmsvc/getallvms

Now you need to go to the failed VM director using cd command.

cd /vmfs/volumes/SHARED-DATASTORE01/DEMOPRDSRM01

Note: — SHARED-DATASTORE01 ->Datastore name where failed VM is residing 

              DEMOPRDSRM01 -> Failed VM name

Now use “ls” to list out files

Now use ->   vi vmware.log (To read vmware.log file)

Now search for the error when it was failing to power on and you’ll see something similar like whatever you were seeing in vCenter but in the easiest way. Like below

Now you need to check the free space on Datastore where your VM is running.

To check the free space on Datastore run the below command

vmkfstools -Ph /vmfs/volumes/SHARED-DATASTORE01   (P in caps and Datastore name)

Now only 719 MB free space available on Datastore, at least 1 GB free space is required to power ON the VM

Now run below command to check which file is taking more space.

Go inside the Datastore and run 

du -h command

Now you need to decide if you can delete any of the VMs from the Datastore to free up the space

If you want to delete any VM from the Datastore run below command.

/vmfs/volumes/61892dcd-b0d3dd11-0852-000c29b75dac] rm -rf /vmfs/volumes/SHARED-DATASTORE01/DEMOPRDSRM01

 Next time when you shall power on the VM it will power on.

Note-: You can manage Datastore space from the web console as well to free up the space.