VERR_HM_UNSUPPORTED_CPU_FEATURE_COMBO

Discussions related to using VirtualBox on Linux hosts.
Post Reply
Smartboy1986
Posts: 4
Joined: 27. Apr 2021, 14:24

VERR_HM_UNSUPPORTED_CPU_FEATURE_COMBO

Post by Smartboy1986 »

Dear all,

I have a problem cannot start Ubuntu Linux VMDK on VirtualBox. When I start the VM, there is an error "VERR_HM_UNSUPPORTED_CPU_FEATURE_COMBO". Any help how to overcome this error? I can make sure you the machine has VT-x and in active condition.

Here is the snippet of error log:

0:00:00.417077 hmR0VmxSetupPinCtls: Invalid pin-based VM-execution controls combo! Cpu=0x16 fVal=0x1f fZap=0x16
00:00:00.417082 AssertLogRel /home/vbox/vbox-6.0.24/src/VBox/VMM/VMMR0/HMVMXR0.cpp(2800) int VMXR0SetupVM(PVM): RT_SUCCESS_NP(rc)
00:00:00.417085 VMXR0SetupVM: hmR0VmxSetupPinCtls failed! rc=-4112
00:00:00.466905 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={VT-x setup failed: VERR_HM_UNSUPPORTED_CPU_FEATURE_COMBO (VERR_HM_UNSUPPORTED_CPU_FEATURE_COMBO)}, preserve=false aResultDetail=-4112
00:00:00.467090 Console: Machine state changed to 'PoweredOff'
00:00:00.475400 Power up failed (vrc=VERR_HM_UNSUPPORTED_CPU_FEATURE_COMBO, rc=NS_ERROR_FAILURE (0X80004005))
fth0
Volunteer
Posts: 5668
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: VERR_HM_UNSUPPORTED_CPU_FEATURE_COMBO

Post by fth0 »

Please post a complete (zipped) VBox.log file.
Smartboy1986
Posts: 4
Joined: 27. Apr 2021, 14:24

Re: VERR_HM_UNSUPPORTED_CPU_FEATURE_COMBO

Post by Smartboy1986 »

Please see attached complete VBox log file
Attachments
VBox.zip
Complete Log File
(14.93 KiB) Downloaded 11 times
fth0
Volunteer
Posts: 5668
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: VERR_HM_UNSUPPORTED_CPU_FEATURE_COMBO

Post by fth0 »

VBox.log file wrote:
00:00:00.357674 HM: MSR_IA32_VMX_PINBASED_CTLS        = 0x1600000016
00:00:00.357675 HM:   EXT_INT_EXIT (must be cleared)
00:00:00.357675 HM:   NMI_EXIT (must be cleared)
[...]
I don't know your host CPU, because VirtualBox bailed out before writing the CPUID dump to the VBox.log file. But according to its source code, VirtualBox definitely requires the two capabilities listed above, and your host CPU does not provide them.

For completeness sake: What's your host CPU?
Martin
Volunteer
Posts: 2560
Joined: 30. May 2007, 18:05
Primary OS: Fedora other
VBox Version: PUEL
Guest OSses: XP, Win7, Win10, Linux, OS/2

Re: VERR_HM_UNSUPPORTED_CPU_FEATURE_COMBO

Post by Martin »

Vbox 6.0.24 is from July last year, according to the log your Ubunutu is version from this February.
Could you try the current Vbox version 6.1.20?

Also:
00:00:00.014071 Host RAM: 3951MB (3.8GB) total, 1618MB available
00:00:00.062815 RamSize <integer> = 0x00000000f6f00000 (4 142 923 776, 3 951 MB, 3.8 GB)

Your host has only 1.6GB of free RAM available to run a guest VM. Why did you try to assign 100% of your host RAM to the VM?
Smartboy1986
Posts: 4
Joined: 27. Apr 2021, 14:24

Re: VERR_HM_UNSUPPORTED_CPU_FEATURE_COMBO

Post by Smartboy1986 »

fth0 wrote:
VBox.log file wrote:
00:00:00.357674 HM: MSR_IA32_VMX_PINBASED_CTLS        = 0x1600000016
00:00:00.357675 HM:   EXT_INT_EXIT (must be cleared)
00:00:00.357675 HM:   NMI_EXIT (must be cleared)
[...]
I don't know your host CPU, because VirtualBox bailed out before writing the CPUID dump to the VBox.log file. But according to its source code, VirtualBox definitely requires the two capabilities listed above, and your host CPU does not provide them.

For completeness sake: What's your host CPU?
I ran this virtualbox from VPS. So I have nested virtualization here. From lscpu command, here is the specification of host VPS droplet:
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: 63
Model name: DO-Regular
Stepping: 2
CPU MHz: 2494.138
BogoMIPS: 4988.27
Virtualization: VT-x
Hypervisor vendor: KVM
Virtualization type: full
L1d cache: 32K
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 mmx fxsr sse sse2 ss ht syscall nx rdtscp lm constant_tsc arch_perfmon rep_good nopl tsc_known_freq pni pclmulqdq vmx ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm invpcid_single ssbd ibrs ibpb kaiser fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt md_clear
Smartboy1986
Posts: 4
Joined: 27. Apr 2021, 14:24

Re: VERR_HM_UNSUPPORTED_CPU_FEATURE_COMBO

Post by Smartboy1986 »

Martin wrote:Vbox 6.0.24 is from July last year, according to the log your Ubunutu is version from this February.
Could you try the current Vbox version 6.1.20?

Also:
00:00:00.014071 Host RAM: 3951MB (3.8GB) total, 1618MB available
00:00:00.062815 RamSize <integer> = 0x00000000f6f00000 (4 142 923 776, 3 951 MB, 3.8 GB)

Your host has only 1.6GB of free RAM available to run a guest VM. Why did you try to assign 100% of your host RAM to the VM?
I have tried to reduce the guest RAM, but result nothing as well
fth0
Volunteer
Posts: 5668
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: VERR_HM_UNSUPPORTED_CPU_FEATURE_COMBO

Post by fth0 »

Smartboy1986 wrote:I ran this virtualbox from VPS. So I have nested virtualization here.
VPS often do not allow nested virtualization, and if they allow it, then it usually only works when using the same hypervisor as the VPS. Search your VPS provider's help for "nested virtualization".
Post Reply