patches and low-level development discussion
 help / color / mirror / code / Atom feed
From: Alyssa Ross <hi@alyssa.is>
To: colbyt <colby@colbyt.com>
Cc: devel@spectrum-os.org
Subject: Re: [PATCH 5/6] installer: suppress boot console status noise
Date: Fri, 26 Jun 2026 16:46:41 +0200	[thread overview]
Message-ID: <87cxxdfjfy.fsf@alyssa.is> (raw)
In-Reply-To: <528a34214942d7b316fde5510da03ef91eb9d2cd.1782409229.git.colby@colbyt.com>

[-- Attachment #1: Type: text/plain, Size: 2290 bytes --]

colbyt <colby@colbyt.com> writes:

> The installer can show systemd or udev messages between Plymouth exiting
> and cage starting, which breaks the intended flicker-free graphical
> handoff.
>
> Add quiet/systemd/udev kernel parameters to suppress status output and
> stop forcing systemd.journald.forward_to_console in the QEMU runner.
> This keeps the installer VM aligned with the quiet graphical boot path.
>
> Signed-off-by: colbyt <colby@colbyt.com>
> ---
>  release/installer/configuration.nix | 9 ++++++++-
>  release/installer/run-vm.nix        | 5 +----
>  2 files changed, 9 insertions(+), 5 deletions(-)
>
> diff --git a/release/installer/configuration.nix b/release/installer/configuration.nix
> index 3f9ef24..daaf5b7 100644
> --- a/release/installer/configuration.nix
> +++ b/release/installer/configuration.nix
> @@ -11,7 +11,14 @@ in
>    imports = [ (modulesPath + "/profiles/all-hardware.nix") ];
>  
>    boot.consoleLogLevel = lib.mkDefault 2;
> -  boot.kernelParams = [ "udev.log_priority=5" ];
> +  boot.kernelParams = [
> +    "quiet"
> +    "loglevel=3"
> +    "systemd.show_status=false"
> +    "rd.systemd.show_status=false"
> +    "udev.log_level=3"
> +    "rd.udev.log_level=3"
> +  ];

Why 3 in particular?  Experimentation?  Inspiration from some other
distribution?

>    boot.initrd.verbose = false;
>  
>    boot.kernelPackages = pkgs.linuxPackages_latest;
> diff --git a/release/installer/run-vm.nix b/release/installer/run-vm.nix
> index b9907f7..6639c8b 100644
> --- a/release/installer/run-vm.nix
> +++ b/release/installer/run-vm.nix
> @@ -40,8 +40,5 @@ writeShellScript "run-spectrum-installer-vm.sh" ''
>      -drive file=/proc/self/fd/3,format=raw,if=virtio \
>      -kernel ${installer.kernel} \
>      -initrd ${installer.initramfs} \
> -    -append ${escapeShellArg (toString [
> -      installer.kernelParams
> -      "systemd.journald.forward_to_console"
> -    ])}
> +    -append ${escapeShellArg installer.kernelParams}
>  '') (_: {})

The divergence here was intentional, since in development it's very
useful to be able to see logs on the serial console, and it should have
a minimal impact on anything else.  Did you see this causing problems
with flicker-free boot or something?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2026-06-26 14:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-25 17:48 [PATCH 0/6] cloud-hypervisor v52 and VM runtime fixes colbyt
2026-06-25 17:48 ` [PATCH 1/6] pkgs/skaware: vendor backported patches colbyt
2026-06-26 13:39   ` Alyssa Ross
2026-06-25 17:48 ` [PATCH 2/6] pkgs/cloud-hypervisor: update GPU patchset to v52 colbyt
2026-06-26 14:06   ` Alyssa Ross
2026-06-25 17:48 ` [PATCH 3/6] vm: use vhost-user networking for crosvm colbyt
2026-06-26 14:45   ` Alyssa Ross
2026-07-02  9:07   ` Alyssa Ross
2026-06-25 17:48 ` [PATCH 4/6] Documentation: use crosvm GPU socket-path option colbyt
2026-06-26 14:18   ` Alyssa Ross
2026-06-25 17:48 ` [PATCH 5/6] installer: suppress boot console status noise colbyt
2026-06-26 14:46   ` Alyssa Ross [this message]
2026-06-26 19:09     ` colby
2026-07-02 11:44       ` Alyssa Ross
2026-06-25 17:48 ` [PATCH 6/6] start-vmm: test GPU socket configuration colbyt
2026-06-26 14:18   ` Alyssa Ross

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=87cxxdfjfy.fsf@alyssa.is \
    --to=hi@alyssa.is \
    --cc=colby@colbyt.com \
    --cc=devel@spectrum-os.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.
Code repositories for project(s) associated with this public inbox

	https://spectrum-os.org/git/crosvm
	https://spectrum-os.org/git/doc
	https://spectrum-os.org/git/mktuntap
	https://spectrum-os.org/git/nixpkgs
	https://spectrum-os.org/git/spectrum
	https://spectrum-os.org/git/ucspi-vsock
	https://spectrum-os.org/git/www

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).