Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Nested virtualization not being activated on vSphere/VMWare v7.0.2
See original GitHub issueAs 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.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
i believe https://github.com/karmab/kcli/commit/d95aa56f66130a641eec3ee1f1f1771e42049d9c is the fix, but please confirm
The PR was merged and accepted and I’ll therefore happily close this issues as resolved.