AHV Virtualization

Hi,I’m looking for clarification on AHV Metro Availability behavior and the supported procedure for temporarily isolating an entire site during network maintenance (switching replacement).The environment consists of two Nutanix AHV clusters with synchronous replication, managed through Prism Centrals (one per site) and a Witness VM deployed at a third site over a VPN. As aditional info AOS and PC versions are PC/AOS 7.6 and AHV 11.0.2 .The customer reported the following sequence during a switch replacement: They disconnected the VPN to the witness, intending to make it unreachable from both clusters (that should avoid automatic launch of any recovery plan). Then they disconnected one swich on cluster A, so cluster B was unable to reach it. According to the customer, at that moment recovery automatically started and the VMs from cluster A were recovered on the cluster B. As a result they reported duplicate VMs and had to determine which instances to retain (splitbrain scenario).

Move Appliance Deployment Nutanix Move 6.3.3 appliance deployed successfully in the VMware environment. VMware Source Configuration VMware vCenter added and source VM inventory discovered successfully. Nutanix Target Configuration Nutanix AOS/AHV destination added and validated successfully. VDDK-Free Migration Plan Migration plan created using Move 6.3.3 DirectPath without supplying VMware VDDK. Nutanix documents DirectPath as the Move 6.3.3 migration method that provides an ESXi migration path without requiring VDDK. Automatic Source VM Preparation Windows source VM preparation completed successfully. Source VM Validation VMware CBT and VMware Tools connectivity validated successfully. Initial Data SeedingMOVESnap-0 created and initial VM data seeded to the Nutanix target. Ready for Cutover VM successfully reached Ready to Cutover status. Periodic Data Synchronization Periodic synchronization continued between VMware and AHV before cutover. Source VM Quiescence Source VMware VM was s

We are encountering an issue during the NCC health check on our Nutanix cluster and would like to know if anyone has experienced a similar problem and can share the resolution.AOS Version: 7.3.1.1 NCC Version: 5.2.1 Hypervisor: AHV v.10.3.1.9 Cluster Size: 16

Hi All, we have several Nutanix Clusters that are all managed by Prism that is on its own machine.  We are looking to move one of the 4-Node Clusters to the DR Site that is on a different subnet, which means a RE-IP will be needed of this Nutanix Cluster. This is going to mean RE-IP of the Dell iDRAC setup, Nutanix AHV hosts IP, Nutanix CVM IPs, etc.  Is a RE-IP straightforward? Or is it generally recommended to avoid a RE-IP due to issues and instead rebuild at the DR site on the network there? Thanks

What’s a vTPM?The vTPM module is the virtual equivalent of a physical TPM chip. It securely stores cryptographic keys used for BitLocker drive encryption, Windows Secure Boot, measured boot, and attestation features. Each vTPM holds unique cryptographic material, and without those keys, a VM may not be able to decrypt its disks or boot securely.Why Does Protection Domain (PD)-Based DR Fail with vTPM VMs?Legacy Protection Domains were built before vTPM was introduced, so PDs replicate only VM disks and metadata, not the vTPM device or its secure state. vTPM keys are encrypted and tied to the local cluster’s KMS. During PD-based replication, those keys cannot be transferred to the DR site. As a result, a vTPM-enabled VM may fail to boot or lose access to encrypted volumes after DR failover.Why Does Protection Policy (PP)-Based DR Support vTPM VMs?Modern Protection Policy-based DR introduces full vTPM awareness. It replicates vTPM state and keys alongside VM data. It integrates with Nutan

I am not able to test drive any more. What has happened to my account? Will someone fix this?

 Hello Nutanix Community,I'm trying to expand an existing 3-node Nutanix cluster by adding a fourth node, but the expansion process fails during the pre-expansion checks with the following error:Failure in pre expand-cluster tests.Errors:Precheck: test_cassandra_ssd_size_check failed.SSD tier on nodes ['172.22.129.4'] is not sized to accommodate expected metadata growth on cluster.Refer KB-8842 for more details.Environment Details: Platform: Cisco UCS C240 M7 AOS Version: 7.0 Storage Type: Hybrid Existing Cluster: 3 Nodes New Node: 1 Node (4th node) Additional Information: The new node has the same SSD and HDD configuration as the existing nodes. The SSD capacity on the affected node (172.22.129.4) is identical to the other cluster nodes. The issue occurs during the pre-expansion validation stage. My Questions: What could cause this error if all nodes have identical SSD configurations and capacities? What troubleshooting steps would you recommend to identify the root caus

