Missing /sys/devices/virtual/dmi on Raspberry Pi

[PaavoHelde]

After upgrading our aws-cpp-sdk version to the tip of the main branch, we started to see some new log messages from InitAPI() which were not there before, about files in /sys/devices/virtual/dmi (our Raspberry Pi box does not have such directory). The library seems to work fine, it's just the log messages. Am I doing something wrong myself or are these log messages expected?

`[ERROR] 2025-05-05 08:39:32.159 common-io [547798657344] static: Failed to open file. path:'/sys/devices/virtual/dmi/id/sys_vendor' mode:'rb' errno:2 aws-error:44(AWS_ERROR_FILE_INVALID_PATH)
[ERROR] 2025-05-05 08:39:32.159 common-io [547798657344] static: Failed to open file. path:'/sys/devices/virtual/dmi/id/product_name' mode:'rb' errno:2 aws-error:44(AWS_ERROR_FILE_INVALID_PATH)

uname -a
Linux raspberrypi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux
ls /sys/devices/virtual/
bcm2835-gpiomem bdi block devlink dma_heap graphics input leds mem misc net sound thermal tty vc vc-mem vtconsole workqueue
cat /etc/debian_version
11.11
`

[sbiscigl]

common-io

my guess is this has something to do with our friends aws-c-io then.

After upgrading our aws-cpp-sdk version to the tip of the main branch

can you elaborate between which versions you updated, that way i can have a better idea of the diff that may cause this to happen. also if you could include a longer log file, it might reveal more about where this is happening.

[PaavoHelde]

Thanks for response! Here is some info about versions, let me know if more is needed:

No messages reported to log during InitAPI:

pi: aws-sdk-cpp> git status
Refresh index: 100% (100564/100564), done.
HEAD detached at 1.10.57
nothing to commit, working tree clean
pi: aws-sdk-cpp> cd ./crt/aws-crt-cpp/crt/aws-c-io
pi: aws-c-io> git status
HEAD detached at 6c19e25
nothing to commit, working tree clean

Error messages in log:

pi: aws-sdk-cpp> git status
On branch main
Your branch is up to date with 'origin/main'.

nothing to commit, working tree clean
pi: aws-sdk-cpp>git log -1
commit 66499f18ed373692da4f20b6e7f8f776a8ba7c4c (HEAD -> main, tag: 1.11.558, origin/main, origin/HEAD)
Author: aws-sdk-cpp-automation <[email protected]>
Date:   Wed Apr 30 18:28:59 2025 +0000
...
pi: aws-sdk-cpp>cd ./crt/aws-crt-cpp/crt/aws-c-io
pi: aws-c-io>git status
HEAD detached at 46974e9
nothing to commit, working tree clean

[PaavoHelde]

Some more log messages from aws-cpp-sdk:

