From: Paolo Bonzini <pbonzini@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] apparently missing yet another notify_event()
Date: Tue, 04 Sep 2012 08:53:20 +0200 [thread overview]
Message-ID: <5045A560.4080108@redhat.com> (raw)
In-Reply-To: <5044F367.5080300@msgid.tls.msk.ru>
Il 03/09/2012 20:13, Michael Tokarev ha scritto:
> There's a new bugreport filed against qemu-kvm in debian,
> which looks very similar to what we already had before --
> https://bugs.launchpad.net/qemu/+bug/1021649
> which were fixed by adding qemu_notify_event() call.
> Later on these qemu_notify_event() calls become unnecessary
> as far as I remember.
>
> But here is a new one.
>
> qemu -nographic -kernel /boot/vmlinuz-$(uname -r) -append console=ttyS0 -serial pty
>
> This will hang with 100% CPU usage until something is sent
> to the pty. <Enter> key is enough.
>
> It does the same on qemu and kvm, with and without -enable-kvm,
> and it looks pretty much like another forgotten notify_event.
> And it happens on 1.1 and 1.2-tobe (today qemu/master), so should
> be fixed before 1.2 is released.
>
> Note: libvirt uses pty-redirected serial port heavily, and this
> is where the users are hit, exactly.
>
> The longer -serial specification (-chardev pty, -device isa-serial)
> triggers it too.
>
> What's missing this time?
Could it be this one?
<http://permalink.gmane.org/gmane.comp.emulators.qemu/168209>
Paolo
next prev parent reply other threads:[~2012-09-04 6:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 18:13 [Qemu-devel] apparently missing yet another notify_event() Michael Tokarev
2012-09-04 6:53 ` Paolo Bonzini [this message]
2012-09-04 6:58 ` Michael Tokarev
2012-09-14 14:17 ` Michael Tokarev
2012-09-14 14:47 ` Michael Tokarev
2012-09-14 14:49 ` Michael Tokarev
2012-09-14 15:47 ` Michael Tokarev
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=5045A560.4080108@redhat.com \
--to=pbonzini@redhat.com \
--cc=mjt@tls.msk.ru \
--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 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.