xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] linux-2.6.18/xencons: generalize use of add_preferred_console()
Date: Thu, 6 Feb 2014 23:53:34 +0100	[thread overview]
Message-ID: <20140206225334.GA21743@aepfle.de> (raw)
In-Reply-To: <52AAE1C2020000780010CE39@nat28.tlf.novell.com>

On Fri, Dec 13, Jan Beulich wrote:

> Changeset 762:a070228ac76e ("add hvc compatibility mode to xencons"
> added this call just for the HVC case, without giving any reason why
> HVC would be special in this regard. Use the call for all cases.

> +++ b/drivers/xen/console/console.c
> @@ -236,6 +234,8 @@ static int __init xen_console_init(void)
>  
>  	wbuf = alloc_bootmem(wbuf_size);
>  
> +	if (!is_initial_xendomain())
> +		add_preferred_console(kcons_info.name, xc_num, NULL);
>  	register_console(&kcons_info);

Why is dom0 special in this case anyway? At least with SLE12, when Xen
is booted with 'console=com1 com1=115200' and the kernel is booted
without any console= or xencons=, kcons_info.index is still -1 and as a
result xvc-1 is registered as name for xvc0. This confuses systemd
because kernel name and console name do not match, so login via serial
is not possible.

When add_preferred_console is called uncondtionally the login on serial
works as expected.


Olaf

  reply	other threads:[~2014-02-06 22:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-13  9:30 [PATCH] linux-2.6.18/xencons: generalize use of add_preferred_console() Jan Beulich
2014-02-06 22:53 ` Olaf Hering [this message]
2014-02-07  8:18   ` Jan Beulich
2014-02-07  8:32     ` Olaf Hering
2014-02-07  9:12       ` Jan Beulich
2014-02-07 10:07         ` Olaf Hering
2014-02-07 10:24           ` Jan Beulich
2014-02-07 12:30             ` Olaf Hering
2014-02-07 12:38               ` Jan Beulich

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=20140206225334.GA21743@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=JBeulich@suse.com \
    --cc=xen-devel@lists.xenproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).