Pro-Tip Suggestion: Avoid Production BSODs by Validating Guest OS Compatibility Before Enabling Automated Hot Add

George Fady Lv2Posted 2026-Jun-30 19:11

Sangfor HCI provides a phenomenal feature under its Dynamic Resource Extension (DRX) capabilities: Automated Hot Add. When a VM runs out of processing capacity during a sudden demand spike, the cluster can dynamically scale up resources to preserve business stability without human intervention.
However, before clicking "Enable," I strongly suggest executing this 2-step verification checklist:
  • Mandate Sangfor vmTools Installation: Without installing the latest stable version of vmTools inside the Guest OS, the management platform cannot access accurate real-time I/O, memory, and IP allocation traffic metrics. More importantly, vmTools unlocks the underlying virtio drivers needed to recognize on-the-fly hardware additions.
  • Check the Compatibility Table: Not all operating systems support hot adding resource blocks seamlessly. While modern Linux kernels handle hot-plugging CPU cores natively, older legacy Windows Server architectures or unpatched kernels will throw a Blue Screen of Death (BSOD) or kernel panic. Always query the "Guest OSes Supported" matrix in the console first!

Note: Remember that DRX can only add resources on the fly—it cannot automatically reduce them. Reclaiming over-allocated resources requires a full virtual machine shutdown.
Join the Discussion: Have you run into crashes or kernel hitches when hot-adding resources to live databases? What is your standard pre-flight routine for deploying vmTools across massive clusters? Drop your advice below!

Feel alike? Bump to help this suggestion accepted by developers.

An accepted suggestion earns you 100 to 1000 coins. For more active members in Suggestions board, a badge Product Consultant may be rewarded. What is Coin?

Enter your mobile phone number and company name for better service. Go