Hide Forgot
when running: /usr/libexec/qemu-kvm -spice qemu-kvm exits gracefully with message: qemu-kvm: -spice: requires an argument but when running: /usr/libexec/qemu-kvm -spice port= qemu-kvm proceeds to run, and with VNC: VNC server running on `::1:5900' Version-Release number of selected component (if applicable): $ rpm -qa qemu-kvm spice-server 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: /usr/libexec/qemu-kvm -spice port= Actual results: qemu-kvm runs vnc Expected results: qemu-kvm should exit or run spice on the default port
Please provide the full command line, better use one from libvirt execution of qemu
The bug happens when qemu-kvm is executed as in the reproducer: $ /usr/libexec/qemu-kvm -spice port= I haven't noticed this bug in libvirt.
I verify with the latest spice-server and qemu-kvm,but this issue doesn't reproduce. Version-Release number of selected component (if applicable): # rpm -qa qemu-kvm spice-server spice-server-0.8.2-3.el6.x86_64 qemu-kvm-0.12.1.2-2.183.el6.x86_64 Steps to Reproduce: 1.when running: # /usr/libexec/qemu-kvm -spice The qemu-kvm exits gracefully with a message: qemu-kvm: -spice: requires an argument The qemu-kvm has exited correctly with friendly tips. 2.and when running: /usr/libexec/qemu-kvm -spice port= The qemu-kvm also exits gracefully with a message: neither port nor tls-port specified for spice. The qemu-kvm has exited correctly with friendly tips.
Reproduced on qemu-kvm-0.12.1.2-2.180.el6.x86_64: Steps to reproduce: -------------------- 1.In host: /usr/libexec/qemu-kvm -spice port= Actual results: ---------------- #/usr/libexec/qemu-kvm -spice port= qemu-kvm proceeds to run, and with VNC: VNC server running on `::1:5900' Verified on qemu-kvm-0.12.1.2-2.184.el6.x86_64: Actual results: --------------- After step 1: #/usr/libexec/qemu-kvm -spice port= neither port nor tls-port specified for spice. Conclusion: ------------- According to results above, this bug has been fixed.
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. http://rhn.redhat.com/errata/RHSA-2011-1531.html