From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753830AbbLJQtS (ORCPT ); Thu, 10 Dec 2015 11:49:18 -0500 Received: from mx1.redhat.com ([209.132.183.28]:55569 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753693AbbLJQtQ (ORCPT ); Thu, 10 Dec 2015 11:49:16 -0500 Subject: Re: freeze host when injecting NMIs in the guest, at least in 4.4-rc4+ To: Borislav Petkov , kvm@vger.kernel.org References: <20151210140404.GA3049@nazgul.tnic> <20151210162733.GA6587@pd.tnic> <20151210164407.GA3593@nazgul.tnic> Cc: lkml , qemu-devel@nongnu.org From: Paolo Bonzini Message-ID: <5669AD06.3030409@redhat.com> Date: Thu, 10 Dec 2015 17:49:10 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <20151210164407.GA3593@nazgul.tnic> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/12/2015 17:44, Borislav Petkov wrote: > Yap, > > this is clearly a qemu/kvm issue. Lemme remove ext4 folks from CC. So > here's what happens: > > I boot a kvm guest, connect to its monitor (qemu is started with > "-monitor pty") and on the monitor I issue a couple of times the "nmi" > command. It doesn't explode immediately but it happens pretty often and > when it happens, the *host*(!) freezes with some nasty corruption, see > below. > > Thoughts, suggestions, ideas? Can you try it on Intel? Paolo