Nutanix Cloud Infrastructure

migration de vm vers nutanix 

has anyone else seen this issue?  We have a Azure NC2 cluster (not in prd yet) and have been notified that we could face the following issueWe would like to inform you about a recently discovered issue where inconsistent CPU microcode configuration will affect the ability to live migrate VMs (internally tracked as ENG-723026). This arises when a Nutanix cluster is upgraded to AHV versions 20230302.103003, 20230302.102005, 10.0.0.1, or 10.0, followed by cluster expansion or node replacement. In such cases, live migration of newly created VMs will encounter issues. Our records show that your Nutanix Cloud Cluster is susceptible to this inconsistent CPU microcode configuration. For details on the action, you can take to remediate, please refer to this Knowledge Base Article. If you have any questions or require assistance, please feel free to open a support ticket.   Anyway I planned on doing the  upgrade to the fixed version in the AHV 20230302

Hi, we have a new Nutanix Cluster with three nodes. Now we will move our citrix farm from VMware to Nutanix.But on Nutanix the VMs much slower as on VMware. We use publish desktops with Citrix MCS an Fslogix.Login with VMware takes 15 seconds with Nutanix more that 50 seconds.The Nutanix Hardware much better then on Vmware.So we don‘t understand why it is so much slower.Also we use the Best Practice Guide from Nutanix for Citrix MCS.so have anybody an idea, why Citrix is slower on Nutanix and what we can do to speed up the system? 

we need  plan for deploy Stretched cluster with Cisco hyperflex C220 M6 Rack server with Nutanix AOS and vmware ESXi

How can I set a UEFI default resolution using the API to create a vm?

