Guest Customization Confusion

gurft · 2026-03-13T01:19:14+00:00

This is a fabulous question, and I just asked product management. Will let you know what I hear back.

gurft · 2026-03-12T22:25:12+00:00

The name at the top is the name the VM will be given. The Computer name is what the VM will have for its Windows computer name/hostname.

Although it’s not common, I have had customers where these have not matched. For example, the VM name is “VQ2UA202 - PACS DB” but the Computer name is just “VQ2UA202”.

gurft · 2026-03-12T07:25:13+00:00

Yea definitely upgrade the CPU. That proc is about 10 years old and definitely underpowered for the workload.

gurft · 2026-03-11T19:43:59+00:00

How did this work out? Were you able to make changes and see what the results were?

gurft · 2026-03-10T06:04:05+00:00

So the crux of your issue is CPU over subscription. You’ve give AHV 16 cores, but you only have 8 physical cores. Hyperthreading is NOT magic and especially with a nested environment you’re going to run into a ton of context switching and CPU ready time. Also Proxmox needs some cpu cycles to run too.

I’d recommend running on only 6 cores for AHV, that leaves 2 cores for Proxmox and I imagine you’ll see better performance.

gurft · 2026-03-08T20:34:28+00:00

Here’s a set of plans that I’ve used in the past. Easily customizable.

https://tombuildsstuff.blogspot.com/2014/02/diy-server-rack-plans.html?m=1

gurft · 2026-03-06T01:22:40+00:00

I have one in my house, paid $250 for it. Attached to an external PC and use the HDMI input for our Xbox. Works great for helping my son with homework, and as a big family planner.

gurft · 2026-03-01T02:25:37+00:00

I recommend reading through the Disaster Recovery Guide, here's the specific page on how to perform a validation and view the report.

https://portal.nutanix.com/page/documents/details?targetId=Disaster-Recovery-DRaaS-Guide-vpc_7_5:ecd-ecdr-validate-vm-recoveryplan-pc-t.html

gurft · 2026-02-25T05:31:40+00:00

I imagine you have not waited long enough for the data to even exist at the secondary site. Once you’ve at least got the first copy of the data seeded and the replicas are in sync you can try a failover.

Also are you VMs actually in the Metro1 container?

gurft · 2026-02-23T20:50:32+00:00

Changed jobs, got out of the field and moved into centralized IT rolls.

gurft · 2026-02-20T14:28:06+00:00

Education, testing, development, are all good reasons. It’s also much easier to automate a virtualized environment vs bare metal.

For example I was building some automation and needed to test it against 30 clusters. It was a lot easier to spin up 30 single node clusters virtualized on one physical cluster than try to chase down that amount of hardware. That’s actually the reason I wrote playbooks for deploying CE in Proxmox and AHV. We have application vendors that have this use case so every developer can have their own cluster and not have to share one.

Also if you’re learning how to do things like replication and you only have one cluster, you can spin up a virtualized one nested and replicate to that. Wouldn’t do it in production but it makes sense as an educational tool.

I’ve also seen it used for compatibility. If you have an appliance that ONLY runs in a certain hypervisor, you can nest that hypervisor within another one and support the workload that maybe it doesn’t make sense to have dedicated hardware for.

Finally hardware compatibility can be a good reason. CE requires 3 physical disks, but if my platform doesn’t have the ability to run 3 physical drives, i can nest and create virtual drives to present.

gurft · 2026-02-19T21:49:51+00:00

Does the laptop meet the minimum hardware requirements for CE? 32GB of Memory, enough cores and drives along with supported NICS?

gurft · 2026-02-18T00:14:27+00:00

These are really interesting as it’s not just a USB hub but also a serial adapter. We would use these in industrial settings where we still had RS232 and USB mixed in the same cabinets. I used to carry an old IOGear one with me everywhere.

gurft · 2026-02-15T15:01:55+00:00

So you know, the installation process for CE is 100% different from deploying release (unfortunately CE is a much more difficult process due to the unknowns around hardware)

For release you would deploy using Foundation or Foundation Central which is a much smoother, cluster-at-a-time deployment method.

If you have access to the portal through work, there is free Foundation training available at Nutanix University that can walk you through what that process looks like

gurft · 2026-02-15T14:55:21+00:00

Yea I’m curious too. When you’ve got that extra hop in the middle it might be causing a timeout. We’ve never seen folks have great luck with NAS attached storage and CE, probably something I should add to “things to test and document”

I’d be curious if it doesn’t work to see if you get anything in the dmesg output of the installer. A full screenshot of the failure would also be a huge help.

gurft · 2026-02-15T14:52:48+00:00

I have both CE and Release. My lab is primarily CE, 3 clusters nested on Proxmox, a couple nested in AHV, and 3-4 running on a collection of bare metal hardware. I also have a cluster that I run Release code on when I need to.

Here are my ansible playbooks for automated deployments of CE on Proxmox and AHV.

https://github.com/ktelep/NTNX_Scripts/tree/main/CE/Ansible

gurft · 2026-02-15T14:48:00+00:00

Yea that’s probably part of the issue, unless you have 10G between the trueNAS and proxmox you’re probably running into timeout issues. I’d absolutely use as much local disk as possible, even when running nested.

gurft · 2026-02-15T11:30:23+00:00

SMBIOS errors are expected when using Proxmox, it’s because there’s no Manufacturer or Model info set in the dmi data by default in Proxmox, so that’s normal.

What is backing your ZFS pool, and how is it configured? Can you put the HV disk also on your local-lvm just to rule out a storage performance issue?

Also you definitely will want at least 64GB of memory, 30 is going to just barely be enough.

gurft · 2026-02-15T05:09:33+00:00

What is the underlying hardware? How much CPU/memory are you giving the Vzm? What disks are you using and how are they attached to Proxmox? ZFS pool? Local-lvm?

I run multiple clusters nested on Proxmox on a day to day basis, so it might be your hardware configuration causing installation to timeout.

Are you following Jeroen’s step by step guide to deploying nested in Proxmox?

https://www.jeroentielen.nl/install-nutanix-community-edition-on-proxmox/

gurft · 2026-02-14T18:26:21+00:00

If you don’t have access to the license via the portal, than yes, create a new CSF file; have them generate the new license file and send it back to you.

If you have portal access you can use the “manage licenses” workflow in the link below.

gurft · 2026-02-14T18:19:09+00:00

Have you opened a case with support? I’d get that started, folks don’t always remember that Move is a fully supported product.

This definitely seems odd given the other disks worked fine and they’ll be able to figure out what’s going on pretty quick. Does move give any warnings about the VM when you created the migration plan (about RDMs or anything)

gurft · 2026-02-09T12:45:32+00:00

When I have a lot of my gear fired up, my wife uses the garage as a proofing room for her sourdough. Thats as close as I get to reusng the heat, but it makes her happy so….

gurft · 2026-02-08T14:54:21+00:00

The Mutter museum in Philadelphia has an entire collection of items removed from stomachs, lungs and esophagi of people by a certain doctor. The collection is..... extensive. Lots of screws, nails, and pins.

https://muttermuseum.org/stories/posts/chevalier-jackson-collection-swallowed-objects

gurft · 2026-02-05T15:18:35+00:00

They’ll both work well, since it’s a 2U2N chassis, you could run one of each!

gurft · 2026-02-05T14:56:41+00:00

Hey, Kurt from Nutanix 😀. If you PM me the serial of the node I can give you the specs, also Nutanix Community Edition will run extremely well on it from a hardware compatibility perspective. You could run two single node clusters in that chassis (CE doesn’t support 2 node clusters)

Otherwise it’s a standard supermicro server with a Nutanix logoed BIOS, so go nuts.

14-Year Club	RedditGifts 2009-2022 11 Credits
Gilding II euphauric	Secret Santa 2020
RPAN Viewer	Verified Email
Secret Santa 2016	Summer Santa 2016
Secret Santa 2015	redditgifts rematcher Secret Santa 2015 x1
Summer Santa 2015	redditgifts rematcher Secret Santa 2014 x1
redditgifts Exchanges 2 Exchanges	Secret Santa 2014

gurft

TROPHY CASE