Unanswered questions

In my blueprint, I need to execute a command on Prism Central VM. The command will be a script on Prism Central VM. My blueprint uses the existing Prism Central VM as the substrate. I tried different ways to execute the command but none of them worked. Could you please advise how I could do it? The script I need to run doesn’t have an API counterpart. I can run PC API from the blueprint without problems. Here are the different ways I tried and how they failed.# SSH EndpointPCSSHEndpoint = Endpoint.Linux.ip(    ["@@{calm_pc_ip}@@"],    name="PC_SSH_Endpoint",    port=22,    cred=SSHCredential,)# ============================================================================# METHOD 1: SSH Endpoint with Target Reference# ============================================================================class Method1_SSHEndpointService(Service):    """    Method 1: Using SSH endpoint with explicit target reference       Pros: Proper SSH connection setup    Cons: Failed with "Machine and credential

HiImagine you have two AHV clusters that are Active-Active (each site has live VMs on it). They are both connected and they are doing Metro-Sync between them.Now you want to move some VMs from one site to the second site. As far as I know I could perform that migration by using MOVE or by doing a manual failover of a protection policy. Is there any way to do a “live migration” between clusters without shuting down any VM?Also, is there any way to do that even if you have Async migration?I have found this but I understand is only talking about migration between nodes): https://portal.nutanix.com/page/documents/solutions/details?targetId=BP-2029-AHV:nutanix-ahv-live-migration.htmlThanks

