From mboxrd@z Thu Jan  1 00:00:00 1970
From: Gleb Natapov <gleb@redhat.com>
Subject: Re: Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry
 failed, hardware error 0x80000021"
Date: Sun, 9 Jun 2013 12:43:28 +0300
Message-ID: <20130609094328.GM4725@redhat.com>
References: <5194C254.4000201@sp.consulting.lsexperts.de>
 <1368925231.3469.98.camel@deadeye.wl.decadent.org.uk>
 <20130519123227.GA13375@redhat.com>
 <51AF27A5.5030509@sp.consulting.lsexperts.de>
 <20130605121024.GZ4725@redhat.com>
 <51AF3447.6090308@sp.consulting.lsexperts.de>
 <20130606064240.GR4725@redhat.com>
 <51B073F1.8030107@sp.consulting.lsexperts.de>
 <20130606114025.GC4725@redhat.com>
 <51B07C3F.2060104@sp.consulting.lsexperts.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Ben Hutchings <ben@decadent.org.uk>, kvm@vger.kernel.org,
	707257@bugs.debian.org
To: Stefan Pietsch <stefan.pietsch@lsexperts.de>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:4974 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1750827Ab3FIJnk (ORCPT <rfc822;kvm@vger.kernel.org>);
	Sun, 9 Jun 2013 05:43:40 -0400
Content-Disposition: inline
In-Reply-To: <51B07C3F.2060104@sp.consulting.lsexperts.de>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Thu, Jun 06, 2013 at 02:10:39PM +0200, Stefan Pietsch wrote:
> On 06.06.2013 13:40, Gleb Natapov wrote:
> > On Thu, Jun 06, 2013 at 01:35:13PM +0200, Stefan Pietsch wrote:
> 
> >> I had no success with the Debian kernel 3.10~rc4-1~exp1 (3.10-rc4-686-pae).
> >>
> >> The machine hangs after "Enabling APIC mode:  Flat.  Using 1 I/O APICs".
> > OK, since it looks like it hangs during timer initialization can you try
> > to disable kvmclock? Add -cpu qemu64,-kvmclock to your command line.
> > Also can you provide the output of "cat /proc/cpuinfo" on your host? And
> > complete serial output before hang.
> 
> 
> command line:
> qemu-system-i386 -machine accel=kvm -m 512 -cpu qemu64,-kvmclock -cdrom
> grml32-full_2013.02.iso -serial file:ttyS0.log
> 
> 
> ttyS0.log:
> ##########
> 

Nothing out of ordinary here. Since you can reproduce the hang and I
cannot, can you try and bisect it? Also can trace kvm during the hang
http://www.linux-kvm.org/page/Tracing? Start the trace as close to hang
as possible and stop it as quick after it as possible too to make trace
file smaller.

--
			Gleb.