Re: [fedora-virt] [Qemu-devel] Fedora FC21 - Bug: 100% CPU and hangs in gettimeofday(&tp, NULL); forever
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
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
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?
(I responded to this thread on qemu-devel already, but the message didn't get back to this list because I'm subscribed here with a different address)
Take a look at the following kernel bug. It specifically deals with a hang in gettimeofday() in a KVM guest:
https://bugzilla.redhat.com/show_bug.cgi?id=1178975
There is a link to a patched kernel you can try; installing that kernel in my guest fixed my problems (I was repeatedly getting hangs in python-urlgrabber during yum updates on F21).
-
Cole Robinson -
Laine Stump -
Paolo Bonzini