Hi Nutanix Team,We are planning to run Windows/Linux VMs on Nutanix AHV with the following environment: Cisco UCS X210C M8 Nutanix AHV Dell PowerMax 2500 25GbE network Can a Windows/Linux Guest OS running on AHV use its native iSCSI initiator to directly access an external Dell PowerMax storage LUN?The architecture is:Guest OS → iSCSI Initiator → AHV/OVS → 25GbE → Dell PowerMaxIf yes, is this officially supported by Nutanix? Could you please provide the relevant documentation?Thank you.

Phase 1: Foundation Orchestration & Pre-Imaging Preparation1. Foundation Session InitializationFoundation does not immediately image the server. It first creates and activates its internal imaging workflow.Foundation associates the imaging workflow with a NodeConfig object representing the target CVM and spins up local CherryPy/Flask microservices on your laptop or deployment machine to handle the imaging tasks.2. Node DiscoveryFoundation attempts to locate the physical nodes. It broadcasts over the local Layer 2 network segment using IPv6 link-local multicast (via the WS-Discovery protocol). It listens for replies from factory-fresh nodes or unconfigured hardware listening on the network.Foundation is using its internal RPC mechanism to resolve information from the node before applying the final configuration.3. Network Provisioning & VerificationFoundation begins constructing the network configuration that will ultimately be applied to the target environment. It subsequently

We operate a hybrid VDI environment: Windows 10 on vSphere and Windows 11 on Nutanix AHV(Horizon 2603/2606).While vSphere works flawlessly, we face two critical blockers on Nutanix AHV that force inefficient manual workarounds.We request feature parity with vSphere. Issue 1: Manual Pool Registration LimitProblem: When deploying VMs from a master image with Horizon Agent pre-installed, only one VM successfully registers in a Manual Desktop Pool on Nutanix AHV.Current Workaround: To register multiple VMs, we must exclude the Horizon Agent from the master image and install it individually on every single VM after provisioning.Expectation: Nutanix AHV should support standard golden image deployment (Agent pre-installed) allowing multiple VMs to register simultaneously, just like vSphere. Issue 2: Persistent Black Console After DisconnectProblem: After a user disconnects a session, the VM's console screen remains Black. Administrators can not view the desktop state or perform maintenance vi

While enabling the Microservices Infrastructure (CMSP) on Nutanix Prism Central, the deployment failed during the post-deployment prechecks with an error indicating that Prism Central was not compatible with enabling Microservices Infrastructure.* Root Cause Analysis:When CMSP is enabled, Prism Central deploys an internal Kubernetes-based platform to host Nutanix microservices. For CMSP deployment on Prism Central, the internal CMSP services use the following default networks: 192.168.5.0/24 – Kubernetes infrastructure network 10.100.0.0/16 – Kubernetes Pod network 10.200.32.0/24 – Kubernetes Services network The upstream network environment must not overlap with these network ranges. Since Kubernetes cannot differentiate between internal container traffic and the production management network, CMSP prechecks intentionally block the deployment to prevent potential routing conflicts.* Solution:If the environment requires using these subnet ranges in the upstream network, you must cha

𝐖𝐡𝐚𝐭’𝐬 𝐚 𝐯𝐓𝐏𝐌?- The vTPM module is the virtual equivalent of a physical TPM chip.- It securely stores cryptographic keys used for BitLocker drive encryption, Windows Secure Boot, measured boot & attestation features.- Each vTPM holds unique cryptographic material, and without those keys, a VM may not decrypt its disks or boot securely.𝐖𝐡𝐲 𝐝𝐨𝐞𝐬 𝐏𝐫𝐨𝐭𝐞𝐜𝐭𝐢𝐨𝐧 𝐃𝐨𝐦𝐚𝐢𝐧 (𝐏𝐃)-𝐛𝐚𝐬𝐞𝐝 𝐃𝐑 𝐟𝐚𝐢𝐥 𝐰𝐢𝐭𝐡 𝐯𝐓𝐏𝐌 𝐕𝐌𝐬?- Legacy Protection Domains were built before vTPM was introduced, so PDs replicate only VM disks + metadata, not the vTPM device or its secure state.- vTPM keys are encrypted and tied to the local cluster’s KMS.- During PD-based replication, those keys cannot be transferred to the DR site.- As a result, a vTPM-enabled VM fails to boot or loses access to encrypted volumes after DR failover.𝐖𝐡𝐲 𝐝𝐨𝐞𝐬 𝐏𝐫𝐨𝐭𝐞𝐜𝐭𝐢𝐨𝐧 𝐏𝐨𝐥𝐢𝐜𝐲 (𝐏𝐏)-𝐛𝐚𝐬𝐞𝐝 𝐃𝐑 𝐬𝐮𝐩𝐩𝐨𝐫𝐭 𝐯𝐓𝐏𝐌 𝐕𝐌𝐬?- Modern Protection Policy-based DR introduce

