Andreas Tanz wrote:
--> dmesg :
[79116.175571] returning from kvm_handle_exit, cause 3, retval = 1, exit_reason = 0
That's an exception or nmi. Next step is to instrument
handle_exception() and see what happens there. Please print out
vect_info, intr_info, and kvm_rip_read(vcpu) (all as hex).
The more you instrument, of course, the better.
for testing i killed the kvm guest 0.4s after starting it - got this:
thousands of lines :
returning from kvm_handle_exit, cause 3, retval = 0, exit_reason = 30
mixed with single line (every ca. 40th-100th line) :
returning from kvm_handle_exit, cause 3, retval = 1, exit_reason = 1
...
This is normal operation. 30 is IO_INSTRUCTION, the guest is probably
reading its boot disk. 1 is EXTERNAL_INTERRUPT, normal host interrupts.
So the guest hands a little later. Let it reach steady state and see
where it hangs.
--
error compiling committee.c: too many arguments to function
--
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
