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:
Some spice options when malformed make qemu-kvm exit gracefully, some make it crash with SIGABRT:
/usr/libexec/qemu-kvm -spice port=blabla
makes qemu-kvm exit gracefully with exit code 1 and error message:
qemu-kvm: -spice port=blabla: Parameter 'port' expects a number
parse error: port=blabla
But,
/usr/libexec/qemu-kvm -spice port=3000,addr=blabla
makes qemu-kvm crash with code 134 and message:
do_spice_init: starting 0.8.1
reds_init_socket: getaddrinfo(blabla,3000): Name or service not known
Aborted (core dumped)
Version-Release number of selected component (if applicable):
qemu-kvm-0.12.1.2-2.165.el6.x86_64
spice-server-0.8.1-2.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1. /usr/libexec/qemu-kvm -spice port=3000,addr=blabla
Actual results:
exit code: 134
message:
do_spice_init: starting 0.8.1
reds_init_socket: getaddrinfo(blabla,3000): Name or service not known
Aborted (core dumped)
Expected results:
exit code: 1
message:
qemu-kvm: -spice port=3000,addr=blabla: Parameter 'addr' expects a valid address identifier
parse error: addr=blabla
Comment 1RHEL Program Management
2011-07-28 16:06:11 UTC
Development Management has reviewed and declined this request. You may appeal
this decision by reopening this request.
Description of problem: Some spice options when malformed make qemu-kvm exit gracefully, some make it crash with SIGABRT: /usr/libexec/qemu-kvm -spice port=blabla makes qemu-kvm exit gracefully with exit code 1 and error message: qemu-kvm: -spice port=blabla: Parameter 'port' expects a number parse error: port=blabla But, /usr/libexec/qemu-kvm -spice port=3000,addr=blabla makes qemu-kvm crash with code 134 and message: do_spice_init: starting 0.8.1 reds_init_socket: getaddrinfo(blabla,3000): Name or service not known Aborted (core dumped) Version-Release number of selected component (if applicable): qemu-kvm-0.12.1.2-2.165.el6.x86_64 spice-server-0.8.1-2.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. /usr/libexec/qemu-kvm -spice port=3000,addr=blabla Actual results: exit code: 134 message: do_spice_init: starting 0.8.1 reds_init_socket: getaddrinfo(blabla,3000): Name or service not known Aborted (core dumped) Expected results: exit code: 1 message: qemu-kvm: -spice port=3000,addr=blabla: Parameter 'addr' expects a valid address identifier parse error: addr=blabla