From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] "trace: split trace_init_file out of trace_init_backends" causes hangs on daemonize
Date: Wed, 10 Feb 2016 10:29:32 +0100 [thread overview]
Message-ID: <56BB02FC.10501@de.ibm.com> (raw)
In-Reply-To: <56BB0176.4040408@de.ibm.com>
On 02/10/2016 10:23 AM, Christian Borntraeger wrote:
> Paolo,
>
>
> commit 41fc57e44ed64cd4ab5393d83624afd897dabd4f
> trace: split trace_init_file out of trace_init_backends
>
> causes hangs for libvirt when checking the daemonized process,
> if the qemu was build with trace-backend=simple.
>
> Also calling
> qemu-system-s390x -machine accel=kvm -S -no-user-config -nodefaults -nographic -M none -qmp unix:/var/lib/libvirt/qemu/capabilities.monitor.sock,server,nowait -pidfile /var/lib/libvirt/qemu/capabilities.pidfile -daemonize
>
> just hangs
>
> without "trace-backend=simple"
> things are fine.
>
>
Just found a fix on the list.
prev parent reply other threads:[~2016-02-10 9:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 9:23 [Qemu-devel] "trace: split trace_init_file out of trace_init_backends" causes hangs on daemonize Christian Borntraeger
2016-02-10 9:29 ` Christian Borntraeger [this message]
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=56BB02FC.10501@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=pbonzini@redhat.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).