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.


Vicente 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 I'm just gonna wait for the confirmation.hehe. Si vic abana po ito, your former student sa st.louis.

Jay said…
hey, you saved my day! thank you!!
Marvin said…

No problem dude . Thank you for visiting my blog.

Popular posts from this blog

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

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 internet for a better solution. I stumbled upon Stateless

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 :


Get Started with MongoDB Stitch : The New Backend As Service Offering from MongoDB

Halfway of this year, the guys from MongoDB launch their new backend as service product called MongoDB Stitch. While the launch is just for the beta, the promise of the service is quite interesting. MongoDB has been around for long now and some development stacks have been based on its database product, the MongoDB-ExpressJS-Angular-NodeJS (MEAN) and the MongoDB-ExpressJS-React-NodeJS (MERN) stacks to name a few. These stacks, however, relies on backend technology such as ExpressJS and NodeJS. The idea of provisioning servers and developing the backend solution makes it daunting for small to medium scale applications. MongoDB Atlas, at least made life much easier by providing on cloud database solution, but there must be a simpler solution, right? A solution the would stitch the backend and frontend together ( see what I did there ?).
MongoDB Stitch lets developers focus on building applications rather than on managing data manipulation code, service integration, or backend infrastruct…