Timeline for Debian VM doesn’t boot on QEMU with "console=hvc0" kernel parameter
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 16, 2023 at 13:52 | vote | accept | xycainoff | ||
| Aug 20, 2023 at 21:48 | answer | added | Chetan Reddy | timeline score: 2 | |
| Jul 24, 2023 at 20:51 | history | edited | xycainoff | CC BY-SA 4.0 | tested other linux distributions - apparently only Debian has the problem |
| Jul 24, 2023 at 20:35 | comment | added | xycainoff | I've tested Ubuntu and openSUSE as well - works like a charm. If /dev/hvc0 is presented in system - systemd starts serial-getty on it. And if i configure hvc0 as only console argument in kernel parameters - /sys/class/tty/console/active contains only hvc0 without ttyAMA0 or other tty. As a result i get kernel messages AND getty on hvc0. | |
| Jul 23, 2023 at 19:59 | comment | added | xycainoff | Nevertheless one of the goals was to get getty on hvc0. In theory systemd has to start getty on console specified in kernel parameters. Furthermore, i was surprised to know, that systemd has to spawn getty on the first special VM console like /dev/hvc0 when it's available, even if it wasn't configured in kernel parameters. Unfortunately it doesn't work in Debian. I tested Fedora - it works as expected: if hvc0 is present [email protected] started automatically. | |
| Jul 23, 2023 at 19:57 | comment | added | xycainoff | Tried to boot with GRUB - it works. However /sys/class/tty/console/active contains both consoles ttyAMA0 hvc0 and /proc/cmdline contains BOOT_IMAGE=/boot/vmlinuz-6.1.0-10-cloud-arm64 root=UUID=104c538b-bea1-443e-b4b1-95cc2068706f ro console=hvc0. Despite kernel parameters contain only single console argument, ttyAMA0 activated by default anyway. Result is the same if i’d use direct kernel boot with -append 'root=UUID=104c538b-bea1-443e-b4b1-95cc2068706f console=ttyAMA0 console=hvc0' argument in QEMU command. | |
| Jul 20, 2023 at 11:42 | comment | added | xycainoff | @NicolasFormichella Sadly it's the very problem i face: when i configure single console hvc0 it doesn't boot, but when configure ttyAMA0 AND hvc0 together - it boots normally. Btw, i dont use GRUB, i boot directly to kernel and specify kernel parameters by -append argument in QEMU command. Do you think i should try with GRUB? | |
| Jul 19, 2023 at 10:55 | comment | added | Nicolas Formichella | Can you try poping into GRUB and replace console=ttyAMA0 by console=hvc0 and see what it does? | |
| S Jul 18, 2023 at 22:22 | review | First questions | |||
| Jul 19, 2023 at 5:20 | |||||
| S Jul 18, 2023 at 22:22 | history | asked | xycainoff | CC BY-SA 4.0 |