-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
runtime: fix missing of VhostUserDeviceReconnect parameter assignment #9849
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm, thanks!
/test |
/test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thx @markyangcc for your contribution.
Could you please add this message to git's commit ?You can follow the example
IMO, this maybe only involve small changes but as a result of go format causing the whole HypervisorConfig
change(L909 ->L979)
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>
Yes, real change is add below line, most of changes caused by go format,
Also, commit message updated. |
Below commit implements the vhost-user-blk reconnection functionality,
runtime: add reconnect timeout for vhost user block
However, this commit has missed assigning
VhostUserDeviceReconnect
when new the QEMU HypervisorConfig, resulting inVhostUserDeviceReconnect
always set to default value 0.Fixes: #9848