This is probably related to a systemd timeout as this is an x86-64 image booted on an arm host: [ 147.971538] systemd[1]: Reached target Preparation for Network. [ 148.116720] systemd[1]: FUSE Control File System was skipped because of a failed condition check (ConditionPathExists=/sys/fs/fuse/connections). [ 148.190434] systemd[1]: Kernel Configuration File System was skipped because of a failed condition check (ConditionPathExists=/sys/kernel/config). [ 148.375518] systemd[1]: Rebuild Hardware Database was skipped because all trigger condition checks failed. [ 148.417587] systemd[1]: Platform Persistent Storage Archival was skipped because of a failed condition check (ConditionDirectoryNotEmpty=/sys/fs/pstore). [ 149.006197] systemd[1]: Starting Create System Users... [ 154.734303] systemd[1]: Finished Create System Users. [ 155.372344] systemd[1]: Starting Create Static Device Nodes in /dev... [ 160.276587] systemd[1]: Finished Create Static Device Nodes in /dev. [ 160.397531] systemd[1]: Reached target Preparation for Local File Systems. [ 160.999976] systemd[1]: Mounting /var/volatile... [ 162.857502] systemd[1]: Starting Rule-based Manager for Device Events and Files... [ 164.161788] systemd[1]: Mounted /var/volatile. [ 165.356273] systemd[1]: Starting Bind mount volatile /var/cache... [ 166.533362] systemd[1]: Starting Bind mount volatile /var/lib... [ 168.309678] systemd[1]: Starting Bind mount volatile /var/spool... [ 170.094700] systemd[1]: Starting Bind mount volatile /srv... [ 171.550794] systemd[1]: Started Journal Service. [ 214.166352] systemd-journald[170]: Received client request to flush runtime journal. [ 219.562548] clocksource: timekeeping watchdog on CPU1: hpet retried 2 times before success [ 308.066981] clocksource: timekeeping watchdog on CPU2: hpet wd-wd read-back delay of 17748510ns [ 308.146923] clocksource: wd-tsc-wd read-back delay of 1644830ns, clock-skew test skipped! [ 336.096488] virtio_net virtio0 enp0s1: renamed from eth0 Press Enter for maintenance (or press Control-D to continue): https://autobuilder.yoctoproject.org/typhoon/#/builders/127/builds/160/steps/14/logs/stdio https://autobuilder.yoctoproject.org/typhoon/#/builders/127/builds/128/steps/14/logs/stdio https://autobuilder.yoctoproject.org/typhoon/#/builders/127/builds/120/steps/14/logs/stdio
Almost certainly due to the lack of KVM acceleration
https://autobuilder.yoctoproject.org/typhoon/#builders/127/builds/170/steps/14/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/127/builds/209/steps/14/logs/stdio oe-selftest-armhost ubuntu2004-arm-1
https://autobuilder.yoctoproject.org/typhoon/#/builders/127/builds/271/steps/14/logs/stdio https://autobuilder.yoctoproject.org/typhoon/#/builders/127/builds/284/steps/14/logs/stdio https://autobuilder.yoctoproject.org/typhoon/#/builders/127/builds/283/steps/14/logs/stdio https://autobuilder.yoctoproject.org/typhoon/#/builders/127/builds/275/steps/14/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/127/builds/347/steps/14/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/127/builds/388/steps/14/logs/stdio
Possibly improved by moving oe-selftest-armhost to qemuarm64, patches posted to oe-core.
Optimistically closing now that I hope this is due to timeouts caused by emulating qemux86-64 on aarch64.