While enabling the Microservices Infrastructure (CMSP) on Nutanix Prism Central, the deployment failed during the post-deployment prechecks with an error indicating that Prism Central was not compatible to enable Microservices Infrastructure.💡 𝗥𝗼𝗼𝘁 𝗖𝗮𝘂𝘀𝗲 𝗔𝗻𝗮𝗹𝘆𝘀𝗶𝘀:- When CMSP is enabled, Prism Central deploys an internal Kubernetes-based platform to host Nutanix microservices.- For CMSP deployment on Prism Central, the CMSP internal services use the following default networks:  --> 𝟣𝟫𝟤.𝟣𝟨𝟪.𝟧.𝟢/𝟤𝟦 - 𝘒𝘶𝘣𝘦𝘳𝘯𝘦𝘵𝘦𝘴 𝘪𝘯𝘧𝘳𝘢𝘴𝘵𝘳𝘶𝘤𝘵𝘶𝘳𝘦 𝘯𝘦𝘵𝘸𝘰𝘳𝘬  --> 𝟣𝟢.𝟣𝟢𝟢.𝟢.𝟢/𝟣𝟨 - 𝘒𝘶𝘣𝘦𝘳𝘯𝘦𝘵𝘦𝘴 𝘱𝘰𝘥 𝘯𝘦𝘵𝘸𝘰𝘳𝘬  --> 𝟣𝟢.𝟤𝟢𝟢.𝟥𝟤.𝟢/𝟤𝟦 - 𝘒𝘶𝘣𝘦𝘳𝘯𝘦𝘵𝘦𝘴 𝘴𝘦𝘳𝘷𝘪𝘤𝘦𝘴 𝘯𝘦𝘵𝘸𝘰𝘳𝘬- The upstream network environment cannot overlap with these networks. - Since Kubernetes cannot differentiate between internal container traffic and the production management network, the CMSP prechecks intentionally block the deployment

What actually happens?Traditional backups copy entire files or virtual disks, which takes time and slows down your system. Nutanix uses a Redirect-on-Write (RoW) architecture combined with instantaneous metadata pointers.1️⃣ 𝘛𝘩𝘦 𝘗𝘰𝘪𝘯𝘵𝘦𝘳𝘴 𝘍𝘳𝘦𝘦𝘻𝘪𝘯𝘨 (𝘐𝘯𝘴𝘵𝘢𝘯𝘵):- Instead of copying your data blocks, Nutanix copies the metadata map (the index or map that tells the system where your data blocks live on the physical disks).* The Process: The system takes a snapshot of this map, which takes milliseconds because metadata is incredibly small.* The Result: The original data blocks become read-only for that specific point in time.2️⃣ 𝘛𝘩𝘦 𝘙𝘦𝘥𝘪𝘳𝘦𝘤𝘵-𝘰𝘯-𝘞𝘳𝘪𝘵𝘦 𝘔𝘦𝘤𝘩𝘢𝘯𝘪𝘴𝘮 (𝘕𝘰 𝘖𝘷𝘦𝘳𝘩𝘦𝘢𝘥):- The moment after the recovery point is created, your Virtual Machine (VM) keeps running and writing new data.* Old Data: Stays exactly where it was, safely frozen as your recovery point.* New Data: Instead of overwriting old data, any new changes are written t