2025-05-05 18:29:07.967 6 {7} [aws/native] INFO: [INFO] 2025-05-05 15:29:07.967 Aws_Init_Cleanup [547764267328] Initiate AWS SDK for C++ with Version:1.11.558 |PID=3467659|TID=3467659|
2025-05-05 18:29:07.969 6 {7} [aws/native] INFO: [INFO] 2025-05-05 15:29:07.969 aws-c-common [547764267328] static: libnuma.so loaded |PID=3467659|TID=3467659|
2025-05-05 18:29:07.970 6 {7} [aws/native] INFO: [INFO] 2025-05-05 15:29:07.970 aws-c-common [547764267328] static: set_mempolicy() loaded |PID=3467659|TID=3467659|
2025-05-05 18:29:07.970 6 {7} [aws/native] INFO: [INFO] 2025-05-05 15:29:07.970 aws-c-common [547764267328] static: numa_available() loaded |PID=3467659|TID=3467659|
2025-05-05 18:29:07.970 6 {7} [aws/native] INFO: [INFO] 2025-05-05 15:29:07.970 aws-c-common [547764267328] static: numa_available() returns -1, numa functions are not available. Skip loading the other numa functions. |PID=3467659|TID=3467659|
2025-05-05 18:29:07.971 7 {7} [aws/native] DEBUG: [DEBUG] 2025-05-05 15:29:07.971 libcrypto_resolve [547764267328] searching process and loaded modules |PID=3467659|TID=3467659|
2025-05-05 18:29:07.971 7 {7} [aws/native] DEBUG: [DEBUG] 2025-05-05 15:29:07.971 libcrypto_resolve [547764267328] did not find aws-lc symbols linked |PID=3467659|TID=3467659|
2025-05-05 18:29:07.972 7 {7} [aws/native] DEBUG: [DEBUG] 2025-05-05 15:29:07.972 libcrypto_resolve [547764267328] did not find boringssl symbols linked |PID=3467659|TID=3467659|
2025-05-05 18:29:07.972 7 {7} [aws/native] DEBUG: [DEBUG] 2025-05-05 15:29:07.972 libcrypto_resolve [547764267328] found static libcrypto 1.1.1 HMAC symbols |PID=3467659|TID=3467659|
2025-05-05 18:29:07.972 7 {7} [aws/native] DEBUG: [DEBUG] 2025-05-05 15:29:07.972 libcrypto_resolve [547764267328] found static libcrypto 1.1.1 EVP_MD symbols |PID=3467659|TID=3467659|
2025-05-05 18:29:07.973 7 {7} [aws/native] DEBUG: [DEBUG] 2025-05-05 15:29:07.973 libcrypto_resolve [547764267328] Compiled with libcrypto OpenSSL 3.0.15-dev , linked to libcrypto OpenSSL 3.0.15-dev |PID=3467659|TID=3467659|
2025-05-05 18:29:07.974 6 {7} [aws/native] INFO: [INFO] 2025-05-05 15:29:07.974 tls-handler [547764267328] static: Initializing TLS using s2n. |PID=3467659|TID=3467659|
2025-05-05 18:29:07.981 7 {7} [aws/native] DEBUG: [DEBUG] 2025-05-05 15:29:07.981 tls-handler [547764267328] ctx: Based on OS, we detected the default PKI path as /etc/ssl/certs, and ca file as /etc/ssl/certs/ca-certificates.crt |PID=3467659|TID=3467659|
[ERROR] 2025-05-05 15:29:07.982 common-io [547764267328] static: Failed to open file. path:'/sys/devices/virtual/dmi/id/sys_vendor' mode:'rb' errno:2 aws-error:44(AWS_ERROR_FILE_INVALID_PATH) 
[ERROR] 2025-05-05 15:29:07.983 common-io [547764267328] static: Failed to open file. path:'/sys/devices/virtual/dmi/id/product_name' mode:'rb' errno:2 aws-error:44(AWS_ERROR_FILE_INVALID_PATH) 
2025-05-05 18:29:07.984 9 {7} [aws/native] DEBUG: [TRACE] 2025-05-05 15:29:07.984 aws-c-common [547764267328] id=0x7f86e3e500: virtualization vendor detected as "" |PID=3467659|TID=3467659|
2025-05-05 18:29:07.985 9 {7} [aws/native] DEBUG: [TRACE] 2025-05-05 15:29:07.985 aws-c-common [547764267328] id=0x7f86e3e500: virtualization product name detected as " " |PID=3467659|TID=3467659|
2025-05-05 18:29:07.985 9 {7} [aws/native] DEBUG: [TRACE] 2025-05-05 15:29:07.985 S3General [547764267328] id=0x7f86e2a520: adding platform entry for "c5n.18xlarge". |PID=3467659|TID=3467659|
2025-05-05 18:29:07.986 9 {7} [aws/native] DEBUG: [TRACE] 2025-05-05 15:29:07.986 S3General [547764267328] id=0x7f86e2a520: adding platform entry for "c5n.9xlarge". |PID=3467659|TID=3467659|
2025-05-05 18:29:07.987 9 {7} [aws/native] DEBUG: [TRACE] 2025-05-05 15:29:07.987 S3General [547764267328] id=0x7f86e2a520: adding platform entry for "c5n.metal". |PID=3467659|TID=3467659|
2025-05-05 18:29:07.988 9 {7} [aws/native] DEBUG: [TRACE] 2025-05-05 15:29:07.988 S3General [547764267328] id=0x7f86e2a520: adding platform entry for "p4d.24xlarge". |PID=3467659|TID=3467659|
2025-05-05 18:29:07.989 9 {7} [aws/native] DEBUG: [TRACE] 2025-05-05 15:29:07.989 S3General [547764267328] id=0x7f86e2a520: adding platform entry for "p4de.24xlarge". |PID=3467659|TID=3467659|
2025-05-05 18:29:07.990 9 {7} [aws/native] DEBUG: [TRACE] 2025-05-05 15:29:07.990 S3General [547764267328] id=0x7f86e2a520: adding platform entry for "p5.48xlarge". |PID=3467659|TID=3467659|
2025-05-05 18:29:07.991 9 {7} [aws/native] DEBUG: [TRACE] 2025-05-05 15:29:07.991 S3General [547764267328] id=0x7f86e2a520: adding platform entry for "trn1n.32xlarge". |PID=3467659|TID=3467659|
2025-05-05 18:29:07.992 9 {7} [aws/native] DEBUG: [TRACE] 2025-05-05 15:29:07.991 S3General [547764267328] id=0x7f86e2a520: adding platform entry for "trn1.32xlarge". |PID=3467659|TID=3467659|

[PaavoHelde]

Meanwhile I digged a bit more, it appears the non-existing paths are directly hard-coded in the file crt/aws-crt-cpp/crt/aws-c-common/source/linux/system_info.c :

    aws_byte_buf_init_from_file_with_size_hint(
        &env->virtualization_vendor, env->allocator, "/sys/devices/virtual/dmi/id/sys_vendor", 32 /*size_hint*/);