From: Stefan Berger <stefanb@linux.vnet.ibm.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Crash when using -daemonize
Date: Mon, 09 Mar 2015 17:03:18 -0400 [thread overview]
Message-ID: <54FE0A96.30907@linux.vnet.ibm.com> (raw)
Since an upgrade to Fedora 21, I get crashes with QEMU when using
-daemonize. I noticed this since libvirt could not QMP probe QEMU.
This is the command line used:
x86_64-softmmu/qemu-system-x86_64 -S -no-user-config -nodefaults
-nographic -M none -pidfile /tmp/foo -daemonize
Here's the backtrace from the coredump:
#0 0x00007fe653d5c8d7 in __GI_raise (sig=sig@entry=6)
at ../sysdeps/unix/sysv/linux/raise.c:55
#1 0x00007fe653d5e53a in __GI_abort () at abort.c:89
#2 0x00007fe658c4cb80 in error_exit (err=<optimized out>,
msg=msg@entry=0x7fe658f58580 <__func__.6036> "qemu_mutex_unlock")
at util/qemu-thread-posix.c:48
#3 0x00007fe658edcab0 in qemu_mutex_unlock (
mutex=mutex@entry=0x7fe6593a01c0 <qemu_global_mutex>)
at util/qemu-thread-posix.c:93
#4 0x00007fe658c7a96c in qemu_mutex_unlock_iothread ()
at /root/qemu/qemu-git.pt/cpus.c:1137
#5 0x00007fe658e7695f in os_host_main_loop_wait (timeout=-1)
at main-loop.c:234
#6 main_loop_wait (nonblocking=<optimized out>) at main-loop.c:494
#7 0x00007fe658c4e82e in main_loop () at vl.c:1795
#8 main (argc=<optimized out>, argv=<optimized out>, envp=<optimized out>)
at vl.c:4354
I am using today's tip of the QEMU git tree, but I don't think that's
the actual problem.
Anyone have an idea? I reinstalled glibc, but that doesn't seem to solve
what looks like a mutex problem.
Stefan
next reply other threads:[~2015-03-09 21:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 21:03 Stefan Berger [this message]
2015-03-09 21:34 ` [Qemu-devel] Crash when using -daemonize Christian Borntraeger
2015-03-09 23:39 ` Stefan Berger
2015-03-10 9:35 ` 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=54FE0A96.30907@linux.vnet.ibm.com \
--to=stefanb@linux.vnet.ibm.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).