Welcome to the MongoDB Community Forums @Bora_Kayalar !
Yes, the issue is about the CPU support that is available within the environment that mongod is running in.
Your Intel(R) Xeon(R) CPU E5-2690 looks like it should have the right feature support, but as @chris mentioned virtualisation layers can affect the CPU features that are exposed.
I do not see the AVX extension which is required for the MongoDB 5.0 server binaries in your CPU info output. MongoDB 4.4 runs without issue because those server binaries are compiled for older microarchitecture targets.
As a quick test to confirm if the MongoDB 5.0 server binaries should run in your hardware environment before investing further time in VMware investigation, I would try running a 5.0 mongod directly in the host environment. You could use tgz/zip downloads instead of the packaged installers to minimise any installation artifacts (i.e. unpack tgz/zip download and run in a test directory, then remove after testing).
What are the versions of O/S and VMware for your host environment?
If you happen to be using a Windows host you may need to disable Hyper-V. There are similar issues with VirtualBox: HMR3Init: Attempting fall back to NEM (Hyper-V is active) - virtualbox.org.
Normally Hyper-V blocks Virtualbox. Hyper-V is a type-1 hypervisor, which accesses the hardware first before any OS runs, and therefore interferes with other programs that need “virtualization technology”, like Virtualbox, which is a type-2 Hypervisor.
Regards,
Stennie