Hello Oliver, On Thu, Mar 18, 2010 at 08:43:53PM +0100, Olivier Berghmans wrote: > I tried nesting kvm in kvm on an AMD processor with support for svm > and npt (the dmesg told me both were in use). I managed to install the > nested kvm and when starting the L2 guest in order to install an > operating system, I got following messages in the L1 guest: > > [ 2016.712047] handle_exit: unexpected exit_ini_info 0x80000008 exit_code 0x60 > [ 2031.432032] handle_exit: unexpected exit_ini_info 0x80000008 exit_code 0x60 > [ 2034.468058] handle_exit: unexpected exit_ini_info 0x80000008 exit_code 0x60 These messages result from a difference between a real hardware svm and the emulated svm from kvm. Hardware SVM always injects an exception first before it does an #vmexit(0x60) while the svm emulation does immediatlt #vmexit again. I have a patch to fix this but it needs more testing. The patch implements detection of the above situation and sends an self-ipi in this case. Joerg -- 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
