Bug 757516 - Login via serial console fails to accept password for a guest(F16) on an F16 host
Summary: Login via serial console fails to accept password for a guest(F16) on an F16 ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: plymouth
Version: 16
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-27 15:42 UTC by Kashyap Chamarthy
Modified: 2013-02-14 00:34 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-14 00:34:25 UTC
Type: ---


Attachments (Terms of Use)

Description Kashyap Chamarthy 2011-11-27 15:42:42 UTC
Description of problem:

Login via serial console fails to accept password for a guest(F16) on an F16 host.The prompt doesn't even let you type the complete password as the Login/Entry fields are distorted.

NOTE: Login via serial console worked fine during F12-F13-F14 release time frame. This appears to be a regression.


Version-Release number of selected component (if applicable):

Fully updated host (KVM based virtualization)
====================
$ rpm -q util-linux-ng qemu-kvm libvirt python-virtinst plymouth
package util-linux-ng is not installed
qemu-kvm-0.15.1-3.fc16.x86_64
libvirt-0.9.6-2.fc16.x86_64
python-virtinst-0.600.0-5.fc16.noarch
plymouth-0.8.4-0.20110822.2.fc16.x86_64
====================
$ cat /etc/fedora-release 
Fedora release 16 (Verne)
$ 
====================

How reproducible:
All the time.

Steps to Reproduce:

1/ Create a guest using the below virt-install command-line
===================
virt-install --connect=qemu:///system \
    --network=bridge:br0 \
    --initrd-inject=/export/fed-minimal.ks \
    --extra-args="ks=file:/fed.ks console=tty0 console=ttyS0,115200 serial rd_NO_PLYMOUTH" \
    --name=fedora16-test \
    --disk /export/vmimgs/$domname.img,size=10 \
    --ram 2048 \
    --vcpus=2 \
    --check-cpu \
    --accelerate \
    --hvm \
    --location=/path/to/fedora/16/tree/ \
    --nographics 
===================
Fedora minimal kickstart I used -- http://kashyapc.fedorapeople.org/virt/fed-minimal.ks


2/ Reboot the guest and start the guest with serial console option.
====
$ virsh start --console fedora16-test
====
 
Actual results:
---------------

Output from the serial console:
==============
.
.
.
.
Started /etc/rc.local Compatibility.
Starting Terminate Plymouth Boot Screen...
Starting Wait for Plymouth Boot Screen to Quit...
Starting D-Bus System Message Bus...
Starting Login Service...
Started Console System Startup Logging.
Started Security Auditing Service.

Fedora release 16 (Verne)
Kernel 3.1.0-7.fc16.x86_64 on an x86_64 (ttyS0)

dhcp201-193 login: root
Password: 
Login incorrect

login: 
Password: 
Login incorrect

login: 
Password: 
Login incorrect

login: 

=================



Expected results:
------------------
Login via serial console interface should be successful


Additional info:
----------------
That's the Fedora-16 'guest' kernel command-line info. (note that I also disabled plymouth with the option rd_NO_PLYMOUTH to no avail) -- which worked during F13-F14 time frame.
====================
.
.
	linux	/vmlinuz-3.1.0-7.fc16.x86_64 root=/dev/mapper/vg_dhcp201193-lv_root ro rd.md=0 rd.lvm.lv=vg_dhcp201193/lv_swap rd.lvm.lv=vg_dhcp201193/lv_root text console=tty0  KEYTABLE=us quiet console=ttyS0,115200 rhgb rd.luks=0 rd_NO_PLYMOUTH LANG=en_US.UTF-8 serial SYSFONT=latarcyrheb-sun16 rd.dm=0 
	echo	'Loading initial ramdisk ...'
	initrd	/initramfs-3.1.0-7.fc16.x86_64.img
.
.
====================

Comment 1 Michal Schmidt 2012-01-02 13:52:16 UTC
(In reply to comment #0)
> note that I also disabled plymouth with the option rd_NO_PLYMOUTH to no avail

Have you also tried masking plymouth-start.service as in https://bugzilla.redhat.com/show_bug.cgi?id=691374#c4 ?

Comment 2 Kashyap Chamarthy 2012-01-02 16:18:44 UTC
Yes Michal, doing a symlink like mentioed in the above bugzilla does fix it.

[root@localhost ~]# #ln -s /dev/null /etc/systemd/system/plymouth-start.service

###########################################
[root@tesla ~]# virsh console f16t1
Connected to domain f16t1
Escape character is ^]

Fedora release 16 (Verne)
Kernel 3.1.0-7.fc16.x86_64 on an x86_64 (ttyS0)

localhost login: root
Password: 
Last login: Mon Jan  2 11:12:14 on ttyS0
[root@localhost ~]# 
###########################################

This appears to be a regression, do you agree?. (Note: A previous discussion(prior to systemd) with Ray Strode resulted in disabling plymouth which resulted in a proper serial console login.)

Comment 3 Fedora End Of Life 2013-01-16 21:53:13 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Fedora End Of Life 2013-02-14 00:34:28 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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