Bug 755463 - Redhat 5.7 xen kernel will not show all the output in xvc
Summary: Redhat 5.7 xen kernel will not show all the output in xvc
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel-xen
Version: 5.7
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: rc
: 5.7
Assignee: Xen Maintainance List
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-21 08:30 UTC by zou.chris
Modified: 2018-11-26 18:16 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
RHEL5.7 Xen
Last Closed: 2011-12-13 12:57:03 UTC
Target Upstream Version:


Attachments (Terms of Use)
cd5f91c [xen] allow booting with broken serial hardware (7.06 KB, text/plain)
2011-12-14 08:59 UTC, Laszlo Ersek
no flags Details

Description zou.chris 2011-11-21 08:30:28 UTC
Description of problem:


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


How reproducible:


Steps to Reproduce:
1. Install Redhat Enterprise Linux 5.7 64bit with Xen enabled.
2. Change grub.conf:
    a. append the following to the kernel line:
        com1=9600,8n1 console=com1,vga
    b. append the following to the vmlinuz line:
        console=xvc xencons=xvc
3. Change /etc/inittab to contain the following line:
    xv:2345:respawn:/sbin/agetty xvc0 9600 vt100
4. Add xvc0 to /etc/securetty.
5. Enable com1 console redirection in BIOS setup and boot to system.
6. Login from com1 via a serial cable.
7. Issue "ls -R /":
    ==> fail, command exit in few seconds, but not all of the output of this command is shown.
  
Actual results:


Expected results:


Additional info:

Comment 1 Laszlo Ersek 2011-12-13 12:57:03 UTC
Using hvc (or perhaps xvc too) between dom0 and Xen should take care of flow
control from dom0 to Xen.

Dependent on: - the hardware of both host and guest, - and possibly the wiring
(pinout) of the null-modem cable connecting them,

the serial output of Xen can behave differently. We have checked the above
testcase in two setups. The host sides running Xen were identical (HP
workstations with real serial ports). The cables were separate objects, and one
client used a USB-to-Serial converter, the other a real serial port.
Surprisingly, the setup with USB-to-Serial converter works perfectly (doesn't
lose a single byte), while the serial-to-serial setup lists about 10K and then
stops printing anything.

However, this dropping behavior of RHEL-5 Xen is intentional. See bug 518338
and commit cd5f91c7 (called
"xen-allow-booting-with-broken-serial-hardware.patch" in the SRPM.) The idea
behind that patch is: instead of being blocked by potentially broken hardware
forever, remove flow control and start dropping data in *big* chunks, until the
output buffer sinks below the half mark. This is the explanation why serial
output can be skippy, and sometimes just "stop" -- the output backlog is
constantly kept over the half mark.

Note that said patch adds the SERIAL_NEVER_DROP_CHARS macro, which reintroduces
flow control. I guess one could experiment with rebuilding the SRPM, #defining
the macro in the SPEC file or somewhere else, but it's untested and
unsupported.

The behavior being deliberate, I'm closing this bug as WONTFIX.

Comment 2 Laszlo Ersek 2011-12-13 12:57:52 UTC
Actually: due to the above, this is not a bug, but a feature.

Comment 3 zou.chris 2011-12-14 00:20:30 UTC
hi I was not authorized to access bug #518338,would you mind coping all the words to me, many thanks

Comment 4 Laszlo Ersek 2011-12-14 08:59:36 UTC
Created attachment 546629 [details]
cd5f91c [xen] allow booting with broken serial hardware

(In reply to comment #3)
> hi I was not authorized to access bug #518338,would you mind coping all the
> words to me, many thanks

Unfortunately I can't do that. However, the patch file that I mentioned before
has an extensive description and is public. I'm attaching it for your
convenience.

Comment 6 zou.chris 2011-12-14 09:03:22 UTC
Many thanks. We will have a try.


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