Red Hat Bugzilla – Bug 1360137
GLib-WARNING **: gmem.c:482: custom memory allocation vtable not supported
Last modified: 2018-06-25 16:36:58 EDT
Description of problem: When start a guest on host with latest qemu-kvm version, there is warning prompt: "GLib-WARNING **: gmem.c:482: custom memory allocation vtable not supported"; while no the issue on host with latesst qemu-kvm-rhev version. [root@intel-5205-32-1 home]# uname -r 3.10.0-475.el7.x86_64 [root@intel-5205-32-1 home]# rpm -qa|grep qemu libvirt-daemon-driver-qemu-2.0.0-1.el7.x86_64 qemu-img-1.5.3-118.el7.x86_64 qemu-kvm-tools-1.5.3-118.el7.x86_64 ipxe-roms-qemu-20160127-1.git6366fa7a.el7.noarch qemu-kvm-1.5.3-118.el7.x86_64 qemu-kvm-debuginfo-1.5.3-118.el7.x86_64 qemu-kvm-common-1.5.3-118.el7.x86_64 [root@intel-5205-32-1 home]# [root@intel-5205-32-1 home]# [root@intel-5205-32-1 home]# /usr/libexec/qemu-kvm -name 'avocado-vt-vm1' -vnc :0 -monitor stdio (process:13080): GLib-WARNING **: gmem.c:482: custom memory allocation vtable not supported QEMU 1.5.3 monitor - type 'help' for more information (qemu) Version-Release number of selected component (if applicable): Kernel: 3.10.0-475.el7.x86_64 Qemu-kvm: qemu-kvm-1.5.3-118.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: Following patch already fix the bug, but not merged into latest QEMU 1.5.3 version: http://git.qemu.org/?p=qemu.git;a=commitdiff;h=98cf48f60aa4999f5b2808569a193a401a390e6a
(In reply to Gu Nini from comment #0) > Additional info: > Following patch already fix the bug, but not merged into latest QEMU 1.5.3 > version: > http://git.qemu.org/?p=qemu.git;a=commitdiff; > h=98cf48f60aa4999f5b2808569a193a401a390e6a commit 98cf48f60aa4999f5b2808569a193a401a390e6a Author: Paolo Bonzini <pbonzini@redhat.com> Date: Wed Sep 16 17:38:44 2015 +0200 trace: remove malloc tracing The malloc vtable is not supported anymore in glib, because it broke when constructors called g_malloc. Remove tracing of g_malloc, g_realloc and g_free calls. Note that, for systemtap users, glib also provides tracepoints glib.mem_alloc, glib.mem_free, glib.mem_realloc, glib.slice_alloc and glib.slice_free. Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Reviewed-by: Alberto Garcia <berto@igalia.com> Message-id: 1442417924-25831-1-git-send-email-pbonzini@redhat.com Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Found the same issue on rhel7.2z qemu-kvm-rhev versions: [root@hp-z800-03 qemu-kvm]# rpm -qa|grep qemu qemu-img-rhev-2.3.0-31.el7_2.20.x86_64 ipxe-roms-qemu-20160127-1.git6366fa7a.el7.noarch qemu-kvm-tools-rhev-2.3.0-31.el7_2.20.x86_64 qemu-kvm-common-rhev-2.3.0-31.el7_2.20.x86_64 qemu-kvm-rhev-2.3.0-31.el7_2.20.x86_64 [root@hp-z800-03 qemu-kvm]# [root@hp-z800-03 qemu-kvm]# [root@hp-z800-03 qemu-kvm]# [root@hp-z800-03 qemu-kvm]# /usr/libexec/qemu-kvm -name 'avocado-vt-vm1' -vnc :0 -monitor stdio (process:13902): GLib-WARNING **: gmem.c:482: custom memory allocation vtable not supported QEMU 2.3.0 monitor - type 'help' for more information (qemu)
Fix included in qemu-kvm-1.5.3-121.el7
Verify the bug on following sw versions: Host kernel: 3.10.0-481.el7.x86_64 Qemu-kvm: qemu-kvm-1.5.3-121.el7.x86_64 There is no the warning prompt any more: # /usr/libexec/qemu-kvm -name 'avocado-vt-vm1' -vnc :0 -monitor stdio QEMU 1.5.3 monitor - type 'help' for more information (qemu)
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2016-2585.html
*** Bug 1594304 has been marked as a duplicate of this bug. ***