Bug#769406: Serial console not set up after serial install

[Bernhard Schmidt <berni@birkenwald.de>]

On Wed, Dec 03, 2014 at 11:29:00PM +0100, Samuel Thibault wrote:

Hi,

> Geert Stappers, le Wed 03 Dec 2014 22:30:39 +0100, a écrit :
> > Jan  1 21:50:07 kernel: [    0.000000] Command line: BOOT_IMAGE=http://alpaca.gpm.stappers.nl/d-i/jessie/amd64/linux vga=normal console=ttyS0,19200,n8 -- initrd=http://alpaca.gpm.stappers.nl/d-i/jessie/amd64/initrd.gz 
> 
> Options to be propagated to the installed kernel have to be put after
> --.  With the recent kernel change which lead to #764675, it's actually
> now ---, so it'd be something like
> 
> > vga=normal initrd=http://alpaca.gpm.stappers.nl/d-i/jessie/amd64/initrd.gz --- console=ttyS0,19200,n8 
> 
> How were this console= parameter added precisely?
> 
> I have added to the manual's Boot Parameters section an explicit mention
> of this.

I can confirm that both 

	[...] console=ttyS0,115200n8 -- console=ttyS0,115200n8

and

	[...] --- console=ttyS0,115200n8

work as expected. 

Part of the problems described here come from #764675. 

I think Florian's problems are actually a missing feature. For SysVinit
and upstart there is code in finish-install that enables a serial
console in inittab or upstart when it is detected (_not_ triggered by
the kernel command line)

http://sources.debian.net/src/finish-install/2.56/finish-install.d/90console/

systemd-enabled fresh systems do not have an inittab, so this entire
code is more or less a no-op. systemd systems get a serial console when
a serial console is specified on the kernel command line, which is most
likely either not done by virtinst or used in the wrong way (without
---, see above).

Takatsugu's comment is related to Bug #760947 .

Best Regards,
Bernhard