From: Gerhard Wiesinger <lists@wiesinger.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Fedora FC21 - Bug: 100% CPU and hangs in gettimeofday(&tp, NULL); forever
Date: Thu, 08 Jan 2015 14:36:01 +0100 [thread overview]
Message-ID: <54AE87C1.2060907@wiesinger.com> (raw)
Hello,
After upgrading my KVM environment from Fedora 20 to Fedora 21 up2date
(hosts and guests, Intel CPU) I've the following problem:
1.) On the database VM PostgresSQL e.g. 2 processes hang with 100% cpu
2.) On the monitoring VM Munin/RRDtool also hangs with 100% cpu
Killing of processes is not possible, only reboot helps.
But I nailed it down to the following:
yum install strace
strace -y -p339
Process 339 attached
# no system calls here
^CProcess 339 detached
Going deeper:
yum --enablerepo fedora-debuginfo,updates-debuginfo install gdb
postgresql-debuginfo
gdb postgres 339
(gdb) bt
#0 0x00007fffffbf8ff8 in gettimeofday ()
#1 0x00000000006d425e in GetCurrentTimestamp () at timestamp.c:1274
(gdb) frame 1
#1 0x00000000006d425e in GetCurrentTimestamp () at timestamp.c:1274
1274 gettimeofday(&tp, NULL);
(same on second process here)
Quitting and reattaching gdb also hangs here, so gettimeofday takes 100%
CPU and never ends!
Therefore I guess this is a problem either in the Linux kernel or in
QEMU/KVM.
It might be the case that something changed in timer handling or some
default changed here. VMs are time syncrhonized with NTP so this might
also be a problem that the syscall hangs here.
Workaround when it happens: reboot ....
Any further ideas?
Thank you.
Ciao,
Gerhard
next reply other threads:[~2015-01-08 13:37 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 13:36 Gerhard Wiesinger [this message]
2015-01-08 17:24 ` [Qemu-devel] Fedora FC21 - Bug: 100% CPU and hangs in gettimeofday(&tp, NULL); forever Paolo Bonzini
2015-01-08 18:12 ` Gerhard Wiesinger
2015-01-08 18:22 ` Paolo Bonzini
2015-01-08 22:28 ` Gerhard Wiesinger
2015-01-08 22:42 ` Paolo Bonzini
2015-01-12 11:41 ` Gerhard Wiesinger
2015-01-12 11:46 ` Paolo Bonzini
2015-01-12 11:53 ` Gerhard Wiesinger
2015-01-12 11:54 ` Paolo Bonzini
2015-01-13 20:13 ` Gerhard Wiesinger
2015-01-13 20:48 ` Paolo Bonzini
2015-01-13 21:08 ` Cole Robinson
2015-01-13 21:14 ` Gerhard Wiesinger
2015-01-13 21:16 ` Paolo Bonzini
2015-01-13 22:01 ` Gerhard Wiesinger
2015-01-14 0:59 ` Laine Stump
2015-01-14 9:15 ` Gerhard Wiesinger
2015-02-15 8:18 ` Gerhard Wiesinger
2015-02-16 14:18 ` Paolo Bonzini
2015-02-16 15:09 ` Gerhard Wiesinger
2015-02-16 15:29 ` Paolo Bonzini
2015-03-01 10:36 ` Gerhard Wiesinger
2015-03-02 9:26 ` Paolo Bonzini
2015-03-02 15:52 ` Gerhard Wiesinger
2015-03-02 17:15 ` Gerhard Wiesinger
2015-03-03 9:12 ` Gerhard Wiesinger
2015-03-03 10:12 ` Paolo Bonzini
2015-03-03 11:51 ` Gonglei
2015-03-03 12:28 ` Gerhard Wiesinger
2015-03-03 13:18 ` Gerhard Wiesinger
2015-03-03 20:50 ` Gerhard Wiesinger
2015-01-14 17:47 ` Juan Quintela
2015-01-14 17:52 ` Juan Quintela
2015-01-14 22:19 ` Gerhard Wiesinger
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=54AE87C1.2060907@wiesinger.com \
--to=lists@wiesinger.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 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.