-
Notifications
You must be signed in to change notification settings - Fork 712
Description
Description
Following run has uploaded artifact containing cloud-init-output.log
, ha.std{out,err}.log
, and journal.log
.
https://github.com/lima-vm/lima/actions/runs/18526075404
ha.stderr.log
:
{"error":"rpc error: code = Unavailable desc = error reading from server: EOF","level":"warning","msg":"guest agent events closed unexpectedly","time":"2025-10-15T10:45:24Z"}
Around 2025-10-15T10:45:24Z
in journal.log
:
Oct 15 10:45:18 lima-default cloud-init[651]: + sudo /usr/local/bin/lima-guestagent install-systemd --debug=false --vsock-port 2222
Oct 15 10:45:19 lima-default sudo[1709]: runner : PWD=/home/runner.linux ; USER=root ; COMMAND=/usr/bin/diff -q /run/lima-boot-done /mnt/lima-cidata/meta-data
Oct 15 10:45:19 lima-default sudo[1709]: pam_unix(sudo:session): session opened for user root(uid=0) by runner(uid=501)
Oct 15 10:45:19 lima-default sudo[1712]: root : PWD=/ ; USER=root ; COMMAND=/usr/local/bin/lima-guestagent install-systemd --debug=false --vsock-port 2222
Oct 15 10:45:19 lima-default sudo[1709]: pam_unix(sudo:session): session closed for user root
Oct 15 10:45:19 lima-default sudo[1712]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Oct 15 10:45:19 lima-default agetty[1571]: could not get terminal name: -22
Oct 15 10:45:19 lima-default kernel: agetty[1571]: segfault at 0 ip 00007c0b78b99681 sp 00007ffc00d2c7d8 error 4 in libc.so.6[199681,7c0b78a28000+196000] likely on CPU 0 (core 0, socket 0)
Oct 15 10:45:19 lima-default kernel: Code: 84 00 00 00 00 00 0f 1f 00 f3 0f 1e fa 48 83 fa 01 7e 57 c4 41 01 ef ff 89 f8 09 f0 c1 e0 14 3d 00 00 00 f8 0f 87 a3 03 00 00 fe 6f 07 c5 fd 74 0e c5 85 74 d0 c5 ed df c9 c5 fd d7 c9 48 83
Oct 15 10:45:19 lima-default kernel: buildkit0: port 1(veth1c303502) entered blocking state
Oct 15 10:45:19 lima-default kernel: buildkit0: port 1(veth1c303502) entered forwarding state
Oct 15 10:45:20 lima-default cloud-init[651]: time="2025-10-15T10:45:19Z" level=info msg="File "/etc/systemd/system/lima-guestagent.service" already exists, overwriting"
Oct 15 10:45:20 lima-default cloud-init[651]: time="2025-10-15T10:45:20Z" level=info msg="Written file "/etc/systemd/system/lima-guestagent.service""
Oct 15 10:45:20 lima-default cloud-init[651]: time="2025-10-15T10:45:20Z" level=info msg="Executing: systemctl --system daemon-reload"
Oct 15 10:45:20 lima-default systemd[1]: Reload requested from client PID 1733 ('systemctl') (unit cloud-init-main.service)...
Oct 15 10:45:20 lima-default systemd[1]: Reloading...
Oct 15 10:45:22 lima-default sudo[1812]: runner : PWD=/home/runner.linux ; USER=root ; COMMAND=/usr/bin/diff -q /run/lima-boot-done /mnt/lima-cidata/meta-data
Oct 15 10:45:22 lima-default sudo[1812]: pam_unix(sudo:session): session opened for user root(uid=0) by runner(uid=501)
Oct 15 10:45:22 lima-default sudo[1812]: pam_unix(sudo:session): session closed for user root
Oct 15 10:45:22 lima-default systemd[1]: Reloading finished in 2455 ms.
Oct 15 10:45:22 lima-default cloud-init[651]: time="2025-10-15T10:45:22Z" level=info msg="Executing: systemctl --system enable lima-guestagent.service"
Oct 15 10:45:22 lima-default systemd[1]: serial-getty@ttyS0.service: Deactivated successfully.
Oct 15 10:45:23 lima-default systemd[1]: serial-getty@ttyS0.service: Scheduled restart job, restart counter is at 5.
Oct 15 10:45:23 lima-default systemd[1]: Started serial-getty@ttyS0.service - Serial Getty on ttyS0.
Oct 15 10:45:23 lima-default systemd[1]: Reload requested from client PID 1827 ('systemctl') (unit cloud-init-main.service)...
Oct 15 10:45:23 lima-default systemd[1]: Reloading...
Oct 15 10:45:23 lima-default containerd-rootless-setuptool.sh[1570]: time="2025-10-15T10:45:23Z" level=info msg="found worker "98wg5b70fpq9moc866ifjztbn", labels=map[org.mobyproject.buildkit.worker.containerd.namespace:default org.mobyproject.buildkit.worker.containerd.uuid:f96134ea-83e5-4fd5-8348-c68709481405 org.mobyproject.buildkit.worker.executor:containerd org.mobyproject.buildkit.worker.hostname:lima-default org.mobyproject.buildkit.worker.network:cni org.mobyproject.buildkit.worker.selinux.enabled:false org.mobyproject.buildkit.worker.snapshotter:overlayfs], platforms=[linux/amd64 linux/amd64/v2 linux/amd64/v3 linux/386]"
Oct 15 10:45:23 lima-default containerd-rootless-setuptool.sh[1570]: time="2025-10-15T10:45:23Z" level=info msg="found 1 workers, default="98wg5b70fpq9moc866ifjztbn""
Oct 15 10:45:23 lima-default containerd-rootless-setuptool.sh[1570]: time="2025-10-15T10:45:23Z" level=warning msg="currently, only the default worker can be used."
Oct 15 10:45:24 lima-default containerd-rootless-setuptool.sh[1570]: time="2025-10-15T10:45:24Z" level=info msg="running server on /run/user/501/buildkit-default/buildkitd.sock"
Oct 15 10:45:24 lima-default systemd[1]: Reloading finished in 1211 ms.
This seems to happen when the lima-guestagent
installed in the previous boot was stopped, updated, and started.
If lima-guestagent
is not updated and the startup options do not change, these steps should be skipped.
In addition, the impact on the hostagent should be minimized even if it is updated.