From: Gleb Natapov <gleb@redhat.com>
To: Stefan Pietsch <stefan.pietsch@lsexperts.de>
Cc: Ben Hutchings <ben@decadent.org.uk>,
kvm@vger.kernel.org, 707257@bugs.debian.org
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 [thread overview]
Message-ID: <20130609094328.GM4725@redhat.com> (raw)
In-Reply-To: <51B07C3F.2060104@sp.consulting.lsexperts.de>
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.
next prev parent reply other threads:[~2013-06-09 9:43 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <518A7323.7000302@sp.consulting.lsexperts.de>
[not found] ` <1368061686.4131.225.camel@deadeye.wl.decadent.org.uk>
[not found] ` <518BF14E.3070509@sp.consulting.lsexperts.de>
[not found] ` <5194C254.4000201@sp.consulting.lsexperts.de>
2013-05-19 1:00 ` Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021" Ben Hutchings
2013-05-19 12:32 ` Gleb Natapov
2013-05-29 15:05 ` Stefan Pietsch
2013-05-29 17:20 ` Ben Hutchings
2013-06-05 11:57 ` Stefan Pietsch
2013-06-05 12:10 ` Gleb Natapov
2013-06-05 12:51 ` Stefan Pietsch
2013-06-06 6:42 ` Gleb Natapov
2013-06-06 7:20 ` Gleb Natapov
2013-06-06 11:35 ` Stefan Pietsch
2013-06-06 11:40 ` Gleb Natapov
2013-06-06 12:10 ` Stefan Pietsch
2013-06-09 9:43 ` Gleb Natapov [this message]
2013-06-13 11:57 ` Stefan Pietsch
2013-06-13 13:42 ` Paolo Bonzini
2013-06-13 13:46 ` Paolo Bonzini
2013-06-13 14:59 ` Stefan Pietsch
2013-06-16 0:25 ` Stefan Pietsch
2013-06-17 16:07 ` Paolo Bonzini
2013-06-18 16:35 ` Stefan Pietsch
2013-06-19 13:41 ` Gleb Natapov
2013-06-19 14:12 ` Stefan Pietsch
2013-06-19 14:38 ` Gleb Natapov
2013-06-20 17:01 ` Stefan Pietsch
2013-06-23 7:51 ` Gleb Natapov
2013-06-23 16:51 ` Stefan Pietsch
2013-06-23 17:36 ` Gleb Natapov
2013-06-24 11:43 ` Stefan Pietsch
2013-06-24 11:47 ` Gleb Natapov
2013-06-24 11:59 ` Stefan Pietsch
2013-06-24 12:30 ` Gleb Natapov
2013-06-24 20:42 ` Stefan Pietsch
2013-06-26 10:47 ` Gleb Natapov
2013-06-27 14:09 ` Stefan Pietsch
2013-06-27 20:01 ` Gleb Natapov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130609094328.GM4725@redhat.com \
--to=gleb@redhat.com \
--cc=707257@bugs.debian.org \
--cc=ben@decadent.org.uk \
--cc=kvm@vger.kernel.org \
--cc=stefan.pietsch@lsexperts.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.