Nested virtualization not being activated on vSphere/VMWare v7.0.2See original GitHub issue
As a proof see this pic
The highlighted checkbox should’ve been checked.
This happens when we’re creating/rolling a K3s cluster with
kcli create kube k3s .... and the following parameter
nested: true has been set in X KCLI plan file.
I checked the code for the provider > https://github.com/karmab/kcli/blob/2c20f402a8bd3adb649be8b5ded59fd6371a1965/kvirt/providers/vsphere/__init__.py#L536 and it looks fine - according to > https://vdc-repo.vmware.com/vmwb-repository/dcr-public/723e7f8b-4f21-448b-a830-5f22fd931b01/5a8257bd-7f41-4423-9a73-03307535bd42/doc/vim.vm.ConfigSpec.html - search for nestedHVEnabled.
I’m pretty sure my former colleague raised this a while back. Finally got around to mention it … as I’m rolling clusters up and down these days … so bumping into it again and again as we need nested virtualization enabled on certain clusters.
Looking forward to hearing what this could be.
- Created 2 years ago
- Comments:5 (5 by maintainers)
Top GitHub Comments
The PR was merged and accepted and I’ll therefore happily close this issues as resolved.