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:
When debugging SPICE issues, that are reproducible only when two spice connections are open, the single log file written to by both becomes very difficult to read.
Version-Release number of selected component (if applicable):
Windows SPICE client, packaged in
rhevm-spice-client-x64-msi-3.6-6.el6.noarch
How reproducible:
100%
Steps to Reproduce:
1. Setup SPICE client debug logging
2. Open multiple connections
3. Watch logging to appear inside this file for both windows/connections
Actual results:
All logging appears in one single log file
Expected results:
Each window/spice client process should log in its own log file
Additional info:
One can redirect stdout/stderr of each remote-viewer instance to a different file, for example:
remote-viewer --spice-debug console_to_VM1.vv > logVM1 2>&1
remote-viewer --spice-debug console_to_VM2.vv > logVM2 2>&1