At 10:08 +0000 on 25 Nov (1416906538), Andrew Cooper wrote: > A failed vmentry is overwhelmingly likely to be caused by corrupt VMCS state. > As a result, injecting a fault and retrying the the vmentry is likely to fail > in the same way.
In particular, the guest's privilege level won't change until _after_ the next vm entry has succeeded. > While crashing a guest because userspace tickled a hypervisor bug to get up > invalid VMCS state is bad (and usually warrants an XSA), it is better than the > infinite loop caused by this change, and the non-ratelimited console output it > would cause. > > Signed-off-by: Andrew Cooper <andrew.coop...@citrix.com> Reviewed-by: Tim Deegan <t...@xen.org> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel