All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@citrix.com>
To: Giridhar Maruthy <giridhar.maruthy@linaro.org>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
	Julien Grall <julien.grall@linaro.org>,
	xen-devel <xen-devel@lists.xen.org>
Subject: Re: [XenARM]  Testing xen-arm on Arndale
Date: Thu, 18 Jul 2013 14:54:11 +0100	[thread overview]
Message-ID: <51E7F383.6090709@citrix.com> (raw)
In-Reply-To: <CAHuqX+EB=T+zp5RZdJOuS91=Yfi=YrAWd2eXatJwezUcvWE1Kw@mail.gmail.com>

On 07/18/2013 02:43 PM, Giridhar Maruthy wrote:
> I am trying to use linaro quantal file system for dom0, but facing a
> problem with serial console.
> 
> I see the following lines getting repeated
> 
> "init: auto-serial-console main process ended, respawning"
> 
> When I modify dom0 kernel bootargs to include init=/bin/sh, I get the prompt.
> 
> The script /bin/auto-serial-console has cases to handle only tty* as
> the console. Do we have to modify it to handle hvc as serial console?

I have created a file /etc/init/hvc0.conf with the following data:
==================================================================
# hvc0 - getty
#
# This service maintains a getty on tty1 from the point the system is
# started until it is shut down again.

start on stopped rc RUNLEVEL=[2345] and (
            not-container or
            container CONTAINER=lxc or
            container CONTAINER=lxc-libvirt)

stop on runlevel [!2345]

respawn
exec /sbin/getty -8 38400 hvc0
==================================================================

This file will start a service and allow you to access to the console.

In future, I think Linaro quantal must be able to handle hvc0 without
any modifications.

Cheers,

-- 
Julien

  reply	other threads:[~2013-07-18 13:54 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJWjLtp3yQhL1x9L=Lb6zq19Qc0dJwfjarwgd1NxFYNxXfER=g@mail.gmail.com>
2013-03-26 16:04 ` Testing xen-arm on Arndale Anthony PERARD
2013-03-26 19:29   ` Julien Grall
2013-03-27  0:40     ` Sengul Thomas
2013-03-27 10:48       ` [XenARM] " Stefano Stabellini
2013-03-27  8:23     ` Sengul Thomas
2013-03-27 11:42       ` Sengul Thomas
2013-03-27 11:57         ` Stefano Stabellini
2013-03-28 10:25           ` Sengul Thomas
2013-03-28 12:09             ` Stefano Stabellini
2013-03-29  6:57               ` Sengul Thomas
2013-03-29 12:42                 ` Julien Grall
2013-03-29 12:50                   ` Stefano Stabellini
2013-03-30  3:40                   ` Sengul Thomas
2013-04-01 14:15                     ` Julien Grall
2013-04-03  9:28                       ` See-Hwan Yoo
2013-04-03 10:52                         ` Stefano Stabellini
2013-04-03 11:57                           ` See-Hwan Yoo
2013-04-03 13:22                             ` Julien Grall
2013-04-04  2:06                               ` See-Hwan Yoo
2013-04-04 13:38                                 ` Julien Grall
2013-04-05  1:26                                   ` See-Hwan Yoo
2013-04-05 11:34                                     ` Stefano Stabellini
2013-04-05 13:34                                       ` Julien Grall
2013-04-03 13:37                             ` Stefano Stabellini
2013-04-10 11:44                               ` Ian Campbell
2013-07-16  6:33     ` [XenARM] " Giridhar Maruthy
     [not found]       ` <CAHuqX+GCwz8RhC3AxKKWzF5PKf4MWWqboHnHiqde7GfzpZ+T6w@mail.gmail.com>
2013-07-17  9:39         ` Julien Grall
2013-07-17 12:53           ` Giridhar Maruthy
2013-07-17 16:38             ` Julien Grall
2013-07-18  9:58               ` Giridhar Maruthy
2013-07-18 13:43                 ` Giridhar Maruthy
2013-07-18 13:54                   ` Julien Grall [this message]
2013-07-18 14:22                     ` Giridhar Maruthy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51E7F383.6090709@citrix.com \
    --to=julien.grall@citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=giridhar.maruthy@linaro.org \
    --cc=julien.grall@linaro.org \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.