From: Paolo Bonzini <pbonzini@redhat.com>
To: Gerhard Wiesinger <lists@wiesinger.com>,
Laine Stump <laine@redhat.com>,
qemu-devel@nongnu.org, Cole Robinson <crobinso@redhat.com>,
virt@lists.fedoraproject.org
Subject: Re: [Qemu-devel] Fedora FC21 - Bug: 100% CPU and hangs in gettimeofday(&tp, NULL); forever
Date: Mon, 16 Feb 2015 16:29:25 +0100 [thread overview]
Message-ID: <54E20CD5.3050909@redhat.com> (raw)
In-Reply-To: <54E20812.4090006@wiesinger.com>
On 16/02/2015 16:09, Gerhard Wiesinger wrote:
> On 16.02.2015 15:18, Paolo Bonzini wrote:
>>
>> On 15/02/2015 09:18, Gerhard Wiesinger wrote:
>>>
>>> Can you grab some random backtraces ("thread apply all bt full") with
>>> gdb?
>
> Very low load on the machine, so I guess most will be sleeping and hard
> to catch non sleeping ones. See below
This likely means that the 100% threads are not the I/O (event loop)
threads, but the VCPU threads.
>>> Kernel (host/guest): 3.18.6-200.fc21.x86_64 #1 SMP
>>> qemu-kvm-2.2.0-5.fc21.x86_64
>>>
>>> Bug 1178975 - endless loop in clock_gettime() on a kvm-based VM
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1178975
>>> is fixed (didn't occour with the test program posted at
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1178975#c28 in 30min,
>>> happened before reproduceable in 2min, still running)
>>>
>>> So I guess there is another problem in the kernel with volatile and gcc
>>> optimizations (or maybe in qemu-KVM)
>> No, this doesn't look like volatile.
>
> But why 100% on 2 cores?
Because you have 2 VCPUs, I guess.
Paolo
next prev parent reply other threads:[~2015-02-16 15:29 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 13:36 [Qemu-devel] Fedora FC21 - Bug: 100% CPU and hangs in gettimeofday(&tp, NULL); forever Gerhard Wiesinger
2015-01-08 17:24 ` 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 [this message]
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=54E20CD5.3050909@redhat.com \
--to=pbonzini@redhat.com \
--cc=crobinso@redhat.com \
--cc=laine@redhat.com \
--cc=lists@wiesinger.com \
--cc=qemu-devel@nongnu.org \
--cc=virt@lists.fedoraproject.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).