Well you can execute certain instructions in the guest, which will cause an unconditional VM exit. Instructions such as CPUID, GETSEC, INVD, XSETBV, INVEPT, INVVPID, VMCALL,2 VMCLEAR, VMLAUNCH, VMPTRLD, VMPTRST, VMREAD, VMRESUME, VMWRITE, VMXOFF, and VMXON will cause VM exit when executed in VMX non root operation.
Or else you can use instructions that cause conditional VM exit based on VM execution controls. (CLTS, HLT, IN, OUT, LGDT, SGDT etc...) . The VMCS can be configured to have specific instruction executions to cause a trap. It all depends on your design. i.e. why you need the unconditional trap and what does the guest expect the hypervisor to do, after vmexit. thanks Vivek On Fri, Nov 23, 2012 at 10:29 AM, R <1989012...@gmail.com> wrote: > > Hi, everyone > > Is it possible to force a guest OS be trapped into KVM just like vmexit > does. > Can anyone tell we where to start looking? > > -- > Thanks > Rui Wu > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
