I checked the IA32_FEATURE_CONTROL and its value is 5.

So my guess is its somehow the kvm yocto which is not right.



On Thu, Feb 18, 2016 at 4:04 PM, Supriti Singh <[email protected]>
wrote:

> Hello,
>
> I compiled the latest version of yocto with meta-virtualization layer for
> Minnowboard Max.
>
> MbMax have hardware virtualization support,
>
> grep vmx /cpu/procinfo shows the vmx flags.
>
> But when I boot the board, dmesg|grep kvm shows "kvm: no hardware support".
>
> I do see kvm loaded as module. Is there some other settings that I need to
> switch on, so that kvm understands that the hardware has the correct
> virtualization support.
>
> Or could it be just the UEFI thats disabling it?
>
> modinfo kvm-intel gives the following output
> filename:
> /lib/modules/4.1.15-yocto-standard/kernel/arch/x86/kvm/kvm-intel.ko
> license:        GPL
> author:         Qumranet
> alias:          cpu:type:x86,ven*fam*mod*:feature:*0085*
> depends:        kvm
> intree:         Y
> vermagic:       4.1.15-yocto-standard SMP preempt mod_unload
> parm:           vpid:bool
> parm:           flexpriority:bool
> parm:           ept:bool
> parm:           unrestricted_guest:bool
> parm:           eptad:bool
> parm:           emulate_invalid_guest_state:bool
> parm:           vmm_exclusive:bool
> parm:           fasteoi:bool
> parm:           enable_apicv:bool
> parm:           enable_shadow_vmcs:bool
> parm:           nested:bool
> parm:           pml:bool
> parm:           ple_gap:int
> parm:           ple_window:int
> parm:           ple_window_grow:int
> parm:           ple_window_shrink:int
> parm:           ple_window_max:int
>
> Thanks,
> Supriti
>
>
-- 
_______________________________________________
meta-virtualization mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-virtualization

Reply via email to