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:
for example: boot guest with addr=0x21.0, it will lead to qemu core dump. if addr values <0x20 then guest work well
Version-Release number of selected component (if applicable):
# uname -r
2.6.32-191.el6.x86_64
# rpm -qa|grep kvm
qemu-kvm-0.12.1.2-2.190.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1./usr/libexec/qemu-kvm -m 4G -smp 4 -drive file=/dev/vg0/data512,if=none,id=drive-virtio0-0-0,format=qcow2,werror=ignore,rerror=ignore,cache=none -device virtio-blk-pci,drive=drive-virtio0-0-0,id=virti0-0-0 -netdev tap,id=hostnet0,vhost=on,script=/etc/qemu-ifup -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:56:00:94:a3:f8,bootindex=1 -uuid 9e6f04cf-2ad7-45aa-9333-2d2ee26570c6 -boot c -monitor stdio -spice id=on,disable-ticketing,port=5911 -drive file=/dev/vg0/data126,if=none,id=drive-virtio0-0-126,format=qcow2,cache=none -device virtio-blk-pci,drive=drive-virtio0-0-126,id=virti0-0-126,addr=0x21.0
2.
3.
Actual results:
core dump
Expected results:
Should have a hint or restrictions,should not core dump directly.
Additional info:
Comment 2Don Dutile (Red Hat)
2011-09-27 21:16:26 UTC
Closing since patch posted to resolve this problem for bz 678729.
*** This bug has been marked as a duplicate of bug 678729 ***