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.

Bug 617463

Summary: Coredump occorred when enable qxl
Product: Red Hat Enterprise Linux 6 Reporter: Amos Kong <akong>
Component: qemu-kvmAssignee: Alex Williamson <alex.williamson>
Status: CLOSED CURRENTRELEASE QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0CC: ailan, amit.shah, bcao, ddumas, kraxel, lihuang, lkocman, mhasko, mkenneth, snagar, tburke, virt-maint
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: qemu-kvm-0.12.1.2-2.102.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-10 21:26:52 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Amos Kong 2010-07-23 06:45:10 UTC 
Description of problem:
Boot up guest with '-vga qxl', coredump occorred.

downgrade qemu-kvm to 0.12.1.2-2.96.el6.x86_64, but could not reproduce.

# qemu-kvm -name 'vm1' -monitor unix:'/tmp/monitor-humanmonitor1-20100721-223536-AqCT',server,nowait -serial unix:'/tmp/serial-20100721-223536-AqCT',server,nowait -drive file='/home/devel/push/client/tests/kvm/images/RHEL-Server-6.0-64-virtio.qcow2',if=none,id=drive-virtio-disk1,media=disk,cache=none,boot=on,format=qcow2 -device virtio-blk-pci,drive=drive-virtio-disk1,id=virtio-disk1 -net nic,vlan=0,netdev=id9UfTTL,model=virtio,macaddr='02:A9:7C:6C:c9:6b' -netdev tap,id=id9UfTTL,ifname='virtio_0_8000',script='/home/devel/push/client/tests/kvm/scripts/qemu-ifup-switch',downscript='no',vhost=on -m 512 -smp 2 -spice port=8000,disable-ticketing -vga qxl -rtc base=utc,clock=host -M rhel6.0.0 -usbdevice tablet -cpu qemu64,+sse2 -no-kvm-pit-reinjection
do_spice_init: starting 0.4.2-14..el6
interface_change_notifier: VD_INTERFACE_KEYBOARD
interface_change_notifier: VD_INTERFACE_MOUSE
interface_change_notifier: VD_INTERFACE_QXL
red_worker_main: begin
RAMBlock "0000:00:02.0/qxl.rom" already registered, abort!
Aborted (core dumped)


Version-Release number of selected component (if applicable):
host kernel: 2.6.32-52.el6.x86_64
# rpm -qa |grep qemu
gpxe-roms-qemu-0.9.7-6.3.el6.noarch
qemu-kvm-tools-0.12.1.2-2.99.el6.x86_64
qemu-img-0.12.1.2-2.99.el6.x86_64
qemu-kvm-0.12.1.2-2.99.el6.x86_64
qemu-kvm-debuginfo-0.12.1.2-2.99.el6.x86_64
# rpm -qa |grep spice
ffmpeg-spice-libs-0.4.9-0.15.5spice.20080908.el6.x86_64
pixman-spice-0.13.3-5.el6.x86_64
spice-server-0.4.2-14.el6.x86_64
cairo-spice-1.8.7.1-4.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1. boot up a guest with '-vga qxl'


Actual results:
guest can boot up

Expected results:
coredump occurred
Comment 1 Amos Kong 2010-07-23 06:48:26 UTC 
(gdb) bt
#0  0x00000032304329b5 in raise () from /lib64/libc.so.6
#1  0x0000003230434195 in abort () from /lib64/libc.so.6
#2  0x00000000004e323e in qemu_ram_alloc (dev=<value optimized out>, name=<value optimized out>, size=65536) at /usr/src/debug/qemu-kvm-0.12.1.2/exec.c:2702
#3  0x0000000000419dd7 in pci_add_option_rom (qdev=0x2db57c0, base=<value optimized out>) at /usr/src/debug/qemu-kvm-0.12.1.2/hw/pci.c:1660
#4  pci_qdev_init (qdev=0x2db57c0, base=<value optimized out>) at /usr/src/debug/qemu-kvm-0.12.1.2/hw/pci.c:1499
#5  0x00000000004c1148 in qdev_init (dev=0x2db57c0) at /usr/src/debug/qemu-kvm-0.12.1.2/hw/qdev.c:275
#6  0x00000000004c11ca in qdev_init_nofail (dev=<value optimized out>) at /usr/src/debug/qemu-kvm-0.12.1.2/hw/qdev.c:317
#7  0x0000000000418ee1 in pci_create_simple (bus=<value optimized out>, devfn=<value optimized out>, name=<value optimized out>) at /usr/src/debug/qemu-kvm-0.12.1.2/hw/pci.c:1543
#8  0x000000000044d605 in pc_init1 (ram_size=134217728, boot_device=0x7fffbe24b0c0 "cad", kernel_filename=0x0, kernel_cmdline=0x5bdbe2 "", initrd_filename=0x0, 
    cpu_model=0x5af739 "qemu64", pci_enabled=1) at /usr/src/debug/qemu-kvm-0.12.1.2/hw/pc.c:1178
#9  0x000000000040dc17 in main (argc=<value optimized out>, argv=<value optimized out>, envp=<value optimized out>) at /usr/src/debug/qemu-kvm-0.12.1.2/vl.c:6362
Comment 4 Mike Cao 2010-07-26 02:10:55 UTC 
This issue comes in qemu-kvm 0.12.1.2-2.98.el6.x86_64
Comment 13 lihuang 2010-07-29 07:22:59 UTC 
Verified this bug on RHEL6 guest with qemu-kvm-0.12.1.2-2.104.el6, spice was able to run successfully, this bug has been fixed .

Change status to verified.
Comment 14 releng-rhel@redhat.com 2010-11-10 21:26:52 UTC 
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.