What actually happens?Traditional backups copy entire files or virtual disks, which takes time and slows down your system. Nutanix uses a Redirect-on-Write (RoW) architecture combined with instantaneous metadata pointers.1️⃣ 𝘛𝘩𝘦 𝘗𝘰𝘪𝘯𝘵𝘦𝘳𝘴 𝘍𝘳𝘦𝘦𝘻𝘪𝘯𝘨 (𝘐𝘯𝘴𝘵𝘢𝘯𝘵):- Instead of copying your data blocks, Nutanix copies the metadata map (the index or map that tells the system where your data blocks live on the physical disks).* The Process: The system takes a snapshot of this map, which takes milliseconds because metadata is incredibly small.* The Result: The original data blocks become read-only for that specific point in time.2️⃣ 𝘛𝘩𝘦 𝘙𝘦𝘥𝘪𝘳𝘦𝘤𝘵-𝘰𝘯-𝘞𝘳𝘪𝘵𝘦 𝘔𝘦𝘤𝘩𝘢𝘯𝘪𝘴𝘮 (𝘕𝘰 𝘖𝘷𝘦𝘳𝘩𝘦𝘢𝘥):- The moment after the recovery point is created, your Virtual Machine (VM) keeps running and writing new data.* Old Data: Stays exactly where it was, safely frozen as your recovery point.* New Data: Instead of overwriting old data, any new changes are written t

The deployment of AHV/AOS through Phoenix ISO on a Hyper-V host failed before the actual imaging process could begin. During the Hyper-V customization stage, Phoenix terminated as it cannot find the required FAT32 partition. The deployment therefore stopped before Phoenix could continue with the normal AHV/AOS installation workflow.💡 𝗥𝗼𝗼𝘁 𝗖𝗮𝘂𝘀𝗲 𝗔𝗻𝗮𝗹𝘆𝘀𝗶𝘀:- The underlying issue was related to the existing storage/partition metadata on the Hyper-V host.- Phoenix's Hyper-V customization logic was evaluating the existing disk layout and detecting the disk as having a previous partition structure.- The customize_hyperv.py script specifically flags sdo as your host boot disk. It triggers a function called Mounting Hyper-V FAT32 partition to search for a pre-existing staging partition.- Because /dev/sdo only contains standard Windows OS layout partitions (with an EFI system partition of only 99MB), it fails the hardcoded check for a size >= 1GB and triggers the FATAL halt.

여러분, 안녕하세요,저희 사무실 테스트 환경에 있는 EOSL Nutanix NX-3060-G4 서버에 Nutanix AOS 및 AHV의 최신 버전을 설치하는 방법에 대한 안내를 부탁드립니다.해당 서버는 하드웨어 지원 수명 주기가 종료되었지만, 테스트 및 연구 목적으로 재사용하고 싶습니다.진행하기 전에, 해당 구성이 더 이상 공식적으로 지원되지 않더라도 이 하드웨어에 최신 AOS 릴리스와 그에 상응하는 AHV 버전을 설치하는 것이 기술적으로 가능한지 여부를 확인하고 싶습니다.다음 질문들에 대한 조언을 부탁드립니다. 하드웨어 호환성: NX-3060-G4는 최신 AOS 및 AHV 버전을 실행할 수 있습니까? 아니면 이 모델에서 지원하는 최대 버전이 특정되어 있습니까? 설치 방법: Nutanix Foundation을 사용하여 이 서버에 AOS 및 AHV를 새로 설치할 수 있습니까? 파운데이션 요구 사항: 이 하드웨어에 필요한 특정 파운데이션 버전 또는 설치 워크플로가 있습니까? 설치 제한 사항: EOSL 시스템에 설치를 방해할 수 있는 하드웨어 호환성 검사, 설치 프로그램 제한 또는 기타 기술적 제한 사항이 있습니까? 대안적인 접근 방식: 최신 버전을 직접 설치할 수 없는 경우, 비운영 연구실 환경에 적합한 권장 해결 방법이나 대체 설치 경로가 있습니까? 해당 서버가 더 이상 공식적으로 지원되지 않을 수 있다는 점을 이해하고 있으며, 저는 순전히 테스트 목적으로만 사용할 예정입니다.NX-3060-G4 또는 이와 유사한 구형 Nutanix 플랫폼에 최신 AOS/AHV 버전을 설치해 본 경험이 있으신 분이 계시다면, 관련 권장 사항, 문서 또는 설치 가이드를 공유해 주시면 대단히 감사하겠습니다.도와주셔서 감사합니다!

