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 665227 - Entering screen to copy/scrollback mode caused guest deadlock
Summary: Entering screen to copy/scrollback mode caused guest deadlock
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Gerd Hoffmann
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 664635
Blocks: 580953
TreeView+ depends on / blocked
 
Reported: 2010-12-23 04:50 UTC by Amos Kong
Modified: 2015-05-25 00:06 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 664635
Environment:
Last Closed: 2011-06-01 15:57:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 3 Gerd Hoffmann 2011-06-01 15:57:12 UTC
As Eduardo sayed in bug 664635:

Just don't stop reading data, this is asking for trouble.

We could try to fix that by implementing flow control everythere, so the guest gets signaled via serial port status registers that the pipe is full and stops writing more.  This depends on pimping up qemu chardevs, which in turn depends on glib main loop, which pretty much implies it is RHEL-7 material.

I suspect that still wouldn't help much for linux kernel messages as the serial console writes are done syncronously.  You can see that even on bare metal, configure a serial line with 9600 baud and watch how this slows down the kernel boot.  In the end qemu wouldn't block, but the linux kernel would block instead.


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