WindowsAdminGuru BLOG

How to deal with PSOD - VMware PSOD Purple Screen of Death - Debugger waiting (world 2078) -- no port for remote debugger. "Escape" for local debugger - Easy troubleshooting steps and how to identify or determine exact root cause of the PSOD issue Host is down with PSOD with the above said error. Verified BIOS settings, worked with on site engineer, contacted the IBM server support (since this is IBM server, have contacted IBM, if it is IBM or some other hardware, you may need to reach out the respective vendor) Sometimes it could be server hardware issue like DIMMs, CPU, Processor related or may be a chance of network related. Please have a through check on the above said and come to a conclusion what could the issue. Based on that, need to troubleshoot the issue.

Guest OS VM sessions going into hung state or unresponsive state while taking snapshot backups. The reason being, while taking snapshot backups, if any more activities planned like running some batch scripts that might cause CPU spike. This leads to more load on the VM session, the assigned resources are not available or in some cases, the data store got filled out fast. In this scenario, we will have stop the VM snapshot backup and reboot the server and check the logs what is the reason the server went into hung state. If the same issue getting repeated, VMware admins can do is, when you found the VM session in unresponsive state, move the VM into suspend mode and download the logs. Later can do the investigation if needed.

VMware System Admins must know this information where the VMware Site Recovery Manager service name will be available in case, if admin unable to connect to SRM configuration server via vCenters. Usually SRM server will be different than the vCenter server. What is the VMware Site Recovery Manager (SRM) service and where we can find this? This can be found in Services Login to SRM server and go to Services and search for VMware VMware vCenter Site Recovery Manager Server