Well, many of us has encountered the issue of VM hung status whether it’s a Windows or Linux machine. Most of the time system admin use to restart the VM to recover from the hung state.
Now, the question comes how can we identify the cause of the VM hung. Yes, we can check the same in vmware.log of that particular Virtual machine but that will give only limited information.
What if we can get the memory dump of that VM to know the actual cause of hung. So, to get the memory dump of the VM we first need to get .vmss file of that VM.
To get the .vmss file we need to suspend the VM by going into edit setting of the VM and select suspend VM option. Now, into the datastore inside VM folder you will find a new file which is called .vmss .
Now, its quite difficult to read the .vmss file . Now to extract it and convert it into core dump (memory dump) you can use one VMware fling tool (Vmss2core).
Vmss2core will convert the .vmss file to coredump (memory dump) and core dump can be readable by MS tool called windbg to get the actual cause of the issue.
Happy sharing …J