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:
Boot a rhel6 or rhel5 guest,and then boot into single user mode by "init 1" or add "single" to kernel command line then reboot, guest stops and can not accept any input.
Version-Release number of selected component (if applicable):
kernel-2.6.32-220.el6.x86_64
qemu-kvm-0.12.1.2-2.209.el6
How reproducible:
Always
Steps to Reproduce:
1.Boot a RHEL guest.
/usr/libexec/qemu-kvm -M rhel6.2.0 -enable-kvm -m 1024 -smp 1,sockets=1,cores=1,threads=1 -name rhel6.2-64 -uuid b1af8ea9-8966-fd2a-6567-5ecbde68f116 -rtc base=utc -drive file=/root/RHEL-Server-6.2-64-virtio.qcow2,if=none,id=drive-ide0-0-0,format=qcow2,cache=none -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -netdev tap,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:8c:b4:ec,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -usb -vnc :10 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -drive file=/home/floppy.img,if=none,id=drive-fdc0-0-0,format=raw,cache=none -global isa-fdc.driveA=drive-fdc0-0-0 -monitor stdio
2.Add "single" to kernel command line.
3.Reboot guest to boot into the single user mode
Actual results:
Guest stops at reboot and can not boot into single user mode.
Expected results:
Guest should boot into single user mode.
Additional info:
Test the following 2 scenarios:
(1) Remove "console=tty0 console=ttyS0,115200" from guest kernel command line, and then boot into single user mode. => Succeed.
(2) Add "console=tty0 console=ttyS0,115200" in guest kernel command line and boot into single user mode. Guest stops as bug description, but I can log into guest from the serial.
(Boot guest with serial device "-chardev socket,id=charserial0,path=/tmp/qzhang,server,nowait -device isa-serial,chardev=charserial0,id=serial0", using "nc -U /tmp/qzhang to connect the guest.)
Based on above, this is not a bug, close it. Please correct me if I am wrong.