From: Markus Armbruster <armbru@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: 'Paolo Bonzini' <pbonzini@redhat.com>,
"Grundmann, Christian" <Christian.Grundmann@fabasoft.com>,
"'qemu-devel@nongnu.org'" <qemu-devel@nongnu.org>,
"stefanha@redhat.com" <stefanha@redhat.com>
Subject: Re: [Qemu-devel] WG: [ovirt-users] Segmentation fault in libtcmalloc
Date: Thu, 10 Dec 2015 14:18:38 +0100 [thread overview]
Message-ID: <87a8picuhd.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <20151210123822.GG2570@work-vm> (David Alan Gilbert's message of "Thu, 10 Dec 2015 12:38:23 +0000")
"Dr. David Alan Gilbert" <dgilbert@redhat.com> writes:
> * Grundmann, Christian (Christian.Grundmann@fabasoft.com) wrote:
>> Hi,
>>
>> qemu-img-ev-2.3.0-29.1.el7.x86_64
>> libvirt-daemon-driver-qemu-1.2.8-16.el7_1.4.x86_64
>> qemu-kvm-ev-2.3.0-29.1.el7.x86_64
>> qemu-kvm-common-ev-2.3.0-29.1.el7.x86_64
>> ipxe-roms-qemu-20130517-7.gitc4bce43.el7.noarch
>> qemu-kvm-tools-ev-2.3.0-29.1.el7.x86_64
>>
>>
>> it seems pc-i440fx-rhel7.2.0 is the default for ovirt 3.6
>>
>> I tried using only virtio-scsi disk but the VM wont boot (not
>> bootable device) so i used IDE for the boot disk.
>
> I think this seg is actually quite different - although it depends
> where the actual corruption
> happened - looking at the backtrace again the failing thread wasn't
> the io thread; it
> failed in a call from the json parser in the main thread.
Yes, in a free on behalf of parser_context_free() on parser cleanup.
Smells like memory corruption. Habe you tried reproducing under
valgrind?
next prev parent reply other threads:[~2015-12-10 13:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6A17C71B52524C408E7AAF69103E9E490F14400C@fabamailserver.fabagl.fabasoft.com>
[not found] ` <20151113190014.GB18986@redhat.com>
2015-11-16 8:11 ` [Qemu-devel] WG: [ovirt-users] Segmentation fault in libtcmalloc Grundmann, Christian
2015-11-17 9:59 ` Dr. David Alan Gilbert
2015-11-17 10:36 ` Grundmann, Christian
2015-11-17 11:36 ` Dr. David Alan Gilbert
2015-11-17 14:11 ` Grundmann, Christian
2015-11-17 14:20 ` Grundmann, Christian
2015-11-17 14:42 ` Dr. David Alan Gilbert
2015-11-19 16:00 ` Grundmann, Christian
2015-11-19 17:02 ` Paolo Bonzini
2015-12-03 8:18 ` Grundmann, Christian
2015-12-03 9:04 ` Dr. David Alan Gilbert
2015-12-03 9:07 ` Grundmann, Christian
2015-12-10 12:38 ` Dr. David Alan Gilbert
2015-12-10 13:18 ` Markus Armbruster [this message]
2015-12-10 13:37 ` Grundmann, Christian
2015-11-20 19:06 ` Dr. David Alan Gilbert
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=87a8picuhd.fsf@blackfin.pond.sub.org \
--to=armbru@redhat.com \
--cc=Christian.Grundmann@fabasoft.com \
--cc=dgilbert@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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.