Skip to main content

Force Shutdown on VMWare Player

Here a simple tip for VMWare users. If you have set the memory allocation of your VMPlayer to be high and one day wake up with error saying it cannot start the VM because there is not enough memory on the host, here is what you can do:

1. Adjust the VMWare memory allocation to a lesser value. Closing the VMWare will not commit the changes on the memory allocation till you shutdown the VM itself. This is the problem, you cannot shutdown the VM unless you can start it.
2. To workaround this problem, go to the folder where the VM file reside and delete the .VMSS file. Open your VM , by then the memory allocation had been applied and the memory allocation problem is resolved.
Labels:

Comments

Unknown said…
Note: This comment isn't with regard to your blog.

Sir may I ask for your email address if you don't mind. And by the way, I invited you sa Linkedin.com. I'm just gonna wait for the confirmation.hehe. Si vic abana po ito, your former student sa st.louis.

Thanks
9:42 PM
Anonymous said…
hey, you saved my day! thank you!!
9:02 PM
MARVIN TRILLES said…
@Jay

No problem dude . Thank you for visiting my blog.
9:48 AM
Post a Comment

Popular posts from this blog

Getting Started with Stateless : A Lightweight Workflow Library Alternative for .NET

Image Credit: https://www.pioneerrx.com A year ago, I was looking for a simple workflow manager for a project I was working. Its a medium sized application that involves tracking the state of assets in the system. Back in 2008, Microsoft (MS) introduced new technologies along with the release of Visual Studio 2008: Windows Presentation Foundation (WPF), Windows Communication Foundation (WCF), and  Windows Workflow Foundation (WF). Having worked in a company utilizing mostly MS products for development, my first option was to go with WF. After doing some time reading and studying the library, I paused and decided it was too complex for my requirement. Using WF would be an overkill and the fact that it has, a rather, steep learning curve, there has to be another option. My mind toyed with the idea of developing a simple workflow library myself. It would be a learning experience but it might end up consuming a lot of time. Why reinvent the wheel? So I started querying the ...
Post a Comment
Read more

Hiding Unwanted Python Folders and Files in Visual Studio Code

Visual Studio Code is a universal editor and pretty good at it. However, the explorer view maybe cluttered with the automatically generated folders and files confusing developers. Python is no different. Below are example files and folders generated by Python. The __pycache__ folder and *.pyc files  are totally unnecessary to the developer. To hide these files from the explorer view, we need to edit the settings.json for VSCode. Add the folder and the files as shown below: Copy and paste the lines below : "**/*.pyc" : { "when" : "$(basename).py" }, "**/__pycache__" : true
Post a Comment
Read more

The Story Behind the Name C#

I remember one time in an exam for employment , the first question was - who is the father of C#? I have been working with the language but never did I ask myself who actually started the language ( of course Mirosoft was the brainchild , right? ) . After a googling expedition I found out who was the culprit - Microsofts Anders Hejlsberg . I was not interested why it was called C# then , but opening my VS2008 today , I stumbled on one of the articles being shown at the VS2008 opening page - "Computer World: The A-Z of Programming : C#". Its an interview with Anders discussing the history and beyond of C# . Heres the cool part , the name for C# prior to its release was actually COOL (C like Object Oriented Language) . Below are some lines taken from the interview: Why was the language originally named Cool, and what promoted the change to C#? The code name was Cool, which stood for ‘C like Object Oriented Language’. We kind of liked that name: all of our files were called .coo...
Post a Comment
Read more