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.
Cause: it's possible to specify SPICE TLS channels on qemu command line without specifying a TLS port for SPICE to use
Consequence: when qemu is started this way, it's not possible to connect to the VM using SPICE
Result: qemu now exits with an error in this situation
Description of problem:
SSIA.
Version-Release number of selected component (if applicable):
qemu-kvm-0.12.1.2-2.222.el6.x86_64
spice-server-0.10.1-1.el6.x86_64
How reproducible:
always
Steps to Reproduce:
run all of these (<dir> and <file> are pointing to valid SSL certs/keys):
qemu-kvm -spice port=<port>,tls-channel=main,tls-channel=inputs
qemu-kvm -spice port=5900,x509-dir=<dir>
qemu-kvm -spice port=5900,x509-cert-file=<file>,x509-cacert-file=<file>,x509-key-file=<file>
Actual results:
qemu-kvm happily runs
Expected results:
qemu-kvm should exit with non-zero error code and message like "spice: SSL/TLS options set but no tls-port specified"
Additional info:
High/High Priority/Severity set because this bug hides bugs that are in other components (RHEV/oVirt)
Comment 1Christophe Fergeau
2012-02-14 17:32:30 UTC
Christophe, thanks a lot. I'm moving the bug to you, switching component like you suggested, note that it will require regetting acks, and moving to POST. The patch is slated for next pull by Gerd:
http://patchwork.ozlabs.org/patch/142956/
Alon
Comment 8Christophe Fergeau
2012-03-22 09:59:53 UTC
It has now been sent to rhvirt-patches, thanks for the reminder.
Reproduced this issue with steps and environment as follows:
# uname -r;rpm -q qemu-kvm
2.6.32-220.el6.x86_64
qemu-kvm-0.12.1.2-2.209.el6.x86_64
1.run all of these
/usr/libexec/qemu-kvm -spice port=5900,tls-channel=main,tls-channel=inputs
/usr/libexec/qemu-kvm -spice port=5900,x509-dir=/home/spice_x509-Pa5
/usr/libexec/qemu-kvm -spice port=5900,x509-cert-file=/home/spice_x509-a5/server-cert.pem,x509-cacert-file=/home/spice_x509-Pa5/ca-cert.pem,x509-key-file=/home/spice_x509-Pa5/server-key.pem
qemu-kvm happily runs
Verified this issue with steps and environment as follows:
# uname -r;rpm -q qemu-kvm
2.6.32-220.el6.x86_64
qemu-kvm-0.12.1.2-2.269.el6.x86_64
redo above steps :
1. /usr/libexec/qemu-kvm -spice port=5900,tls-channel=main,tls-channel=inputs
qemu reports:
qemu-kvm: spice: tried to setup tls-channel without specifying a TLS port
Program exited with code 01.
2. /usr/libexec/qemu-kvm -spice port=5900,x509-dir=/home/spice_x509-Pa5
qemu-kvm happily runs
3. /usr/libexec/qemu-kvm -spice port=5900,x509-cert-file=/home/spice_x509-a5/server-cert.pem,x509-cacert-file=/home/spice_x509-Pa5/ca-cert.pem,x509-key-file=/home/spice_x509-Pa5/server-key.pem
qemu-kvm happily runs
Hi Christophe,
Is this consistent with the expected results ?
daiwei
Hi Wei, please could you look if qemu-kvm opens only plaintext port in 2. and 3. and if you can connect to it with a client? If yes (spice console is accessible as a result), then you can mark it as verified.
Verified this issue with steps and environment as follows:
# uname -r;rpm -q qemu-kvm
2.6.32-220.el6.x86_64
qemu-kvm-0.12.1.2-2.269.el6.x86_64
redo step 2 and step 3
2. /usr/libexec/qemu-kvm -spice port=5900,disable-ticketing,x509-dir=/home/spice_x509-Pa5 -monitor stdio
With "spicec -h host_ip -p 5900" spice console is accessible
3. /usr/libexec/qemu-kvm -spice port=5900,disable-ticketing,x509-cert-file=/home/spice_x509-a5/server-cert.pem,x509-cacert-file=/home/spice_x509-Pa5/ca-cert.pem,x509-key-file=/home/spice_x509-Pa5/server-key.pem -monitor stdio
With "spicec -h host_ip -p 5900" spice console is accessible
According to Comment12, this issue has been fixed.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
NEEDINFO
Comment 17Christophe Fergeau
2012-05-04 12:46:54 UTC
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1 +1,5 @@
-NEEDINFO+Cause: it's possible to specify SPICE TLS channels on qemu command line without specifying a TLS port for SPICE to use
+
+Consequence: when qemu is started this way, it's not possible to connect to the VM using SPICE
+
+Result: qemu now exits with an error in this situation
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/RHBA-2012-0746.html