Bug 985834 - fail to login into guest even with only one virtconsole port
fail to login into guest even with only one virtconsole port
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm (Show other bugs)
Unspecified Unspecified
medium Severity low
: rc
: ---
Assigned To: Amit Shah
Virtualization Bugs
Depends On:
  Show dependency treegraph
Reported: 2013-07-18 06:56 EDT by Sibiao Luo
Modified: 2014-08-19 07:44 EDT (History)
12 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2014-08-19 07:44:05 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Sibiao Luo 2013-07-18 06:56:38 EDT
Description of problem:
as subject.

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

How reproducible:

Steps to Reproduce:
1.boot guest with one virtconsole.
e.g:...-device virtio-serial-pci,id=virtio-serial0,max_ports=16,vectors=0,bus=pci.0,addr=0x3 -chardev socket,id=foo,path=/tmp/foo,server,nowait -device virtconsole,chardev=foo,name=com.redhat.rhevm.vdsm.1,bus=virtio-serial0.0,id=port1,nr=1
2.in guest configure my inittab to support serial console logins
  2.1. open /etc/inittab append:  s1:2345:respawn:/sbin/agetty -L -f /etc/issue 115200 ttyS1 vt100
  2.2. config guest kernel append:  console=ttyS1,115200
  2.3. open /etc/securetty  append : ttyS1
3.try to login the guest via virtconsole.
guest] # agetty /dev/hvc0 9600 vt100
host ] # nc -U /tmp/foo

Red Hat Enterprise Linux Server release 6.4 (Santiago)
Kernel 2.6.32-398.el6.x86_64 on an x86_64

dhcp-8-219.nay.redhat.com login: root

Actual results:
after step 3, the 'agetty /dev/hvc0 9600 vt100' will quit in guest after input the username and press 'Enter' keyboard.

Expected results:
it can login to guest succeesfully and can run some simple command.

Additional info:
# /usr/libexec/qemu-kvm -S -M rhel6.5.0 -cpu SandyBridge -enable-kvm -m 4096 -smp 4,sockets=2,cores=2,threads=1 -no-kvm-pit-reinjection -name sluo -uuid 43425b70-86e5-4664-bf2c-3b76699b8bec -rtc base=localtime,clock=host,driftfix=slew -device virtio-serial-pci,id=virtio-serial0,max_ports=16,vectors=0,bus=pci.0,addr=0x3 -chardev socket,id=foo,path=/tmp/foo,server,nowait -device virtconsole,chardev=foo,name=com.redhat.rhevm.vdsm.1,bus=virtio-serial0.0,id=port1,nr=1 -drive file=/home/RHEL6.5-20130712.n.0-6.5-Server-x64.qcow2,if=none,id=drive-system-disk,format=qcow2,cache=none,aio=native,werror=stop,rerror=stop,serial="QEMU-DISK1" -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-system-disk,id=system-disk,bootindex=1 -device virtio-balloon-pci,id=ballooning,bus=pci.0,addr=0x5 -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -netdev tap,id=hostnet0,vhost=on,script=/etc/qemu-ifup -device virtio-net-pci,netdev=hostnet0,id=virtio-net-pci0,mac=2C:41:38:B6:40:21,bus=pci.0,addr=0x6,bootindex=2 -drive file=/home/my-data-disk.qcow2,if=none,id=drive-data-disk,format=qcow2,cache=none,aio=native,werror=stop,rerror=stop,serial="QEMU-DISK2" -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-data-disk,id=data-disk,bootindex=3 -k en-us -boot menu=on -qmp tcp:0:4444,server,nowait -vnc :1 -spice port=5931,disable-ticketing -monitor stdio
Comment 1 Sibiao Luo 2013-07-18 06:58:09 EDT
I have disabled the selinux and iptables in both host and guest.
# setenforce 0
# service iptables stop
Comment 2 Sibiao Luo 2013-07-18 23:38:47 EDT
Use the TCP socket also hit the same issue that fail to login into guest event with only one virtconsole.
e.g:...-device virtio-serial-pci,id=virtio-serial0,max_ports=16,vectors=0,bus=pci.0,addr=0x3 -chardev socket,id=foo,host=localhost,port=12345,server,nowait -device virtconsole,chardev=foo,name=com.redhat.rhevm.vdsm.1,bus=virtio-serial0.0,id=port1,nr=1

Best Regards,

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