Qemu: Unsupported syscall: 345


#1

I have an asp.net core app that I have cross compiled to run on a raspberry pi.

When runs fine on the pi but if I run the container on my machine (under qemu thanks to the magic of the resin base image) I get lots of qemu: Unsupported syscall: 345 lines logged.
Functionally the app seems to not be affected but as it’s outputting these lines about every second reading the output for real messages.

I’m not really sure how I would go about working out what is causing this, or where, or if I should report it as a bug.


#3

Hi there. Have not used this myself but I believe @petrosagg can shed some light here


#4

@gambrose I checked what this syscall is about and it’s getcpu(2) . QEMU warns cause it doesn’t know how to translate it but it looks like one of those syscalls that are informational and maybe trigger some optimisation. I opened an issue in our QEMU repo but it looks safe to ignore


#5

Thanks for your help @petrosagg.