Skip to content

vm: autologin on the serial console for images without cloud-init #80

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
MickLesk merged 1 commit into from
Sep 30, 2026
Merged

vm: autologin on the serial console for images without cloud-init #80

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions incus/vm-core.func
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1569,13 +1569,15 @@ vm_enable_consoles() {
# trixie no longer accepts an empty one - so the getty above puts a prompt
# nobody can answer on tty1. Decided in the guest: the caller's
# USE_CLOUD_INIT is only set once vm_prompt_cloud_init has run. Template
# level, the way Debian ships the serial one, so it holds for whichever
# instance systemd starts.
# level, so it holds for whichever instance systemd starts. The nocloud
# images no longer ship an autologin of their own on either console.
_vm_customize "console autologin" "$image" --run-command \
'if ! command -v cloud-init >/dev/null 2>&1; then
mkdir -p /etc/systemd/system/getty@.service.d
mkdir -p /etc/systemd/system/getty@.service.d /etc/systemd/system/serial-getty@.service.d
printf "[Service]\nExecStart=\nExecStart=-/sbin/agetty --autologin root --noclear %%I \$TERM\n" \
>/etc/systemd/system/getty@.service.d/autologin.conf
printf "[Service]\nExecStart=\nExecStart=-/sbin/agetty --autologin root --keep-baud 115200,57600,38400,9600 %%I \$TERM\n" \
>/etc/systemd/system/serial-getty@.service.d/autologin.conf
fi'

_vm_customize "grub console" "$image" --run-command \
Expand Down
9 changes: 5 additions & 4 deletions pve/vm-core.func
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2023,14 +2023,15 @@ vm_enable_consoles() {
# trixie no longer accepts an empty one - so the getty above puts a prompt
# nobody can answer on tty1. Decided in the guest: the caller's
# USE_CLOUD_INIT is only set once vm_prompt_cloud_init has run.
# Template level, the way Debian ships the serial one, so it holds for
# whichever instance systemd starts. serial-getty is left alone - those
# images already autologin there, and it carries --keep-baud.
# Template level, so it holds for whichever instance systemd starts. The
# nocloud images no longer ship an autologin of their own on either console.
_vm_customize "console autologin" "$image" --run-command \
'if ! command -v cloud-init >/dev/null 2>&1; then
mkdir -p /etc/systemd/system/getty@.service.d
mkdir -p /etc/systemd/system/getty@.service.d /etc/systemd/system/serial-getty@.service.d
printf "[Service]\nExecStart=\nExecStart=-/sbin/agetty --autologin root --noclear %%I \$TERM\n" \
>/etc/systemd/system/getty@.service.d/autologin.conf
printf "[Service]\nExecStart=\nExecStart=-/sbin/agetty --autologin root --keep-baud 115200,57600,38400,9600 %%I \$TERM\n" \
>/etc/systemd/system/serial-getty@.service.d/autologin.conf
fi'

# A getty alone only gets you a login prompt after boot -- the kernel still
Expand Down
Loading