Yes, I will file a request to get this changed. Strange error message, for a simple problem. 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! In order to fix the message that VMware failed to lock the file, you need to look for so-called lock files or lock folders in your virtual machine folder. In this case I removed some obsolete VMs and then powered on the VM that had the issue without any problems. In other words, you are probably running out of disk space on the device the VM is stored on. 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.į 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. Module MonitorLoop power on failed when powering on VM switch so if the appliance fails you wont lose your Internet connection. I had never seen it before myself, so I was kind of surprised when I figured out what it was referring to. A DPI based module, developed using Cavium SDK for octeon multicore network. Once it is turned off, go to the directory where VM and the files are saved. 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. If the VM is still on, right-click on the VM and go to Power and then Power Off.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |