Oak Containers logs contain fatal entries even in successful runs

[tiziano88]

I'm trying to debug a failure in #4596 , but I got sidetracked by the fact that the logs seem to point to errors, even though I switched back to main and re-ran those tests, and the errors are still in the logs (which means they were not really errors in the first place).

For instance, below, the PCI: Fatal: No config space access function found line should probably be silenced somehow? Also I am not sure whether systemd[1]: Failed to find module 'autofs4' is expected or not (that said, again, this is from a successful run).

stage0 INFO: starting...
stage0 INFO: Enabled SEV features: SevStatus(0x0)
stage0 DEBUG: early E820 entry: [0x0000000000000000-0x0000000000080000), len 524288, type RAM
stage0 DEBUG: early E820 entry: [0x0000000000080000-0x00000000000a0000), len 131072, type ACPI
stage0 DEBUG: early E820 entry: [0x00000000000a0000-0x00000000000f0000), len 327680, type RESERVED
stage0 DEBUG: early E820 entry: [0x00000000000f0000-0x0000000000100000), len 65536, type DISABLED
stage0 DEBUG: early E820 entry: [0x0000000000100000-0x0000000080000000), len 2146435072, type RAM
stage0 DEBUG: early E820 entry: [0x00000000feffc000-0x00000000ff000000), len 16384, type RESERVED
stage0 DEBUG: Kernel cmdline:  console=ttyS0 panic=-1 brd.rd_nr=1 brd.rd_size=1000000 brd.max_part=1 ip=10.0.2.15:::255.255.255.0::eth0:off quiet
stage0 DEBUG: Kernel image size 4883392
stage0 DEBUG: Kernel image start address 0x0000000002000000
stage0 DEBUG: Kernel entry point 0x0000000002000200
stage0 INFO: Using x2APIC for AP initialization.
stage0 DEBUG: Local APIC: ProcessorLocalApic { header: ControllerHeader { structure_type: 0, len: 8 }, processor_uid: 0, apic_id: 0, flags: LocalApicFlags(ENABLED) }
stage0 DEBUG: uninteresting structure: 1
stage0 DEBUG: uninteresting structure: 1
stage0 DEBUG: uninteresting structure: 4
stage0 INFO: Expected number of APs: 0, started number of APs: 0
stage0 DEBUG: Initial RAM disk size 2543183
stage0 DEBUG: Initial RAM disk address 0x000000003fd93000
stage0 DEBUG: Kernel image digest: [57, 23, 144, 252, 111, 82, 111, 45, 166, 174, 162, 99, 81, 47, 143, 210, 192, 15, 69, 149, 9, 6, 8, 123, 236, 32, 132, 45, 220, 229, 232, 231]
stage0 DEBUG: Kernel setup data digest: [134, 136, 17, 30, 54, 119, 99, 76, 216, 184, 77, 67, 128, 233, 24, 30, 94, 197, 237, 180, 58, 0, 30, 134, 36, 17, 19, 229, 139, 19, 20, 6]
stage0 DEBUG: Kernel image digest: [224, 33, 235, 146, 18, 177, 54, 32, 157, 189, 199, 48, 212, 5, 25, 212, 4, 112, 152, 217, 90, 131, 122, 238, 186, 172, 214, 227, 179, 138, 126, 35]
stage0 DEBUG: Initial RAM disk digest: [249, 224, 173, 101, 112, 114, 198, 18, 236, 33, 128, 103, 102, 37, 54, 10, 81, 74, 175, 171, 29, 163, 22, 17, 153, 23, 46, 167, 28, 232, 193, 192]
stage0 DEBUG: ACPI table generation digest: [150, 109, 254, 55, 53, 214, 181, 102, 178, 244, 56, 56, 135, 108, 99, 113, 206, 212, 109, 174, 4, 24, 17, 77, 247, 218, 202, 102, 90, 67, 154, 93]
stage0 DEBUG: E820 table digest: [87, 31, 66, 95, 95, 74, 83, 36, 195, 194, 198, 187, 88, 248, 46, 189, 197, 211, 98, 202, 3, 228, 129, 8, 0, 193, 141, 100, 193, 65, 185, 26]
stage0 INFO: jumping to kernel at 0x0000000002000200
PCI: Fatal: No config space access function found
mke2fs 1.47.0 (5-Feb-2023)
Creating filesystem with 250000 4k blocks and 62592 inodes
Filesystem UUID: 1bfe5145-9cf2-412f-b717-fd599179230e
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376

Allocating group tables: done
Writing inode tables: done
Writing superblocks and filesystem accounting information: done

systemd[1]: Failed to find module 'autofs4'
: Linux version 6.1.33 (@tzn0) (gcc (GCC) 12.3.0, GNU ld (GNU Binutils) 2.40) #3 SMP Thu Aug 24 09:02:21 BST 2023
: Command line:  console=ttyS0 panic=-1 brd.rd_nr=1 brd.rd_size=1000000 brd.max_part=1 ip=10.0.2.15:::255.255.255.0::eth0:off quiet -- --oak-dice=0x16000
: KERNEL supported cpus:
:   Intel GenuineIntel
:   AMD AuthenticAMD
: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
: x86/fpu: Supporting XSAVE feature 0x020: 'AVX-512 opmask'
: x86/fpu: Supporting XSAVE feature 0x040: 'AVX-512 Hi256'
...