This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Serial console problem with Xen 3.0

To: "Stephen C. Tweedie" <sct@xxxxxxxxxx>, "Amitayu Das" <amitayudas@xxxxxxxxx>
Subject: Re: [Xen-devel] Serial console problem with Xen 3.0
From: "Michael Paesold" <mpaesold@xxxxxx>
Date: Fri, 7 Apr 2006 15:59:01 +0200
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 07 Apr 2006 06:59:32 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <5f74ce410604042140y3f9c2154pc2410cc73654d500@xxxxxxxxxxxxxx> <1144416460.3405.2.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Stephen C. Tweedie wrote:
On Wed, 2006-04-05 at 00:40 -0400, Amitayu Das wrote:

1. I can boot normal Linux FC4 kernel and direct its output to serial
console (and see the messages in a separate monitor) using the options
as mentioned in the grub.conf.
    If I do the exactly the same (meaning, whatever you can see as
uncommeted lines in the xen-related portion of the grub.conf),
    I can't see the messages in the separate monitor.

Right, because you commented out the xen.gz com1=... line, so there's no
HV serial console.  You need that enabled.

2. If I uncomment the third line in the following:
#       kernel /xen.gz dom0_mem=131072 com1=9600,8n1

then Xen even does not boot up.

I've seen this a lot --- for me, adding "sync_console" to that xen.gz
line cures it.  Does that help for you?

Me too. Adding "sync_console" at least repaired the console *output*. I still have the problem that keyboard input does not reach linux, as it seems. Here is my config:

serial --unit=0 --speed=38400 --word=8 --parity=no --stop=1
terminal --timeout=10 serial console
title CentOS (2.6.16-2.EL4xen0)
       root (hd0,0)
       kernel /xen.gz-2.6.16-2.EL4 com1=38400,8n1 conswitch=s sync_console
module /vmlinuz-2.6.16-2.EL4xen0 ro root=LABEL=/1 console=tty0 console=ttyS0,38400n8
       module /initrd-2.6.16-2.EL4xen0.img

Using the same config for native linux gives me a working console access (NB. I have agetty in inittab). In Xen/Linux I get all boot messages (from linux and Xen), but when I hit the login prompt, no keyboard input is excepted. I am using minicom on the other side of the cable.

Additionally, pressing CTRL-A (or CTRL-S after changing the key) three times does *not* give me access to the Xen console.

Any additional hints how I could get this working? (NB. this is xen-unstable, just a two days old, on x86 with an Intel 7210 board).

Best Regards,
Michael Paesold

Xen-devel mailing list