You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The vhost_user_reconnect_timeout_sec parameter in the configuration.toml file is intended to set the reconnect timeout for vhost-user devices. However, the actual log output consistently shows ReconnectTime as zero, which does not reflect the value specified in the configuration.
Actual Result
The log indicates that ReconnectTime is always zero, regardless of the configuration value set for vhost_user_reconnect_timeout_sec:
Commit 'ca02c9f5124e' implements the vhost-user-blk reconnection functionality,
However, it has missed assigning VhostUserDeviceReconnect when new the QEMU
HypervisorConfig, resulting in VhostUserDeviceReconnect always set to default value 0.
Real change is this line, most of changes caused by go format,
return vc.HypervisorConfig{
// ...
VhostUserDeviceReconnect: h.VhostUserDeviceReconnect,
}, nil
Fixes: kata-containers#9848
Signed-off-by: markyangcc <mmdou3@163.com>
Issue Description
The
vhost_user_reconnect_timeout_sec
parameter in theconfiguration.toml
file is intended to set the reconnect timeout for vhost-user devices. However, the actual log output consistently showsReconnectTime
as zero, which does not reflect the value specified in the configuration.Actual Result
The log indicates that
ReconnectTime
is always zero, regardless of the configuration value set forvhost_user_reconnect_timeout_sec
:Expected Result
The log should show like below,
ReconnectTime
should be set to 1 (vhost_user_reconnect_timeout_sec = 1
)Would be fixed by #9849
The text was updated successfully, but these errors were encountered: