From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jes Sorensen Subject: Re: [PATCH 1/1] Disable GUEST_INTR_STATE_STI flag before injecting NMI to guest on VMX Date: Fri, 27 Aug 2010 10:31:06 +0200 Message-ID: <4C7777CA.4010208@redhat.com> References: <1282853162-16925-1-git-send-email-Jes.Sorensen@redhat.com> <1282853162-16925-2-git-send-email-Jes.Sorensen@redhat.com> <4C7776F9.4070306@siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, avi@redhat.com, gleb@redhat.com To: Jan Kiszka Return-path: Received: from mx1.redhat.com ([209.132.183.28]:40290 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752463Ab0H0IbK (ORCPT ); Fri, 27 Aug 2010 04:31:10 -0400 In-Reply-To: <4C7776F9.4070306@siemens.com> Sender: kvm-owner@vger.kernel.org List-ID: On 08/27/10 10:27, Jan Kiszka wrote: > Am 26.08.2010 22:06, Jes.Sorensen@redhat.com wrote: >> From: Jes Sorensen >> >> Injecting an NMI while GUEST_INTR_STATE_STI is set may fail, >> which can cause an EXIT with invalid state, resulting in the >> guest dieing. > > Very interesting. Reality obviously doesn't bother about the statement > of the vendor [1]. > > Just curious: is this limited to specific CPU models or actually a > generic issue? I have been able to reproduce this on a core2 and a nehalem box, so I think it is at least somewhat generic on Intel. Not sure if it can be reproduced on AMD. It also seems to be specific to which guest kernel I run, so timing may play a part as well. Cheers, Jes