All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cole Robinson <crobinso@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
	Gerhard Wiesinger <lists@wiesinger.com>,
	qemu-devel@nongnu.org, virt@lists.fedoraproject.org
Subject: Re: [Qemu-devel] Fedora FC21 - Bug: 100% CPU and hangs in gettimeofday(&tp, NULL); forever
Date: Tue, 13 Jan 2015 16:08:02 -0500	[thread overview]
Message-ID: <54B58932.9070104@redhat.com> (raw)
In-Reply-To: <54B584AB.4090303@redhat.com>

On 01/13/2015 03:48 PM, Paolo Bonzini wrote:
> 
> 
> On 13/01/2015 21:13, Gerhard Wiesinger wrote:
>>
>> It happens also with qemu-kvm 2.2.0 on another VM where also PostgreSQL
>> is running:
>> (gdb) bt
>> #0  0x00007fff9a1feff4 in gettimeofday ()
>> #1  0x00000000006d425e in GetCurrentTimestamp () at timestamp.c:1274
>>
>> What we know:
>> OK : F20: 3.17.6-200.fc20.x86_64 on guest/host,
>> qemu-kvm-1.6.2-10.fc20.x86_64 on host
>> NOK: F21: 3.17.7-300.fc21.x86_64 on guest/host,
>> qemu-kvm-2.1.2-7.fc21.x86_64 on host
>> NOK: F21: 3.17.8-300.fc21.x86_64 on guest/host,
>> qemu-kvm-2.2.0-1.fc21.x86_64 on host
>>
>> No one less can reproduce or has similar problems?
>> Any further ideas?
> 
> Hmm, too bad. :(
> 
> Any chance you can try with 1.7 and 2.0 releases?  Cole, perhaps you
> help building some RPMS for Gerhard?
> 
> Paolo
> 

There's F21 qemu-2.0 builds here:
http://koji.fedoraproject.org/koji/buildinfo?buildID=538383
And 1.7 builds here: http://koji.fedoraproject.org/koji/buildinfo?buildID=499026

There might be dependency issues trying to install on latest f21, if they were
built against older libraries. Worth a shot though. Besides that something
custom will need to be built, though at that point it's probably easier to
build qemu from source

- Cole

  reply	other threads:[~2015-01-13 21:08 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 [this message]
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=54B58932.9070104@redhat.com \
    --to=crobinso@redhat.com \
    --cc=lists@wiesinger.com \
    --cc=pbonzini@redhat.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 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.