I'm seeing an issue with MCS provisioned persistent machines being created with the main disk on the selfservicecontainer rather than the container specified. The source image/snapshot is on the desired storage container (granted I moved it there as it was on the selfservicecontainer originally) and the identity disk is getting created on the proper storage container. Is this an artifact of the source machine originally being on the selfservicecontainer?

I need to move our Gold image VM from one cluster to another - easy enough with a protection domain (can't do it with PC due to reasons). However, that only brings the current VM, not the previous snapshots. Is there an easy way to bring the snapshots along as well? My thought currently is to revert the image to each snapshot desired to be kept, and protection domain snapshot it and then restore as a separate VM in the unlikely event we need to use it. Was hoping there would be a cleaner way to move the VM along with all of its snaps.

Here’s a demo of Nutanix Files VDI Sync for your EUC profiles and user data.

https://www.reddit.com/r/nutanix/comments/1kzqgr4/netapp_as_external_storage/ Anyone?

Has anyone tried to run a Nutanix Vm and load the IGEL software? I am trying to setup a lab device to test with and Nutanix runs our Lab. When I mount the ISO I get to the Standard Installation + Recovery screen and choose that, it then boots to this screen and I cannot see anything. Is it possible to do this?

.NEXT on demand sessions - https://www.nutanix.com/next/on-demand

Big release of the Nutanix Packer Builder today - lots of goodies for EUC workloads https://jkindon.com/deploying-euc-images-with-packer-and-nutanix/

Attempting to create a Windows 11 VM on my new Nutanix CE lab that I recently stood up, which runs on generic NUCs with Intel CPUs. I ran into the e1000 nic issue, so used acli to add an Intel NIC and also the vTPM, and checked machine type is set to Q35. If I boot the machine in UEFI mode, and untick Secure Boot the VM will boot and starts setup, but states system requirements aren't met (which you'd expect). If I tick the Secure Boot setting, the VM boots but hangs at the "Press F2 for EFI" screen. I haven't found any workarounds to this - has anyone run into this and know a resolution?

Next challenge. After updating everything to latest versions through LCM (AOS 7.0.1.6/AHV 10.0.1.1), I can no longer boot any of my VMs at all. The issue looks to be same as this one described in the forum post here, I fixed the maxmem issue by editing the qemu-kvm-frodo script but the VMs then hang at the console with "Guest has not initialized the display (yet)". I am wondering if something in this latest AHV version has removed support for my CPU (Intel Core i9-11900H). VMs won't power on - QEMU error | Nutanix Community

I have a small 4 node cluster that has crossed the storage threshold for node failure tolerance. When the cluster was built, ALL of the persistent VDIs were created on the self service cluster with no compression or dedupe. In order to prevent excess cpu utilization, I've been moving VMs to a different container that has compression/dedupe enabled. This is very, very slow as I can only do 3 VMs at a time, and it takes hours to complete. Can I safely enable post process compression (and dedupe ideally since it's all persistent vdi) on the self service container and have it compress the data without impact to the cluster? There are about 130 VMs in the container, with ~50GB of data each. If I can do it 'safely while monitoring' what would be my 'stop it' fix if it does begin impacting things? This cluster is for RPA bots so it stays around 40% cpu all the time with normal load, so there's no benefit to doing it on a weekend or during off hours.

set the channel topic: Nutanix employees in this channel: Jarian Gibson, Kees Baggerman, sven James Kindon and Dave Brett

set the channel topic: Nutanix employees in this channel: Jarian Gibson, Kees Baggerman, Sven Huisman, James Kindon and Dave Brett

Because my OCD went crazy 👆🏻

Now put them in alphabetical order...

