Support and News Forum

Hardware:
Intel BXNUC10i7FNH Core i7-10710U 6-Core NUC
32 GB RAM
1TB SSD
2 network interfaces (1 USB).
EVE-NG Running on - Inside vSphere v7.0 (free)- Give it 16GB RAM, 8 cores (it goes up to 12), and 200GB (thin provisoined). No resources are reserved.
VT-X - Enabled, confirmed in vSphere CLI
New install of Eve-NG version 2.0.3-110 from OVA

I installed vMX v18.2R1.9 (vmx-bundle-18.2R1.9.tgz) following the guide: https://www.eve-ng.net/index.php/docume ... 16-x-17-x/ . I create a lab and place either a VCP or VFP or both (if both I connect them). I start either one or both. The VM stops after a few seconds and I have to power it back on from vSphere. If I check the logs /opt/unetlab/data/Logs/ api.txt and error.txt are 0 bytes and I see nothing relevant in access or php_errors. I tried a few other vMX versions and I get the same issue. I have an older Eve-NG VM version 2.0.3-77 that was working fine in another hypervisor, ESXi v6.5 and it a similar thing where attempting to start vMX (v14.1.R1) will halt the VM. Same with vEOS or nexus 9k. I feel I am missing a basic setting.

Hmm this may be platform related vSphere 7 + new NUC.... viewtopic.php?f=3&t=16830

Such was observed with ESXi 7.0 hhen to install it un non supported CPU..
You check is your CPU is in the list of supported CPUs by esxi 7.0

Ouch that sucks . I guess I'll have to rebuild my old Xeon box.

SIR
even you successfully installes ESXi 7.0 on non supported CPU, it does not mean it will work after with all features of vSphere 7.0 after
EVE is working on ESXi 7.0, but esxi must be installed on proper clu box supported by esxi 7.0 !!!