From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joerg Roedel Subject: Re: unexpected exit_ini_info when nesting svm Date: Sun, 21 Mar 2010 18:09:24 +0100 Message-ID: <20100321170924.GJ13108@8bytes.org> References: <5a8bf3181003181243m84cf568h22a1885284d0338f@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: kvm@vger.kernel.org To: Olivier Berghmans Return-path: Received: from 8bytes.org ([88.198.83.132]:43680 "EHLO 8bytes.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751820Ab0CURJ1 (ORCPT ); Sun, 21 Mar 2010 13:09:27 -0400 Content-Disposition: inline In-Reply-To: <5a8bf3181003181243m84cf568h22a1885284d0338f@mail.gmail.com> Sender: kvm-owner@vger.kernel.org List-ID: 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