[google/syzkaller] 77bc2e: vm/adb, docs/linux: allow to configure boot comple...

0 views
Skip to first unread message

Oleg Kulachenko

unread,
Mar 19, 2026, 10:21:27 AM (2 days ago) Mar 19
to syzk...@googlegroups.com
Branch: refs/heads/gh-readonly-queue/master/pr-6942-bd6dcb30873a835583692eaa69f3bafebcba1cfd
Home: https://github.com/google/syzkaller
Commit: 77bc2e1a1faaf378139679533bc0d5c356499a0b
https://github.com/google/syzkaller/commit/77bc2e1a1faaf378139679533bc0d5c356499a0b
Author: Oleg Kulachenko <vvar...@gmail.com>
Date: 2026-03-19 (Thu, 19 Mar 2026)

Changed paths:
M CONTRIBUTORS
M docs/linux/setup_linux-host_android-device_arm-kernel.md
M docs/linux/setup_linux-host_android-virtual-device_x86-64-kernel.md
M vm/adb/adb.go
A vm/adb/adb_test.go

Log Message:
-----------
vm/adb, docs/linux: allow to configure boot completion service

Currently waitForBootCompletion waits for the 'systemui' process
to determine if the Android device has finished booting. This works
for regular Android devices, but when testing QEMU Android and AOSP
builds without SystemUI, users need to wait for other services like
'servicemanager'.

Add a new 'boot_service' configuration option that allows users to
specify which service to wait for during boot completion. The default
value is 'systemui' to maintain backward compatibility.

Example configuration:

{
"type": "adb",
"vm": {
"devices": ["1234567890"],
"boot_service": "servicemanager"
}
}


Commit: 2375800d36b99e94605971217e287fc7dab44319
https://github.com/google/syzkaller/commit/2375800d36b99e94605971217e287fc7dab44319
Author: Oleg Kulachenko <vvar...@gmail.com>
Date: 2026-03-19 (Thu, 19 Mar 2026)

Changed paths:
M vm/adb/adb.go

Log Message:
-----------
vm/adb: mark boot as successful

When running Android in QEMU with A/B slot configuration, it can be
difficult to configure SwitchRoot in the bootloader. Without proper
bootloader setup, the bootloader tracks failed boots and may switch
to a different slot after reaching the limit (typically 3 failed boots).

Call 'bootctl mark-boot-successful' after each successful boot to
prevent slot switching during fuzzing. n non-A/B devices,
the command does not return an error.


Compare: https://github.com/google/syzkaller/compare/77bc2e1a1faa%5E...2375800d36b9

To unsubscribe from these emails, change your notification settings at https://github.com/google/syzkaller/settings/notifications

Oleg Kulachenko

unread,
Mar 19, 2026, 10:33:51 AM (2 days ago) Mar 19
to syzk...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages