Must install on ESX, any chance?

[Proximate]

Unfortunately, I simply cannot remember now. I spent a couple of days on this trying variations of things I was reading.
I did install proxmox onto esx but don't recall if I enabled nested virtualization or not. If it was suggested, I probably did if it was an option.

However, I don't know what point I got to where I decided I had to work with a real physical proxmox host and at that point, I was able to get through a complete stage. I posted what worked for me in case it can help someone else in another thread.

 

[apoc]

I did install proxmox onto esx but don't recall if I enabled nested virtualization or not. If it was suggested, I probably did if it was an option.

PVE will likely work without nested virtualization. It uses Qemu the AFAIK and emulates things. That makes things damn slow and unusable.
To use KVM you need to have VT and therefore nested virtualization support.
When I did it that was not available through the UI. You needs to manually edit the VMX and first unregister the VM, because otherwise the settings were reset on my end.

 

[bbgeek17]

I am not sure if a patch level is required, but in 6.7 this is all you had to enable in VM Options under CPU

---

Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[apoc]

Impressive.
That has been improved a lot.
My experience is from 6.5 iirc

 

[janssensm]

I'm not sure if I'm looking for Nested Virtualization since it's the host itself that doesn't have VT enabled.

So if production is needing virtualization layers, it's hardware is misconfigured right now.
A production system that can't be rebooted is misconfigured too.
If you cannot change settings on the host as it is right now, nested virt won't work, or it real be real slow.
Every system needs maintenance, one needs too include maintenance into budget, not erase it. Just saying.

Nested virt is great because you can test almost like real world.
But at the moment you seem to be running circles around a system that doesn't meet your requirements.
So there's two options: adjust the host (probably including a reboot) or get yourself hardware that meets requirements and with witch you can test and experiment.
Time is money too, you know (i'm not a fan of this phrase, but in this case it may be an argument towards your management)

 

[Proximate]

If you are writing to me janssensm, I just went ahead and fired up a server so I had a real environment and it worked out well.

Like all new technology, lots of learning but I'm enjoying proxmox so far. Definitely will be buying licensing if I start using it in production at some point. Love supporting alternatives. I'll start running a couple of servers regularly and see how things go as we move some resources away from vmware. I see us using both.

 

[janssensm]

@Proximate Yes I was, nice to read that you got progress and also take time to learn, that's important too.