Andreas Tanz wrote:
[ 3732.020033] returning from kvm_handle_exit, cause 3, retval = 1, exit_reason = 7
Here, vmx tells us that the guest is ready to accept interrupts (having
executed the sti instruction)
[ 3732.020044] vmx->vmx_vcpu_run() 00 : vmcs_read32(VM_ENTRY_INTR_INFO_FIELD) returned 0x80000408
... noticing that, kvm injects a timer interrupt that was previously
blocked ...
[ 3732.020056] vmx->handle_exception 00 : giving some infos
[ 3732.020062] vmx->handle_exception 01 : vect_info: 0x0
[ 3732.020067] vmx->handle_exception 02 : intr_info: 0x80000b0d, is_page_fault()==0
... and the Nano rewards us with a General Protection Fault instead of
injecting the interrupt.
Will talk to the specification and come up with further tests.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
--
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
