Skip to main content

 Mware PSOD (Purple Screen of Death) 

-----------------------------------------------------------------------------------------

Causes

1. Hardware issues: Hardware failures, such as CPU, memory, or disk failures, can cause a PSOD.

2. Software bugs: Software bugs or errors in the ESXi code can cause a PSOD.

3. Configuration issues: Configuration errors, such as incorrect settings or incompatible hardware, can cause a PSOD.

4. Firmware issues: Firmware issues, such as outdated or corrupted firmware, can cause a PSOD.

==========================================================================================

Symptoms 

1. Purple screen: A purple screen with a white font appears, displaying an error message.

2. System crash: The ESXi host crashes, and all VMs running on it are terminated.

3. Error logs: Error logs are generated, providing information about the cause of the PSOD.

------------------------------------------------------------------------------------------

Troubleshooting PSOD:

1. Check error logs: Check the error logs to determine the cause of the PSOD.

2. Verify hardware: Verify that all hardware components are functioning correctly.

3. Update ESXi: Update ESXi to the latest version to ensure that any known bugs are fixed.

4. Check configuration: Check the configuration to ensure that all settings are correct.

Preventing PSOD:

----------------------------------------------------------------------------------------

1. Regularly update ESXi: Regularly update ESXi to the latest version.

2. Monitor hardware: Monitor hardware components for signs of failure.

3. Verify configuration: Verify that all configuration settings are correct.

4. Implement a backup strategy: Implement a backup strategy to ensure that all data is protected in case of a PSOD.

Comments

Post a Comment

Popular posts from this blog

Quick Guide to VCF Automation for VCD Administrators

  Quick Guide to VCF Automation for VCD Administrators VMware Cloud Foundation 9 (VCF 9) has been  released  and with it comes brand new Cloud Management Platform –  VCF Automation (VCFA)  which supercedes both Aria Automation and VMware Cloud Director (VCD). This blog post is intended for those people that know VCD quite well and want to understand how is VCFA similar or different to help them quickly orient in the new direction. It should be emphasized that VCFA is a new solution and not just rebranding of an old one. However it reuses a lot of components from its predecessors. The provider part of VCFA called Tenenat Manager is based on VCD code and the UI and APIs will be familiar to VCD admins, while the tenant part inherist a lot from Aria Automation and especially for VCD end-users will look brand new. Deployment and Architecture VCFA is generaly deployed from VCF Operations Fleet Management (former Aria Suite LCM embeded in VCF Ops. Fleet Management...
Post a Comment
Read more
  Issue with Aria Automation Custom form Multi Value Picker and Data Grid https://knowledge.broadcom.com/external/article?articleNumber=345960 Products VMware Aria Suite Issue/Introduction Symptoms: Getting  error " Expected Type String but was Object ", w hen trying to use Complex Types in MultiValue Picker on the Aria for Automation Custom Form. Environment VMware vRealize Automation 8.x Cause This issue has been identified where the problem appears when a single column Multi Value Picker or Data Grid is used. Resolution This is a known issue. There is a workaround.  Workaround: As a workaround, try adding one empty column in the Multivalue picker without filling the options. So we can add one more column without filling the value which will be hidden(there is a button in the designer page that will hide the column). This way the end user will receive the same view.  
Post a Comment
Read more

Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware

 πŸ”Ή Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware ⸻ 1️⃣ Memory Ballooning (vmmemctl) Ballooning is the first memory reclamation technique used when ESXi detects memory pressure. ➤ Step-by-Step: How Ballooning Works  1. VMware Tools installs the balloon driver (vmmemctl) inside the guest OS.  2. ESXi detects low free memory on the host.  3. ESXi inflates the balloon in selected VMs.  4. Balloon driver occupies guest memory, making the OS think RAM is full.  5. Guest OS frees idle / unused pages (because it believes memory is needed).  6. ESXi reclaims those freed pages and makes them available to other VMs. Why Ballooning Happens?  • Host free memory is very low.  • ESXi wants the VM to release unused pages before resorting to swapping. Example  • Host memory: 64 GB  • VMs used: 62 GB  • Free: 2 GB → ESXi triggers ballooning  • VM1 (8 GB RAM): Balloon inflates to 2 GB → OS frees 2 GB → ESXi re...
Post a Comment
Read more