qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Matt Lupfer <mlupfer@ddn.com>, QEMU Developers <qemu-devel@nongnu.org>
Cc: alex@alex.org.uk
Subject: Re: [Qemu-devel] CentOS 5.x intermittently fails to boot on QEMU 1.7.0
Date: Fri, 21 Feb 2014 07:30:58 +0100	[thread overview]
Message-ID: <5306F2A2.1070107@redhat.com> (raw)
In-Reply-To: <5306D74B.7070104@ddn.com>

Il 21/02/2014 05:34, Matt Lupfer ha scritto:
>
> This doesn't appear to be a solution, because with the timer rewrite, QEMU
> moves its periodic (1 ms) qemu_notify_event() call to break out of
> the main event loop from a SIGALRM handler to the rearm of a QEMU timer.
> Presumably QEMU is counting on these generic callbacks.

Thanks for the report, I'll try to reproduce.

Paolo

  reply	other threads:[~2014-02-21  6:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-21  4:34 [Qemu-devel] CentOS 5.x intermittently fails to boot on QEMU 1.7.0 Matt Lupfer
2014-02-21  6:30 ` Paolo Bonzini [this message]
2014-02-21 13:27 ` Alex Bligh
2014-02-22  0:57   ` Matt Lupfer
2014-02-22  8:55     ` Alex Bligh
2014-02-22  8:59     ` 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=5306F2A2.1070107@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=alex@alex.org.uk \
    --cc=mlupfer@ddn.com \
    --cc=qemu-devel@nongnu.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).