Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752461Ab2E0Ilb (ORCPT ); Sun, 27 May 2012 04:41:31 -0400 Received: from mx1.redhat.com ([209.132.183.28]:58150 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752121Ab2E0Il2 (ORCPT ); Sun, 27 May 2012 04:41:28 -0400 Date: Sun, 27 May 2012 11:41:26 +0300 From: Gleb Natapov To: Sasha Levin Cc: Avi Kivity , mtosatti@redhat.com, Dave Jones , kvm@vger.kernel.org, "linux-kernel@vger.kernel.org" Subject: Re: kvm: KVM internal error. Suberror: 1 Message-ID: <20120527084126.GM9769@redhat.com> References: <1336324765.3638.4.camel@lappy> <4FA787D5.6040508@redhat.com> <20120527062129.GK9769@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 904 Lines: 24 On Sun, May 27, 2012 at 10:23:23AM +0200, Sasha Levin wrote: > On Sun, May 27, 2012 at 8:21 AM, Gleb Natapov wrote: > > On Sun, May 27, 2012 at 02:55:39AM +0200, Sasha Levin wrote: > >> On Fri, May 11, 2012 at 1:40 PM, Sasha Levin wrote: > >> > I wasn't able to reproduce this issue so far. > >> > >> So I've managed to hit this again, this time with a 3.4 host kernel: > >> > > Do you have this instance of QEMU running? > > Nope, qemu pretty much hangs at that point, so I've killed it. > Guest hangs, but not qemu. > Should I wait with that next time? Yes. You can inspect guest's state further. -- Gleb. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/