For those with Nutanix CE labs on non-Xeon CPUs, I got a response on the forums re some of the recent changes. It's a long post but here is some of the key info. Full post at VMs won't power on - QEMU error | Nutanix Community What Changed in AHV 10.x? Nutanix AHV 10.x Enforces "Server-Class CPU Compliance" Starting with AHV 10.x, Nutanix hardened the VM launch pipeline to: • Explicitly validate CPU capabilities against enterprise server-grade specs (e.g., Xeon or EPYC-class), • Enforce minimum physical address bits (typically ≥ 46) during VM memory allocation. This is not a documented behaviour change in public-facing PDFs, but it's implied in internal support KBs and developer-level discussions. Consumer-grade Intel CPUs (like your i7-10710U) only expose 39–42 physical address bits depending on firmware microcode. AHV 10.x+ now expects 46–52 bits, in line with Xeon-class processors. Root Technical Impact In AHV 10.x: • qemu-kvm now fails fast when attempting to allocate maxmem values above what your CPU can theoretically address. • The error: • phys-bits too low (39): 61 • qemu-kvm: Address space limit 0x7fffffffff < 0x4bcbfffffff This is not just a warning, it's now a hard stop, unlike in AHV 2023.x which was more lenient or silently clamped memory ranges. What Are Your Options? If you want to stay on AHV 10.x: • Patch VMs to lower maxmem manually for each. • Limit to smaller memory footprints, ideally ≤ 16GB per VM. • Disable ballooning and dynamic memory reservations. But expect to continue hitting issues due to subtle QEMU/kvm flag incompatibilities. If you're testing/dev only: • Consider reverting to AHV 2023.x (AOS 6.6 or 6.7) where QEMU was more forgiving. • Or switch to Nutanix CE, which has relaxed CPU checks and allows more override flexibility. If you need long-term compatibility: • Move to Xeon-D or Xeon-E3 based NUCs, like the NUC Enthusiast series or Supermicro MicroCloud nodes (widely used in labs). You're correct that this isn't a BIOS issue, this is a design hardening in AHV 10.x. The InternalException masks what is really a low-level qemu-kvm memory init panic, and it's now unrecoverable on consumer CPUs. Your workaround on maxmem works but not sustainable unless you're using AHV in an unsupported/lab environment, which Nutanix won’t provide roadmap support for.

If I initiate an action/task in Prism Central, does it not show as a running task on PE? I see in the PE gui there are 3 running tasks, but when I connect via Powershell, the get-ntnxtask command shows nothing running

Anyone had any success with hosts using realtek network cards on CE? I keep having wierd issues with one host that uses realtek network card, but the other nodes are fine

Folks, I recently helped a customer deploy a bunch of Windows 11 24H2 persistent VDI machines on Nutanix. All was working ok but they have done a load of hardening (CIS, GPOs, Defender blah blah). Now when they add new machines, they register and blue screen shortly after. Looks to be caused by Hyper-V (not installed) trying to call VMX/Security features. They can workaround by disabling Hyper-V services but Id like to fully understand. Does anyone have a link to a blog/article that explains Win11 via Citrix on Nutanix that details key settings/Do's and don'ts around TMP, Secure boot, UEFI, cred/dev guard settings etc? cheers

Hello everyone.

https://download.intel.com/newsroom/2025/client-computing/Intel-Arc-Pro-B60-Data-Sheet.pdf ... "Ensure reliable, precise performance for common AI, design, engineering, architectural, and manufacturing software with a workstation-focused, validated, and robust graphics driver. Paired with trusted ISV (Independent Software Vendor) certified" Sounds VDI-ish, but last I checked it's Citrix-only for Intel on VDI?

What homelab equipment is everyone using for their Nutanix labs?

Our lab was connected to Prism Central. Our administrator went through the work to get it setup as an Azure AD EntraID domain, which changed usernames etc. In the process, our LDAP authentication for Prism Central was broken, and logins to Prism Central GUI ceased. After much troubleshooting, I made the decision to just redeploy Prism Central. I went through the decommissioning as suggested and removed the lab cluster from the old Prism Central. Now, I cannot re-add it unless I call support, which I cannot do because it is CE. Is there anyone who can help me get the blacklisted removed from the lab cluster so we can reconnect it to the new Prism Central?

Hey guys - have you ever seen a problem where Citrix MCS fails to create machines, when creating catalogs on AHV? Small batches work, but anything larger than creating 20+ machines seems to fails, or there are missing machines along the way. I’m just starting to research this for a customer. My initial thoughts were to update the AHV plugin on the Controllers. But curious if others have seen this, and if it’s a known issue with certain versions, or specific cluster configurations. Customer was using AHV plugin 2.7.1.0 at the time.

Anyone using Pure Storage with Nutanix AHV to deliver Citrix MCS desktops? We're floating the idea of moving away from HCI storage on NX3155 G9's. The local storage has been good to us, but management is convinced the future is to transition to a Pure Storage unit.

Is it true that Nutanix AHV does not support MCSIO. It's my first time creating an MCS image on Nutanix and the settings are not there when creating a Machine Catalog. I found a KB article with a vague statement (or maybe it's just how I read it), but just want to be sure I've not missed something. Cheers

we deleted about 80 or so persistent citrix mcs desktops a week and half ago in our environment and have not really seen our space improve more than maybe 1% (typically we would have seen a decent improvement w/ that amount of cleanup. we use snapshotting on the Central side where we take a nightly snapshot but only keep 2 so we should be well passed that point of purging i would have thought. is there anything that possibly could be stuck and didnt clear old data yet after this amount of time?

Is there any update on vtpm VMs being able to be used with PE protection domains or are PC protection policies the only method, and likely to be the only method?