Now I can run an L2 guest (nested guest) using the kvm kernel module of kernel 3.12 However, I am facing a new problem when trying to build and use kvm kernel module from git://git.kiszka.org/kvm-kmod.git: L1 (nested hypervisor) cannot boot L2 and the graphic console of virt-manager hangs displaying 'Booting from Hard Disk...'. L1 still runs fine. Loading kvm_intel with 'emulate_invalid_guest_state=0' in L0 does not solve the problem. I have also tried with different kernel versions: 3.12.0, 3.12.8 and 3.13.0 without success. Can you give me some suggestions? Thank you very much Best, Hai On Thu, Jan 16, 2014 at 1:17 PM, duy hai nguyen <haind93@xxxxxxxxx> wrote: > Thanks, Jan and Paolo! > > Great! It helps solve the problem. > > Sincerely, > Hai > > On Thu, Jan 16, 2014 at 12:09 PM, Paolo Bonzini <pbonzini@xxxxxxxxxx> wrote: >> Il 16/01/2014 17:10, duy hai nguyen ha scritto: >>> Dear All, >>> >>> I am having a problem with using nested EPT in my system: In L0 >>> hypervisor CPUs support vmx and ept; however, L1 hypervisor's CPUs do >>> not have ept capability. Flag 'ept' appears in /proc/cpuinfo of L0 but >>> does not show in that of L1. >>> >>> - 'Nested' and 'EPT' are enabled in L0: >>> >>> $cat /sys/module/kvm_intel/parameters/nested >>> Y >>> >>> $cat /sys/module/kvm_intel/parameters/ept >>> Y >>> >>> - The libvirt xml file used in L0 has this cpu configuration: >>> >>> <cpu mode='host-passthrough'/> >>> >>> - The kernel version I am using for both L0 and L1 is 3.9.11 >> >> Nested EPT was added in 3.12. You need that version in L0. >> >> Paolo >> -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
