Community edition VM on ESXi 6.7 running on Dual Processor

[mathewfer]

Hi Team,

I posted this viewtopic.php?f=3&t=22162 before but I have the below question still.

Does EVE-ng VM built by your team supports ESXi 6.7 running on Dual processors?
If yes, can you please tell what should be the guidelines for allocating vCPU and RAM on EVE-ng VM?

I my issue, I am either missing something or EVE-ng does not support ESXi 6.7 running on Dual processors.

Thanks

[Uldis (UD)]

Absolutely not true.
EVE VM is byuild on ESXi 8, but set the compatibility starting from esxi 6.5. CPU amount has no matter at all.

Best way to install EVE on ESXi with all your custom stuff, is to do it from ISO.
read EVE CE cookbook, chapter 3.2.1
https://www.eve-ng.net/index.php/docume ... -cookbook/

[mathewfer]

Hi UD,

Thanks for the reply.
I will install the EVE-ng from ISO on ESXi 6.7 soon and update here.

I also found the below during the testing this particular Linux image.

1. When the OVA image of the same Linux image runs on EXSi on the same server with 4 core and 8G RAM, there is no CPU errors for more than 24hrs testing it.
2. CPU errors are only on EVE-ng running on ESXi under Dual CPU. I also added 16 CPUs and 16G RAM in the template setting for the Linux node but it did not help at all. I should say this Linux image is very resource consuming as it runs many services for DevOps.
3. I also noticed Juniper vMX and SRX-ng dropping BGP peers time-to-time which was not the case when this same server were with one CPU
4. I ran the same image on EVE-ng Pro running on bare-metal - different server and there are no issues/ CPU errors.

I am wondering whether there is any changes can be done with QEMU Version, QEMU Arch, QEMU custom options in the template for this image. If so, please let me know.

CPU errors - this freezes the CLI access to this Linux image:

Code: Select all

kernel: [   33.007870] watchdog: BUG: soft lockup - CPU#1 stuck for 27s! 
kernel: [   33.007867] watchdog: BUG: soft lockup - CPU#10 stuck for 26s!

Hope it see it run on fresh install from ISO on ESXi soon.

[mathewfer]

Hi UD,

I installed EVE-ng CE from IOS and the CPU errors disappeared from the nodes but nodes are very bad in response and almost not usable, Then I found the below, same error on EVE-ng host now.

Q, What should the number of "vCPUs" and "Cores per Socket" in ESXi 6.7 for the below CPU configurations?

Dual CPU motherboard, 36 physical cores with Intel Xeon E5-2695 v4. ESXi shows 72 vCPUs, I believe with Hyper-threading - https://www.intel.com/content/www/us/en ... tions.html

The below errors were with 64 vCPUs and 32 Cores per Socket. I did not try any other settings and wondering whether I should try 36 vCPUs and 18 Cores per Socket.

Code: Select all

root@eve-ng:~# cat /var/log/kern.log | grep watchdog
Nov 30 06:38:18 eve-ng kernel: [    0.863223] NMI watchdog: Perf NMI watchdog permanently disabled
Nov 30 07:00:09 eve-ng kernel: [    1.062103] NMI watchdog: Perf NMI watchdog permanently disabled
Nov 30 07:26:37 eve-ng kernel: [ 1601.172018] watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [kworker/2:1:439]
Dec  1 02:54:25 eve-ng kernel: [71670.198031] watchdog: BUG: soft lockup - CPU#43 stuck for 23s! [qemu-system-x86:39626]
Dec  1 04:16:29 eve-ng kernel: [76594.220493] watchdog: BUG: soft lockup - CPU#7 stuck for 26s! [qemu-system-x86:41232]
Dec  1 04:16:29 eve-ng kernel: [76594.244166] watchdog: BUG: soft lockup - CPU#23 stuck for 22s! [migration/23:154]
Dec  1 04:16:29 eve-ng kernel: [76594.284165] watchdog: BUG: soft lockup - CPU#51 stuck for 26s! [uksmd:550]
Dec  1 06:48:14 eve-ng kernel: [    1.043941] NMI watchdog: Perf NMI watchdog permanently disabled
Dec  1 11:50:34 eve-ng kernel: [    1.053959] NMI watchdog: Perf NMI watchdog permanently disabled
root@eve-ng:~#

[Uldis (UD)]

Total overload of your CPU, thats it
ESXi VM cannot hold what you have running on lab..
Especially it is worse way, if you start such as mass start all, it creates bottleneck on your CPU and excuseme 36 vcores are so much here

[mathewfer]

Hi UD,

I am very much confused when you say "Total overload of your CPU". I do not start all the nodes at the same time.

I have already calculated the LAB's RAM and vCPU core requirements from your Excel sheet and it is as bellow.

CPU virtual cores total = 34
RAM MB total = 56832

This server has more than this requirement as it has 72 vCPUs and 128G RAM in total. I have assigned 64 vCPUs, 18 cores per socket and 120G RAM.
I do not understand why EVE-ng VM has got poor responses from the nodes and CPU watchdog errors.

I am without answers and only way will be bare-metal install to test this. I can confirm that there is no hardware issues as all other VMs on this box runs without issues. I tested it after shutting down EVE-ng VM - I do not run all other VMs, except for one Linux VM for management of EVE-ng when running EVE-ng for LABs.

I believe EVE-ng needs proper settings under ESXi for proper functioning and I am unable to work it out.

Can you please let me know the answer to my question posted in the previous post?
Awaiting your reply/ideas to resolve this

Thanks

[rusty725]

What kind of hard drive do you have ?

[mathewfer]

Hi

I use 870 QVO SATA III 2.5" SSD 2TB (MZ-77Q2T0BW) and 1.2T is allocated for EVE-ng

I am still waiting for reply on how to allocate vCPUs and cores per socket - above question.

Awaiting for a reply

[rusty725]

I would suggest not to separate them per socket, but select total number of cores -2 cores (for VM), i.e if you have 60 cores -2 cores =58 cores assign.

[mathewfer]

Hi Rusty725

Thank you for your reply.
I should say I am not very good with Hypervisor and learning ESXi with this home LAB environment.
I am not getting what should be the setting for the EVE-ng. I have the below server spec - CPU and RAM.

Can you please help to work out what should be the setting for CPU settings for EVE-ng VM?

ESXi CPU details:

ESXi-CPU.png

EVE-ng CPU settings - I would like to allocate 64 vCPUs from 72 vCPUs if that possible.

EVE-ng-settings.PNG

Do you mean this as I have 72 vCPUs in total?

EVE-ng-settings-new.PNG