-
1. Re: Nested NSX-V 6.4.6 lab - controller VMs failing to boot (Photon OS boot screen followed by black screen)
Sreec Nov 29, 2019 10:09 PM (in response to bobbyccie)Were are you deploying the nsx controllers ? I'm hoping it's on the nested ESXI and NSX manager is at bare metal server ? . One of the key reason controllers get deleted immediately after deployment is because of network connectivity issue . This being a nested lab , can you ensure connectivity is in place ? MAC learning works fine (Promiscuous mode ) ? Do follow steps @ NSX Controller Deployment Issues
-
2. Re: Nested NSX-V 6.4.6 lab - controller VMs failing to boot (Photon OS boot screen followed by black screen)
bobbyccie Nov 30, 2019 2:40 AM (in response to Sreec)Thanks for the reply but I am still facing issues with the NSX controller VM starting up properly.
The NSX manager and vCenter are running directly on EVE-NG (not inside a nested ESXi host).
Other VMs run fine on the nested ESXi hosts.
I have enabled promiscuous mode on the vSS used for management connectivity but it didn’t help.
It seems to be an issue with the NSX controller VM booting up properly. It gets deployed and started OK but doesn’t progress past the Photon boot screen (console screen stays black) and eventually the VM gets deleted.
As I mentioned, my lab is running on EVE-NG which is using KMV under the hood. Other nested VMs work fine. I guess most people are running nested labs using ESXi on ESXi but I would like to stick with EVE-NG.
I have checked the deployment issues link but didn’t see anything that could be causing it.
Any other hints?
Sent from my iPhone -
3. Re: Nested NSX-V 6.4.6 lab - controller VMs failing to boot (Photon OS boot screen followed by black screen)
bobbyccie Dec 1, 2019 1:25 AM (in response to bobbyccie)After some more testing I think my issue is affecting ANY 64-bit VMs on the nested ESXi hosts (32-bit VMs work OK but as the NSX controller VMs are 64-bit I think that's my problem).
Apparently I need to set 'options kvm ignore_msrs=1' but for some reason this is not surviving a reboot .
I have posted a question here: https://communities.vmware.com/message/2902276#2902276 for help with that.
Thanks all.