Nanos JVM Quarkus log getsockopt unimplemented: fd 13, level 6, optname 4

[AngeloRubens]

Hi @francescolavra, after fix the create image for aws(nanovms/ops#1735)
i try execute quarkus java application on nanos with aws t4.small vm, when start the application the log print this error:

[37.638012] getsockopt unimplemented: fd 13, level 6, optname 4
[37.638881] getsockopt unimplemented: fd 13, level 6, optname 6
[37.639687] getsockopt unimplemented: fd 13, level 6, optname 5
[37.640618] getsockopt unimplemented: fd 13, level 1, optname 56

the same error is reproduce in local pc with:
download the quarkus jar from this url:https://github.com/AngeloRubens/quarkus-faces-nanos/actions/runs/21218011985

and execute with

ops pkg load AngeloRubens/SemeruJREarm64Linux:25.0.1 --arch arm64 --nightly -c configAws.json --verbose

......
[355.288636] getsockopt unimplemented: fd 13, level 6, optname 4
[355.289127] getsockopt unimplemented: fd 13, level 6, optname 6
[355.289511] getsockopt unimplemented: fd 13, level 6, optname 5
[355.291544] getsockopt unimplemented: fd 13, level 1, optname 56
......

[AngeloRubens]

the same log is for the same application in oracle oci env.

[francescolavra]

Thanks for reporting this.

Socket option level 6 is SOL_TCP, and options 4, 5, 6 are TCP_KEEPIDLE, TCP_KEEPINTVL, TCP_KEEPCNT. Nanos does implement the TCP keep-alive feature, so adding support for retrieving these parameters should be easily doable.

Socket option level 1 is SOL_SOCKET, and option 56 is SO_INCOMING_NAPI_ID; this is supposed to return a unique ID of the receive queue on which the last packet associated with a given socket is received. Nanos implements multiple receive queues in its virtio-net driver (which is used by a few cloud providers, among which GCP, and also for on-prem deployments with Qemu or VirtualBox); currently there is no infrastructure in the kernel for the network card driver to pass a receive queue ID up the network stack to the socket level, but we could add that infrastructure by using the LWIP_PBUF_CUSTOM_DATA option to attach this type of metadata to each received network packet.

[AngeloRubens]

Hi @francescolavra thanks for reply, perfect, we can't wait to see this improvement...