Hi thereI am trying to patch some settings programmatically, for example the virtual IP of the cluster, but i encounter an interesting issue with the E-Tag mismatch although i am sure it’s right.Here is my function:def update_vip(cluster_name, cluster_uuid, old_vip, new_vip, api_credentials, pc_endpoint) -> None:"""This function is updating the VIP of the cluster@param cluster_name[str] -> this parameter is the name of the cluster@param cluster_uuid[str] -> this parameter is the UUID of the cluster@param old_vip[str] -> this parameter is the current VIP of the cluster@param new_vip[str] -> this parameter is the new VIP of the cluster@param api_credentials[dict] -> this parameter is the API credentials used to connect to the cluster@param pc_endpoint[str] -> this parameter is the endpoint of the cluster

Please provide the download link for Community Edition

It seems to be the case that no category and value can be applied to the PCVMs.Is that true and if so, will that be altered in the future?If not this causes some unexpected challenge. Thank you

We have a couple of VG’s with 20’ish disks in each, on our 4 node AHV (AOS 6.10.1) cluster. 1 VG is shared with 2 SQL boxes in prd and the other with 2 SQL boxes in our pre environment.  I was patching the environment today with a BIOS update so the hosts needed to be restarted for the update to apply, I had a report from our DBA that they lost connection to the shared disks from the SQL boxes.  What is the expect behavior for VGs with shared disks when a host is unavailable due to a planned or unplanned outage? 

Hi All, I wanted to change VM UUID due to some technical reason, could you please help me for the same. Regards,Ratnakar

How to get Nutanix AHV software's(NOT CE) and trail licenses?

Trying to install latest version of AHV with Foundation (latest ) We get the below error 2025-03-21 07:03:27,122Z environment.py:542 INFO Registered new host with alias '10.8.12.31'2025-03-21 07:03:35,430Z dell_idrac9_redfish.py:209 INFO platform: 14G Monolithic2025-03-21 07:03:35,438Z remote_boot.py:295 INFO Selected tartarus remote boot implementation idrac9 via <Bound command## IDRAC9Redfish instance at 0x230e8e71fd0>2025-03-21 07:03:35,654Z cache_manager.py:133 DEBUG Cache MISS: key(get_md5sum_('C:\\Program Files (x86)\\Nutanix\\Portable Foundation\\tmp\\sessions\\20250321-123220-5\\phoenix_node_isos\\foundation.node_10.8.72.33.iso',)_{})2025-03-21 07:03:38,516Z dell_idrac9_redfish.py:209 INFO platform: 14G Monolithic2025-03-21 07:03:41,289Z dell_idrac9_redfish.py:396 INFO BIOS settings do not match expected values, updating configuration for {  "CorrEccSmi": "Disabled",  "IoatEngine": "Enabled",  "MemoryMappedIOH": "1

Is there any resolution to the "svm failed with reasons (None)" error during install using foundation 

Hi, Hello,Am looking for help on snapshots and reverting to recovery points. Is my PC GUI fully equipped to handle snapshots and restore to snaps? sometimes for some vms it works and it doesn't for for few other vms. as a workaround we were asked to do it via CLI. though this may get fixed in later versions, any RCA on why this happens? am on AHV 6.x version.Are these snapshots work exactly like the snapshots from VMware or is it different?

Can I please get the Community Roll. I am trying to get going on my Nutanix cluster and I get this error.   

Hi,I am confused by information in the prism central infrastructure guidePrism pc.2024.3.1 - Defining Behaviour for Non-migratable VMs (GPU/CPU/PCI/Host Affinity configured VMs)non_migratable_vm_action: By default, this parameter is set to block, which means the non-migratable VMs are shut down when you put a node into maintenance mode. For more information on non-migratable VMs, see Non-Migratable VMs.If you want to automatically shut down such VMs for the duration of the maintenance mode, set this parameter to acpi_shutdown.It seems both settings result in shutting down the VMs. Am I missing something, or is there an error in the documentation? I assumed block

Please help me here.I am unable to deploy the prism central. Prism Element is not compatible to enable Microservice Infrastructure: cmsp domain ltimindtree.com name already in use, Domain name must be atleast 3 sub domain long    

Team, Looking for Nutanix Partner Presentations download section, please share the right Location and URL to access the same.

When configuring a protection policy for synchronous replication between two Nutanix on-premises availability zones (AZs) without utilizing a witness VM, under the Failure Detection Mode setting, in what scenarios should Manual Mode be used, and when is Automatic Mode recommended and that related to witness service?  

Hi,Use Case: I have a POC account on which I want to launch a NC2 cluster using my Azure account.Problem Statement: I am able to create an azure cloud account successfully but when I try to create a cluster, it does not let me use my azure account and depicts that my aws trial account is still active. Question: How can I activate Azure trial license in my POC account? Can I use my azure trial license if I have already used AWS trial?

I checked the log rotation interval for CVM and Prism Central in the manual, but I couldn't find any information.With the default settings, how often are logs rotated, and how many generations of data are retained?

I am considering building a cluster that will use a mix of TLC and QLC NVMe SSDs. I assume that Nutanix will put all of these drives into the SSD-PCIe storage tier and every disk will be a member of the same tier. Since QLC SSDs have lower performance and lower write endurance than their TLC, MLC, and SLC counterparts, it would be advantageous to use storage tiering to encourage cold data to reside on the QLC media and hotter data to reside on the more performant drives. Is there a supported method for this in non-community edition clusters? It would be relatively straightforward to manually change the tier-name for the QLC drives to SSD-SATA, but is that a supported practice?

Hi everyone,anyone face issue, when they run nutanix collector to gather data of PC or PE, but when we open the excel file. we got required data except VM IP details.can anyone resolve this or have any solution to this. without VM IP details, collector is not worth. Please share thought about it.

If I have two AHV clusters distributed across a primary site and a disaster recovery (DR) site, and I configure Metro Availability between them, is it possible to deploy the Witness VM at the DR site?

I have 2 AHV clusters (3 nodes), and if I want to configure synchronous replication between them, I have two options: Sync Replication and Metro Availability. I would like to understand the key differences between these two approaches and the specific features. Note that I will not use a Witness VM.