From faf5aed965c264474d73a3845e4b46cf97c45cc8 Mon Sep 17 00:00:00 2001 From: Hyounggyu Choi Date: Wed, 28 May 2025 12:45:22 +0200 Subject: [PATCH] runtime-rs: Adjust VSOCK timeouts for IBM SEL The default `reconnect_timeout` (3 seconds) was found to be insufficient for IBM SEL when using VSOCK. This commit updates the timeouts as follows: - `dial_timeout_ms`: Set to 90ms to match the value used in go-runtime for IBM SEL - `reconnect_timeout_ms`: Increased to 5000ms based on empirical testing Signed-off-by: Hyounggyu Choi --- .../config/configuration-qemu-se-runtime-rs.toml.in | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/runtime-rs/config/configuration-qemu-se-runtime-rs.toml.in b/src/runtime-rs/config/configuration-qemu-se-runtime-rs.toml.in index 46d1d68647..242897cf2b 100644 --- a/src/runtime-rs/config/configuration-qemu-se-runtime-rs.toml.in +++ b/src/runtime-rs/config/configuration-qemu-se-runtime-rs.toml.in @@ -541,7 +541,7 @@ kernel_modules=[] # Agent dial timeout in millisecond. # (default: 10) -dial_timeout_ms = 30 +dial_timeout_ms = 90 # Agent reconnect timeout in millisecond. # Retry times = reconnect_timeout_ms / dial_timeout_ms (default: 300) @@ -550,7 +550,7 @@ dial_timeout_ms = 30 # You'd better not change the value of dial_timeout_ms, unless you have an # idea of what you are doing. # (default: 3000) -#reconnect_timeout_ms = 3000 +reconnect_timeout_ms = 5000 # Create Container Request Timeout # This timeout value is used to set the maximum duration for the agent to process a CreateContainerRequest.