Bug 969487
| Summary: | the openstack cloud image should print boot messages also on ttyS0 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Giulio Fidente <gfidente> |
| Component: | guest-images | Assignee: | Joey Boggs <jboggs> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.4 | CC: | cpelland, dgregor, fdinitto, gfidente, jboggs, jgreguske, leiwang, mburns, wshi |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | rhel-guest-image-6-6.5-20131101.2.el6 | Doc Type: | Bug Fix |
| Doc Text: |
* The Red Hat Enterprise Linux guest image did not make use of the ttyS0 serial port by default, so tools that monitor the serial console log did not capture any information. This update adds a console log feature to the boot loader, and the Red Hat Enterprise Linux guest image will now print boot messages on the ttyS0 serial port and the standard console.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-11-22 00:21:28 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1001730 | ||
|
Description
Giulio Fidente
2013-05-31 14:15:08 UTC
*** Bug 1024389 has been marked as a duplicate of this bug. *** Hi Joey,
After you apply this patch, i can use virsh console to connect to our applance, but this is still something abnormal.
The getty prompt appears earlier than the other bootup messages, if i type username at this time, i'll give me the bash session, but after all services is booted, there will have another getty prompt, which will interrupt with the earlier one, which make everything messed up.
The way to workaround such problem is interact with getty prompt after all services launched.
Bringing up interface eth0:
Determining IP information for eth0...
Red Hat Enterprise Linux Server release 6.4 (Santiago)
Kernel 2.6.32-428.el6.x86_64 on an x86_64
localhost.localdomain login: done.
[ OK ]
Starting system logger: [ OK ]
Starting rpcbind: [ OK ]
.....
.....
.....
Starting atd: [ OK ]
Starting rhsmcertd... [ OK ]
Red Hat Enterprise Linux Server release 6.4 (Santiago)
Kernel 2.6.32-428.el6.x86_64 on an x86_64
virtlab-66-84-199.englab.nay.redhat.com login: root
Verified: rhel-guest-image-6-6.5-20131101.2.el6 We can watch the system booting messages through 'virsh console' and login to the appliance after getty apears and interact with the shell. Starting crond: [ OK ] Starting atd: [ OK ] Starting rhsmcertd... [ OK ] Red Hat Enterprise Linux Server release 6.4 (Santiago) Kernel 2.6.32-428.el6.x86_64 on an x86_64 virtlab-66-84-199.englab.nay.redhat.com login: root Last login: Sun Nov 3 20:38:04 on ttyS0 -bash-4.1# -bash-4.1# -bash-4.1# -bash-4.1# ls anaconda-ks.cfg -bash-4.1# 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-2013-1735.html |