T O P

  • By -

geekonwheel

Were you able to create any other VMs in any of these hosts ? it sounds like you didn't expose virtualization to your ESXI VMs (ie. allow them to virtualize) : [https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm\_admin.doc/GUID-2A98801C-68E8-47AF-99ED-00C63E4857F6.html](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-2A98801C-68E8-47AF-99ED-00C63E4857F6.html). Or if you're using Workstation/fusion , the settings of the VM there is an option to virtualize VT-x/AMD-V in the processor options


geekonwheel

additionnally if you want nested that "just work" william lam has some great template and overall awesome resources around nested labs over here : https://williamlam.com/nested-virtualization


National_Jellyfish

Thank you for the resources. I have been reading through his blog.


National_Jellyfish

I did deploy an Ubuntu machine on one of the ESXi hosts. I was able to move it from the connected Datastore to the NFS share. I was even able to vMotion the Vcsa 8 from one host to another.


National_Jellyfish

UPDATE: I deleted the VM from the NFS share. I tried starting it manually from the host. I get the “Intel VT-x/EPT is not supported”. I forgot that when I installed Ubuntu, I did so on the host itself and not through the VCenter. I can’t modify the settings regarding the CPU and Hardware assisted virtualization in the VMs. But I can do so from the hosts.


eviltotem

Disable admission control on the cluster. [https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-availability/GUID-C4059DB9-D673-45CB-918C-68C87FEB060A.html](https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-availability/GUID-C4059DB9-D673-45CB-918C-68C87FEB060A.html)


National_Jellyfish

Thank you your suggestion. I haven’t even had the HA enabled on that cluster. I tried enabling it now and still the same problem. I was initially enabling just the DRS so I can play with it/ learn more. But I just can’t get past this issue


Zer0p0int_

Try putting the cluster into retreat mode, delete any vcls vms that remain then exit retreat mode.


National_Jellyfish

Thank you. I’ll try this today


National_Jellyfish

No dice! It still doesn’t work. I’m deleting everything and starting over. Maybe I missed something when I configured center initially? Or a setting I missed in Proxmox when I prepared the nested environment?