no handler for some reasons to cause vmexit

* no handler for some reasons to cause vmexit
@ 2014-06-25 13:41 Xuekun Hu
  0 siblings, 0 replies; only message in thread
From: Xuekun Hu @ 2014-06-25 13:41 UTC (permalink / raw)
  To: kvm

Hi, All

For some reasons to cause vmexit (e.g. LGDT, INVPCID etc), there is no
corresponding handler in kvm. So in general, what will the kvm
hypervisor do? Do nothing, and reschedule for next time vmentry? From
guest view, no state changed, right?

Many thanks.

Thx, Xuekun

^ permalink raw reply	[flat|nested] only message in thread