docs: how to measure a normal boot of the test VM
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 file changed
+5
-1
@@ -36,4 +36,8 @@ Pinning saves a full rebuild when only testing.
|
||||
|
||||
## Boot time
|
||||
|
||||
Measure it over ssh with `systemd-analyze`, `systemd-analyze blame` and `systemd-analyze critical-chain`. In `blame`, the `.device` units only show when udev announced the device, not time spent, so filter them out. The test VM has one CPU and always does a first boot (setup, growfs), so a real VM boots faster.
|
||||
Measure it over ssh with `systemd-analyze`, `systemd-analyze blame` and `systemd-analyze critical-chain`. In `blame`, the `.device` units only show when udev announced the device, not time spent, so filter them out.
|
||||
|
||||
The test VM always does a first boot (setup, growfs, enrolling the Secure Boot keys). To measure a normal boot, reboot it with `systemctl reboot` as root: the throwaway copy lasts until qemu exits. Compare a few boots, since timings vary.
|
||||
|
||||
To see what systemd waits for, boot with debug logging without a rebuild: `mkosi --kernel-command-line-extra=systemd.log_level=debug vm`.
|
||||
Reference in new issue
Block a user