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:
Consoles get scrambled and unusable if two clients try to connect
at same time to the console.
Version-Release number of selected component (if applicable):
libvirt-0.9.4-17.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1. append 'console=ttyS0,115200' to guest kernel cmdline in grub.conf
2. reboot guest
3. open a terminal and run virsh console $guest
4. open another terminal and run virsh console $guest
6. run other shell command such as 'ls' in the first terminal
Actual results:
Output information is incomplete in these 2 terminals.
Expected results:
if a client has opened the console, and the other clients should get a notice rather than continue to allow connect the console, it will let 2 clients confusion, especially, if these 2 clients are a remote users.
Additional info:
Maybe, There are 2 solutions for this issue:
1. Document these stuff in virsh man page or other place such as libvirt.org
2. Get a notice if the console is alive.
Solution 2 should be very nice.