i need a nutanix command to change the ovs0 interfaces as the command :nutanix@cvm$ manage_ovs --bridge_name br0 --interfaces eth0,eth2 --bond_name br0-up --bond_mode active-backup --require_link=false update_uplinksfrom AHV 11.2 doesn’t work if the cvm doesn’t reach to the gateway ,so if there is a command from ahv do that searched and found that command but i not sure it is valued or not ovs-vsctl set port br0-up interfaces=eth2,eth4

Hi,Since upgrading to PC 7.6 / AOS 11.2 we’ve tipped over the edge on available CPU resources and are experiencing some performance issues (Spikes in CPU Wait, application failures) we’ve engaged with support who identified ADS/Solver being unable to move VM’s to reduce hotspots, because all hosts are hotspots, and we’re basically oversubscribed.  I won’t deny this, but we weren’t experiencing so many issues before the update. Support advice is to reduce vCPU allocation on vm’s that don’t need them. We’ve got a lot of VM’s reporting as over provisioned, the majority of these are windows VM’s with 2 vCPU’s our testing has shown that with only a single vCPU windows really doesn’t work well. So i have some questions:Has anyone else noticed an increase in consumed CPU resources following update to PC/AOS 7.6 Do others experience the same with windows server VM’s, or is it a feature of our environment that 2 vCPU’s is the minimum If you do experience the same, do you just live with a large

Please advise on vulnerability mitigation for nutanix-sa-57 security advisory and possible fix release date. We understand that upgrading to AOS 7.6 is the available option at the moment.  The hardware is 3-node Lenovo HX650 V3 cluster.Please confirm the dark site upgrade sequence with the below bundles is correct, or if it can be done better.1    LCM Framework Bundle 3.4.0.12    NCC LCM Bundle 6.0.0.13    Nutanix Compatibility Bundle4    Prism Central LCM Bundle 7.65    Foundation LCM Bundle 5.116    AOS LCM Bundle 7.67    AHV LCM Bundle 11.38    LENOVO Firmware LCM Bundle 3.0All bundles to be uploaded and run from PE LCM except the "Prism Central Bundle LCM Bundle" from the PC LCM.

wanted to share a real-world scenario I recently encountered regarding Prism Central account lockouts and see how the community handles similar setup challenges.The Issue:Our primary local administrator account on Prism Central kept getting locked out unexpectedly. After inspecting the logs, we traced the issue to an external automated log integration (like a SIEM/Splunk collector) executing API calls using stale credentials.Even after disabling the integration at the source and resetting the admin password, the lockout behavior occasionally persisted due to cached sessions or residual background API requests.

Hello,I am experiencing an issue where VM IP addresses are no longer displayed in Prism after changing the network environment of a Nutanix cluster.I would appreciate any advice or information about similar cases.Environment Nutanix AHV-based cluster Multiple VMs running on the cluster Both Windows and Linux guest operating systems are present Nutanix Guest Tools (NGT) are not being used What happened The network environment of the Nutanix cluster was changed. The Gateway configuration of the existing cluster/service network was also changed. The cluster was then connected to a different network environment. The cluster was powered on again. The cluster and VMs are operating normally after the change. Current symptoms All VMs have valid IP addresses configured inside their guest operating systems. Network connectivity from the VMs to the Gateway and external networks is working normally. The VM network adapters and VLAN configuration appear to be functioning correctly

Hello all,We are encountering an issue with a user who updated ESXi to version 8.0u3e onto nutanix Supermicro 8155 G8. The problem has arisen while attempting to update hardware components; the LCM update fails because `ipmitool` is missing from the hosts.The cluster is located in a "dark site," so updates are loaded via direct upload and AOS is at 7.5.1.10 version.Do you know of any workarounds?Thanks in advice,Alex

As per the infrastructure deployment SDK:Typically, Dell ships their hardware pre-configured to automatically install AHV after you first turn the node on. The downside is that, when you turn the node on for the first time, it runs a series of scripts to install the hypervisor and create the CVM. Customers often turn the machines off before the preparations are finished because they don’t know to leave the machines on. It’s usually less complex to use a standalone Foundation VM on bare-metal nodes.after power on the node and wait about an hour, the AHV is installed and the CVM not created, what can cause this issue and what is the expected time for the node to install the AHV and create the CVM?

While deploying Nutanix three nodes cluster we are not able to ping default gateway from all the hosts.Please suggest end customer network team is working on the same but do anyone has faced similar kind of issue.