Trying to deploy the latest CE image (phoenix.x86_64-fnd_5.6.1_patch-aos_6.8.1_ga) on a VMware Workstation 25 machine, the VM is being deployed with the recommended hardware (8 cores, 32Gb, 3 drives (64, 200 and 500). The machine I’m deploying on is a minipc with i9 16 cores, 64Gb Ram and plenty of free NVMe space so its not a resource issue.  I see some other similar posts asking the same question but they looked to be using machines that didnt have sufficient ram to support the VM running with 32GB.  I’ve tried turning the compatibility down to workstation 17.x but that’s made no difference.I’m getting the following error, I’ve looked through the log file but there doesnt appear to be anything obvious that is causing the issue. Thanks in advanceJohn 

Hello, I'm trying to install Nutanix CE on my workstation. I keep getting “error 1155 could not create tmpvol.bin” and “Failed to create tmpvol”. I've already tried it on two different PCs and with different HDDs and SSDs. I tried it with UEFI and with legacy Bios. What could be the cause of this error? Thx.  

Hi Guy’s I'm trying to update our Dev environment which runs on community edition, and AOS, NCC etc all working via LCM, for the AHV though it will just keep failing every single time.It just goes round in a loop watching from the ilo, it first does choose AHV re image, the it reboots and get to that same screen and then just boots to current AHV OS.So is there a way to do this manually without it affecting the CVM’s config running on them?ThanksMark

HiI’m reviewing the network design for a Nutanix AHV cluster and I would like to clarify best practices regarding CVM backplane traffic.Specifically: Is it considered a best practice to separate the CVM backplane (CVM-to-CVM traffic, Stargate/metadata replication, etc.) onto a dedicated network or VLAN? Or is it generally recommended to keep the backplane traffic on the same network as the CVM/host data network (as long as bandwidth and latency requirements are met)? Assuming a standard production environment (10/25GbE, properly sized switching, no extreme east-west congestion), does separating the backplane provide measurable operational or performance benefits? Is it buggy in therms of troubleshooting? does it mainly add complexity without real gain?I’m particularly interested in official guidance or field experience from larger deployments.Thanks in advance!

Hi, We have two cluster, Prod and DR. We have protection policies all set up, as well as recovery plans. However, when performing a planned failover (for testing) ​​​​​​, the execution of the recovery fails. But it also succeeds… with warnings. The warnings say as follow:------VMs/Recovery Points detected on Prism Element(s) with unsupported licenseIMPACTSome VMs might not be recovered.CAUSESome of the VMs/Recovery Points are located on Prism Element(s) with unsupported license.RESOLUTIONMake sure that the Prism Element(s) have supported license. Supported License includes Ultimate License or Pro license with add-on advanced replication.-----The (planned) failover is also successful - so why the warnings? We have Pro licence. As far as I understand it, we need Ultimate licence for Test failover, but not for the planned failover (as long as we don’t do staging in bringing VMs back up). Are these warnings a red herring? Also, what about unplanned failover? Will we also just get the warni

From PC/VMs - select VM - Power Operations - Power onTasks comes back as failed   

HI!Microsoft certificates for Secure Boot expire in June 2026Will AHV, CVM, and VM legacy boot continue to function properly after the certificate expires?Secure Boot expiration will only affect guest VMs using UEFI? 

need to setup on-prem VM setup with our Hardware which is the best one. 

HiI’m looking for guidance on the best practice to upgrade a Metro Availability setup with a Witness VM and would like to confirm the recommended and supported approach.Scenario: Two AHV clusters configured with Metro Availability External Witness VM providing quorum on a third site Prism Central deployed (one per cluster) Upgrade-related questions: During maintenance, is it recommended or even possible to: Temporarily pause or disable the Witness service Upgrade Prism Central Re-enable the Witness afterward Or is this not required / not supported? Can Prism Central be upgraded without impacting Metro Availability, assuming both clusters remain healthy and communication between them is intact? My concern is the following scenario: During a Prism Central upgrade, communication with the Witness is temporarily lost due to the reboot of the VM or the services Both clusters are still communicating correctly with each other all time In that case, should the env

When Adding Cluster in Prism Central getting this error "Failed to perform the operation Register Prism Element during precheck execution due to reason-The remote cluster is blacklisted for registration" 

i have created a root share name as ABC and I have 4 subfolder names as A1, B1, C1, and D1, i have create short cut of all 4 subfolder and it shows to user as root folders.i want to apply disk quota on 4 subfolder names as A1, B1, C1, and D1, please suggest

Hello All,We are trying to deploy prism central on top of 2 node cluster but that prism central fails to deploy at 100%.Error message that it gives - Encountered Exception in post_deployment step: Failed to enable micro services infrastructure on PC: deploy msp:Error deploying addons: failed to deploy monitoring addon: failed to deploy and verify kube-prometheus: failed to verify kube-prometheus: Operation timed out: failed to verify kube-prometheus: expecting 1 available replica of k8s prometheus in ntnx-system namespace. Currently running: 0Trying to get the pods up but that isnt possible.Checked the resources for the hardware and they are also available.Need help to resolve this issueBelow are the versions - AHV - 11.0AOS- 7.5Prism - 7.5Troubleshooting done so far - Attempted to manually bring the affected pods up and runningDeleted the problematic podEnsured all components are configured in the same time zone (UTC – default for Nutanix)

hello,I’ve made rufus stick of the iso.. get stuck on “getting AOS ..”I’ve tried to install via cimc attach dvd and used the iso phoenix file.. get stuck on “getting AOS..”“INFO Getting AOS version from /mnt/iso/images/svm/nutanix.installer package.tar.p00 This may take a few minutes if phoenix is running from BMC”and then you can wait for hours …. all help is welcome.kind regards,johan claes

In our Nutanix environment we have windows cluster with nodes having os 2016 using volume group for sql and file server. Now we are planning for windows os  upgrade from 2016 to 2022.We are planning to create new cluster with windows 2022 nodes and mount the same volume to this new cluster. If it is feasible or not. Any one help on this

Hello All,I am looking for documentation latest field deployment guide for Cisco Nutanix deployment using intersight. I can see last documetn published on Octobe 25 by cisco, in which the 2022 PC have all EOL software bundles. 2024 PC required completed ESXi environment (vcenter serveras well). Is there way to eliminate vcenter server in any of the latest PC which is used for deployment of cisco nutanix cluster. Thanks in advanceThejesh

We are using Nutanix Data protection APIs to compute the changed regions between VM recovery points, where we are seeing in-consistent behaviour. API version - v4.1API First we do discover cluster on Prism central IP - /api/dataprotection/v4.1/config/recovery-points/{extId}/$actions/discover-cluster Then we Compute VM change regions on Prism Element IP - api/dataprotection/v4.1/content/recovery-points/{recoveryPointExtId}/vm-recovery-points/{vmRecoveryPointExtId}/disk-recovery-points/{extId}/$actions/compute-changed-regionsSo for Second request the start offset is provided as 0 to compute the regions from the start. It provides the change regions and let’s say the last offset changed is n. Now when we request the same compute regions API with the start offset n, it stills gives more compute regions which should not be the case as the last request ended the compute regions in n. We check below meta data response for if the response in paginated - isPaginated - flag nextOffset - extraIn

Hello All,We are trying to create disk on a VM from a source VM Disk, It was running fine but after sometime it started to error out with error - VMM-10000:Failed to perform the operation due to an internal error. API Used - /api/vmm/v4.1/ahv/config/vms/{vmExtId}/disksAHV - 10.3AOS- 7.3Prism - 7.3 CVM acropolis logs - 2026-01-29 10:43:36,252Z INFO base_task.py:635 Running task b417bd15-c4e9-4297-6b2d-2830f3afd181(VmDiskCreate 3aac3b95-f5ef-48a5-5db3-fb18647ee0e5)2026-01-29 10:43:36,257Z WARNING client.py:89 CastorRPC returned error 8.2026-01-29 10:43:36,267Z INFO base_task.py:775 Task b417bd15-c4e9-4297-6b2d-2830f3afd181(VmDiskCreate 3aac3b95-f5ef-48a5-5db3-fb18647ee0e5) failed with message: RPC GetVolumeDiskPath forwarded to Castor failed with error Unknown volume disk 8c3cadcc-6cf3-4749-9447-0a8078913db0Checked the Source Disk ID  8c3cadcc-6cf3-4749-9447-0a8078913db0, it is correct in the infra and Source VM Disk is shown on acli VM Disk list.Check Cluster health status -   ncc healt

Hi everyone,I have a problem.The disk types in the Nutanix cluster are SATA SSDs and HDDs.ODF disks have been added to the worker nodes for the OpenShift cluster creation. SCSI was selected as the bus type, and all-flash was selected. Despite these selections, when checking within the OS, the ROTA value shows 1. In other words, the OS is recognising the disks as HDDs.  The ROTA value must be 0; the disks need to appear as SSDs. Does anyone have experience with this? How can I fix this at the Nutanix or OS level to ensure a correct connection between the VM and the hardware?  

Facing issue when we install or configure 7.3 with Foundation 5.9 getting error and not reimage on Nutanix box NX-3060-G7.     raise Exception("Cannot reach BMC after reset")Exception: Cannot reach BMC after reset2026-01-23 07:36:29,583Z imaging_step.py:123 DEBUG Setting state of <ImagingStepInitIPMI(<NodeConfig(192.168.10.32) @9370>) @95e0> from RUNNING to FAILED2026-01-23 07:36:29,583Z imaging_step.py:123 DEBUG Setting state of <ImagingStepRAIDCheckPhoenix(<NodeConfig(192.168.10.32) @9370>) @9040> from PENDING to NR2026-01-23 07:36:29,583Z imaging_step.py:182 WARNING Skipping <ImagingStepRAIDCheckPhoenix(<NodeConfig(192.168.10.32) @9370>) @9040> because dependencies not met, failed tasks: [<ImagingStepInitIPMI(<NodeConfig(192.168.10.32) @9370>) @95e0>]2026-01-23 07:36:29,583Z imaging_step.py:123 DEBUG Setting state of <ImagingStepPreInstall(<NodeConfig(192.168.10.32) @9370>) @91c0> from PENDING to NR2026-01-23 07:36:29,583Z

Guest has not initialized the display (yet).Operation failed: Internal Exception.VM 起動時です。ついでに  UEFI Secure Boot だと  Operation failed: Internal Exception. です。このログみればいいよ～とか、このコマンドを cvm で叩いてみてくれとか、見当がつきません。CEAHV 10.3.1.1AOS 7.3.1.1

Hi All,I have Dell power edge R760 server with loads of RAM and Storage. My plan is to configure this as single node cluster.is there any limit for number of Virtual Machines per single node cluster? I read that maximum 5 VM’s only allowed in single node cluster. is this true?

I’m looking at trying Nutanix, I was orginally on ESXi with a Dell PowerEdge T340, I’ve since migrated to Proxmox.I’m in the process of reading documentation and reviewing etc.  I currently have 4 x SSDs in the unit with 64GB RAM installed.  I may put an HBA330 in to allow use of the other 4 drive bays.  I have a spare BOSS card too that I’ve not used.Does anyone have Veeam CE Edition v13 appliance working with Nutanix?

Hello Nutanix Community,I’m reaching out for help after spending a significant amount of time troubleshooting an issue where a Nutanix cluster cannot complete initialization. I would truly appreciate any insight from the community, as I believe I have exhausted all standard troubleshooting paths.This cluster was previously created successfully and had been running in production without issues.However, due to security-related changes in our IT infrastructure, we were required to re-address the entire environment, including: CVM IPs Hypervisor IPs IPMI IPs Because of this requirement, I intentionally chose the cleanest and officially recommended approach, which was: Reclaim licenses Stop the cluster Destroy the cluster Rebuild the cluster from scratch using Nutanix Foundation This was not an accidental failure during a first-time installation.The issue only started after performing a controlled teardown and reinstallation due to the IP address changes. Support experience and re