Intel VT-x is greyed out (only under Linux (Mint) in VMWare Workstation 15.x

Questions about virtualization software
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
TiKay

Intel VT-x is greyed out (only under Linux (Mint) in VMWare Workstation 15.x

Post by TiKay »

Hello, i´m running a dualboot (Linux Mint 19.3 and Windows 10 1903) under different Partitions on my Odroid H2 machine which got an Intel J4105 Processor.
Booted into my Windows System, then creating or running an existing VM under VMWare Workstation 15.5.1, there is the possibility to check and use the Intel VT-x extensions under the CPU settings. This results in great Performance for the VMs.

Booted in my fresh installed Linux Mint 19.3 x64 on another Partition, that option is greyed Out in also VMWare Workstation (even if executed as root)
Only able to check there "Virtualize CPU performance counters".
My abilities as a user are on a level where i can walk through setups and daily use, always find solutions through forums sometimes by combining similarities. Mostly i even learn something for future. This is the fist problem in decades, i don´t even find a clue somewhere.

Most hits i´ ve found by trying to find a solution are telling about turning on the Intel-VT Settings in the Bios (95% of the hits) and by the way - yes i checked that. I even turned it off - rebooted and turn it on again.
Under Windows that results in the behaveior i thought with. Greyed out option when booted with disabled Intel VT. The possibility to switch on "Intel VT-x" was back when booting with enabled Intel VT setting in the Bios.
But booted into my Linux Mint it makes no difference. Always greyed out Checkbox for "Intel VT-x".

Some hits via internet search recommends to reconfigure Windows (Hyper-V, Services, etc) but in Windows it is working as it should on another partition on the same PC.

Somehow i have to bring some more Information but which ones. As i have no clue on what that greyed out checkbox under Linux depends i start by inserting the result of lscpu.

Code: Select all

Architecture:        x86_64
CPU op-mode(s):      32-bit, 64-bit
Byte Order:          Little Endian
CPU(s):              4
On-line CPU(s) list: 0-3
Thread(s) per core:  1
Core(s) per socket:  4
Socket(s):           1
NUMA node(s):        1
Vendor ID:           GenuineIntel
CPU family:          6
Model:               122
Model name:          Intel(R) Celeron(R) J4105 CPU @ 1.50GHz
Stepping:            1
CPU MHz:             2187.411
CPU max MHz:         2500.0000
CPU min MHz:         800.0000
BogoMIPS:            2995.20
Virtualization:      VT-x
L1d cache:           24K
L1i cache:           32K
L2 cache:            4096K
NUMA node0 CPU(s):   0-3
Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave rdrand lahf_lm 3dnowprefetch cpuid_fault cat_l2 pti cdp_l2 ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust smep erms mpx rdt_a rdseed smap clflushopt intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts umip rdpid md_clear arch_capabilities
I appreciate your help and thank in advance.
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
mitchd123
Level 1
Level 1
Posts: 4
Joined: Sat Aug 06, 2016 8:24 pm

Re: Intel VT-x is greyed out (only under Linux (Mint) in VMWare Workstation 15.x

Post by mitchd123 »

Is the issue occurring with VMware workstation under both Windows and Linux? Your CPU support it, turning it on/off requires a cold boot, not a reboot. CPU info shows it's there. Sounds like a VMware workstation issue.
Locked

Return to “Virtual Machines”