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 1075125 - /dev/console doesn't ouput to ttyS0
Summary: /dev/console doesn't ouput to ttyS0
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: guest-images
Version: 6.5
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Joey Boggs
QA Contact: Virtualization Bugs
URL:
Whiteboard: node
Depends On: 1065007
Blocks: 1099462
TreeView+ depends on / blocked
 
Reported: 2014-03-11 14:36 UTC by Jaroslav Henner
Modified: 2015-11-04 16:58 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1065007
Environment:
Last Closed: 2014-10-22 18:43:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 969487 0 high CLOSED the openstack cloud image should print boot messages also on ttyS0 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1278084 0 medium CLOSED kernel logs (/dev/console) are not routed to /dev/ttyS0 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHBA-2014:1697 0 normal SHIPPED_LIVE rhel-guest-image enhancement update 2014-10-22 22:42:47 UTC

Internal Links: 969487 1278084

Comment 4 Jaroslav Henner 2014-03-12 15:32:54 UTC
Aha, it wasn't probably ever working exactly as written in the "Steps to Reproduce:"

With    rhel-guest-image-6-6.5-20140121.0-1, which has 

  console=ttyS0,115200n8 console=tty0 

on the cmdline, the command

  [root@bar cloud-user]# echo console > /dev/console

doesn't output the "console" to the ttyS0, but only to the tty0 and the boot messages are with color codes:

  Setting hostname bar.beerdrop:  [60G[[0;32m  OK  [0;39m]


However, if there is

  console=tty0 console=ttyS0,115200n8 

the output then goes to the ttyS0, but not to tty0.

  Setting hostname foo.beerdrop:  [  OK  ]


So, I would rather preferred the messages without the color codes as it makes the messages more readable in the log, though we don't get the eye candiness on the tty0. So if this has no other implications, I would recommend to change the command line to  console=tty0 console=ttyS0,115200n8.

Comment 7 yuliu 2014-09-11 06:20:28 UTC
Version:
rhel-guest-image-6.6-20140910.0.x86_64.qcow2

Steps:
1. #echo asdfasfasdf >/dev/ttyS0
asdfasfasdf
2. # echo adsfasfasdf >/dev/console
adsfasfasdf
we can see both ttyS0 and console are output to console.

Verified as above.

Comment 9 errata-xmlrpc 2014-10-22 18:43:39 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.

https://rhn.redhat.com/errata/RHBA-2014-1697.html


Note You need to log in before you can comment on or make changes to this bug.