Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1155702

Bug#1041891: cloud.debian.org: Debian VM doesn’t boot with "console=hvc0" kernel parameter

Show all headers | View raw

Package: cloud.debian.org
Severity: important
X-Debbugs-Cc: xycainoff@gmail.com

Dear Maintainer,

I've tried to run "genericcloud" arm64 image on QEMU with "device virtconsole" argument and direct kernel boot with "console=hvc0" kernel parameter. 
When "hvc0" is the only console argument in kernel parameters - debian doesn't boot. 
But when i configure additional console argument like this: "console=ttyAMA0 console=hvc0" - it boots normally. 
In this case "/sys/class/tty/console/active" contains both consoles "ttyAMA0 hvc0". 
However "serial-getty" doesn't start at hvc0 as expected. Systemd has to spawn getty on hvc0 when it's present. 
I've tried to boot VM using GRUB with 'GRUB_CMDLINE_LINUX="console=hvc0"' option. 
It runs - but ttyAMA0 activates anyway and "/sys/class/tty/console/active" again contains both consoles "ttyAMA0 hvc0". 
I've tested debian-12-genericcloud-arm64 and debian-11-genericcloud-arm64 images with same result. 
Noteworthy i've tried another distributions (Ubuntu, Fedora and openSUSE "cloud" arm64 images) and they all work with "hvc0" configured as the only console, "/sys/class/tty/console/active" contains only "hvc0" and serial-getty automatically started on hvc0. 

Back to linux.debian.bugs.dist | Previous | Next | Find similar | Unroll thread

Thread

Bug#1041891: cloud.debian.org: Debian VM doesn’t boot with "console=hvc0" kernel parameter Azat Khusainov <xycainoff@gmail.com> - 2023-07-25 00:10 +0200

csiph-web