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 787678

Summary: print info about x509-* files used
Product: Red Hat Enterprise Linux 6 Reporter: David Jaša <djasa>
Component: spice-serverAssignee: Uri Lublin <uril>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: low Docs Contact:
Priority: low    
Version: 6.3CC: acathrow, cfergeau, dblechte, mkenneth, mkrcmari
Target Milestone: alpha   
Target Release: 6.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: spice-server-0.10.1-4.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-20 12:17:06 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 David Jaša 2012-02-06 13:50:00 UTC
Description of problem:
When qemu starts with -spice x509-<something>=<path> or -spice tls-port=<sport> option, it does not print any output regarding certs/keys loaded

Version-Release number of selected component (if applicable):
qemu-kvm-0.12.1.2-2.222.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. cd to directory with valid spice certs & keys
2. run /usr/libexec/qemu-kvm -spice tls-port=<sport>
3.
  
Actual results:
qemu-kvm prints to console:
spice_server_add_interface: SPICE_INTERFACE_MIGRATION
spice_server_add_interface: SPICE_INTERFACE_KEYBOARD
spice_server_add_interface: SPICE_INTERFACE_MOUSE
spice_server_add_interface: SPICE_INTERFACE_QXL
red_worker_main: begin
display_channel_create: create display channel
cursor_channel_create: create cursor channel

Expected results:
in addition to output above, spice-server should also something like this (based on output when the server-cert.pem file is missing):
reds_init_ssl: Loaded certificates from ./server-cert.pem
reds_init_ssl: Using private key from ./server-key.pem
reds_init_ssl: Loaded certificates from ./ca-cert.pem

Additional info:

Comment 1 Christophe Fergeau 2012-03-02 16:02:25 UTC
Patch fixing this sent upstream

Comment 6 David Jaša 2012-04-16 13:55:22 UTC
spice-server-0.10.1-5.el6.x86_64 prints:

/usr/libexec/qemu-kvm -spice tls-port=5900,password=123456,x509-dir=/etc/pki/libvirt-spice
do_spice_init: starting 0.10.1
reds_init_ssl: Loaded certificates from /etc/pki/libvirt-spice/server-cert.pem
reds_init_ssl: Using private key from /etc/pki/libvirt-spice/server-key.pem
reds_init_ssl: Loaded CA certificates from /etc/pki/libvirt-spice/ca-cert.pem

--> can be moved to VERIFIED

Comment 9 errata-xmlrpc 2012-06-20 12:17:06 UTC
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-0765.html