Mastering Your Nutanix Environment: Nonconfigurable AHV and ESXi Components

In the world of Nutanix, customization and configuration play significant roles in optimizing your virtual environment. However, it’s crucial to recognize that certain components within Nutanix, whether you’re using AHV or ESXi hypervisors, are non-configurable. Modifying these elements could severely impact the performance or even jeopardize the functionality of your Nutanix cluster.

Nutanix Software: Key Limits

  1. Local Datastore: The local datastore name is a fixed entity.
  2. Controller Virtual Machine (CVM):
    • Memory Configuration: Adjusting memory settings is permissible only to enable specific features.
    • Modifications: Avoid deleting, taking snapshots for backups, renaming, modifying, or deleting CVM.
    • User Accounts: The admin and nutanix user accounts are not to be altered or deleted. Creation of additional accounts is discouraged; instead, use the default accounts or sudo for root access.
    • CVM Memory: Never reduce below the recommended minimums.
  3. Third-Party Storage: Use on the host part of Nutanix clusters is unsupported and risky.
  4. Command Restrictions: Stick to commands found in Nutanix documentation for CVM operations.

AHV Hypervisor: Where Not to Tread: AHV, Nutanix’s integrated hypervisor, has specific configuration boundaries:

  • Hypervisor Configuration: Including package installations.
  • Controller VM Virtual Hardware: Editing the .xml configuration file is off-limits.
  • iSCSI Settings: Avoid modifications.
  • Open vSwitch Settings: Remain unaltered.
  • Third-Party Software: Installation of non-approved software is unsupported.
  • Software Updates: Only use Nutanix sources.
  • Snapshots and User Accounts: Avoid creating these for Controller VM and on AHV hosts.
  • Timezone and Domain Settings: Changing the AHV host timezone or joining to domains is not supported.

ESXi Settings: Configurations to Avoid: For those using ESXi hypervisors:

  • NFS Datastore Settings: Modifications can impact performance.
  • VM Swapfile Location: Keep as is.
  • VM Startup/Shutdown Order: This should remain unchanged.
  • CVM Virtual Hardware: The .vmx file is not to be tampered with.
  • iSCSI Software Adapter Settings: Maintain default configurations.
  • Hardware Settings: Includes passthrough HBA settings.
  • vSwitchNutanix Standard Virtual Switch: Avoid alterations.
  • vmk0 Interface: This should remain configured in the Management Network port group.
  • SSH: Essential for various scenarios, including host failure recovery.
  • Host Firewall Ports: Open as necessary.
  • CPU Resource Settings: For the CVM, these should not be altered.
  • Reset System Configuration: Use this option with caution.
  • ProductLocker Symlink: Do not redirect to non-local data stores.

Summary: Navigating the Nutanix environment requires balancing customization and adherence to certain non-configurable aspects, especially when dealing with AHV or ESXi hypervisors. Understanding these limitations is essential for maintaining a stable and efficient Nutanix cluster. Remember, while Nutanix offers a wide range of configurable options, respecting these boundaries is key to ensuring a robust and reliable virtual environment.



Is this something you are interested in? Did I miss something?

Feel free to leave a comment and let me know what you think!