From: Avi Kivity <avi@redhat.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [Bug 1021649] Re: qemu 1.1.0 waits for a keypress at boot
Date: Wed, 25 Jul 2012 15:50:12 +0300 [thread overview]
Message-ID: <500FEB84.6040409@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1207251202490.26163@kaball.uk.xensource.com>
On 07/25/2012 02:12 PM, Stefano Stabellini wrote:
> On Wed, 25 Jul 2012, Michael Tokarev wrote:
>> Stefano, Paul, can you take a look please?
>>
>> https://bugs.launchpad.net/bugs/1021649
>
> That is a very good bug triage that you did!
>
> However "main_loop_wait: block indefinitely" only increases the maximum
> select timeout of QEMU's main_loop.
> That mean that if one or more emulators have bugs and don't get
> notifications correctly they might hang.
> The reason why it only reproduces with nographic is that both sdl and vnc
> introduce a gui_timer that wakes QEMU up every 30ms.
>
> So the question is: why is kernel_irqchip=on required to repro the bug?
> It strikes me as a bug in kernel_irqchip that prevents QEMU from being
> waken up when it should.
kernel_irqchip=on means that many guest timers and interrupt sources are
removed from qemu and implemented in the kernel, so qemu sees a lot less
wakeups and hangs. With kernel_irqchip=off the APIC or PIT wakes up
qemu, taking the place of the keypress.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-07-25 12:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 9:20 [Qemu-devel] [Bug 1021649] [NEW] qemu 1.1.0 waits for a keypress at boot Richard W.M. Jones
2012-07-06 9:20 ` [Qemu-devel] [Bug 1021649] " Richard W.M. Jones
2012-07-06 9:21 ` Richard W.M. Jones
2012-07-06 9:28 ` Richard W.M. Jones
2012-07-07 14:09 ` Anthony Liguori
2012-07-07 14:47 ` Richard W.M. Jones
2012-07-08 8:45 ` Michael Tokarev
2012-07-08 9:07 ` Michael Tokarev
2012-07-08 9:31 ` Bug Watch Updater
2012-07-08 9:33 ` Richard W.M. Jones
2012-07-08 9:50 ` Michael Tokarev
2012-07-08 10:02 ` Michael Tokarev
2012-07-09 9:41 ` Bug Watch Updater
2012-07-25 8:25 ` Michael Tokarev
2012-07-25 10:13 ` Michael Tokarev
2012-07-25 11:12 ` Stefano Stabellini
2012-07-25 12:50 ` Avi Kivity [this message]
2012-08-04 4:58 ` Jamie Heilman
2012-08-05 8:47 ` Avi Kivity
2012-07-25 18:10 ` Georg Hopp
2012-07-26 8:18 ` Michael Tokarev
2012-08-06 14:49 ` Paolo Bonzini
2012-08-07 3:35 ` Jamie Heilman
2012-08-25 17:16 ` Bug Watch Updater
2016-11-10 9:15 ` Thomas Huth
2016-11-10 9:49 ` Richard Jones
2016-11-10 10:00 ` Paolo Bonzini
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=500FEB84.6040409@redhat.com \
--to=avi@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
/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.