From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:52602) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T8n0p-0001YV-1K for qemu-devel@nongnu.org; Tue, 04 Sep 2012 02:53:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1T8n0n-0007rl-Ti for qemu-devel@nongnu.org; Tue, 04 Sep 2012 02:53:26 -0400 Received: from mail-pb0-f45.google.com ([209.85.160.45]:36470) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T8n0n-0007rg-NL for qemu-devel@nongnu.org; Tue, 04 Sep 2012 02:53:25 -0400 Received: by pbbjt11 with SMTP id jt11so8950554pbb.4 for ; Mon, 03 Sep 2012 23:53:24 -0700 (PDT) Sender: Paolo Bonzini Message-ID: <5045A560.4080108@redhat.com> Date: Tue, 04 Sep 2012 08:53:20 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <5044F367.5080300@msgid.tls.msk.ru> In-Reply-To: <5044F367.5080300@msgid.tls.msk.ru> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] apparently missing yet another notify_event() List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Michael Tokarev Cc: qemu-devel 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. 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? Paolo