Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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>
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>
Reviewed-by: Alberto Garcia <berto>
Message-id: 1442417924-25831-1-git-send-email-pbonzini
Signed-off-by: Stefan Hajnoczi <stefanha>
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
can it be that this bug is only fixed for qemu-kvm, but not for qemu-system-x86_64
While trying to use packer from packer.io and qemu as builder I ran into:
2019/01/16 13:32:11 packer: 2019/01/16 13:32:11 Executing /usr/bin/qemu-system-x86_64: []string{"-vnc", "127.0.0.1:66", "-machine", "type=pc,accel=tcg", "-device", "virtio-net,netdev=user.0", "-name", "centos-vm", "-netdev", "user,id=user.0,hostfwd=tcp::3397-:22", "-cdrom", "/home/****/packer.io/configs/centos7/packer_cache/2c14e2204a6adb446f541f4437d9540f0972ed66637769c6527aea0242ec540f.iso", "-m", "512M", "-drive", "file=builds/centos-vm,if=virtio,cache=writeback,discard=ignore,format=qcow2", "-boot", "once=d", "-display", "sdl"}
2019/01/16 13:32:11 packer: 2019/01/16 13:32:11 Started Qemu. Pid: 50389
2019/01/16 13:32:11 packer: 2019/01/16 13:32:11 Qemu stderr:
2019/01/16 13:32:11 packer: 2019/01/16 13:32:11 Qemu stderr: (process:50389): GLib-WARNING **: 13:32:11.276: gmem.c:489: custom memory allocation vtable not supported
2019/01/16 13:32:11 packer: 2019/01/16 13:32:11 Qemu stderr: Could not initialize SDL(No available video device) - exiting
2019/01/16 13:32:11 ui error: ==> qemu: Error launching VM: Qemu failed to start. Please run with PACKER_LOG=1 to get more info.
rpm -qa |grep ^qemu
qemu-system-x86-2.0.0-1.el7.6.x86_64
qemu-img-1.5.3-160.el7.x86_64
qemu-kvm-1.5.3-160.el7.x86_64
qemu-common-2.0.0-1.el7.6.x86_64
qemu-kvm-common-1.5.3-160.el7.x86_64
System is RHEL 7.6
(In reply to Peter Bieringer from comment #11)
> can it be that this bug is only fixed for qemu-kvm, but not for
> qemu-system-x86_64
>
> While trying to use packer from packer.io and qemu as builder I ran into:
>
See https://bugzilla.redhat.com/show_bug.cgi?id=1666811#c1