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
Currently, vmm_task's log is redirected into the host by vmm-sandboxer process.
However, vmm-sandboxer process just use the debug!() macro to print the vmm_task's logs into the stdout, which will add the redundant log header like this:
[2023-06-27T07:24:46.160098Z DEBUG vmm_sandboxer::utils] console: [2023-06-27T07:24:45.531189Z DEBUG vmm_task::task] receive exit event: PID 87 exit with code 0
[2023-06-27T07:24:46.160198Z DEBUG vmm_sandboxer::utils] console: [2023-06-27T07:24:45.531308Z DEBUG vmm_task::io] copy_io: pipe stdout from to hvsock://vsock:2000
[2023-06-27T07:24:46.161295Z DEBUG vmm_sandboxer::utils] console: [2023-06-27T07:24:45.532399Z INFO containerd_shim::asynchronous::task] Create request for b3fdff9ae24160e1fd21a36c6e87af6a47c4cd49a300100867aeae86390c1c63 returns pid 96
What we want to achieve like this:
[2023-06-27T07:24:45.531189Z DEBUG vmm_task::task] receive exit event: PID 87 exit with code 0
[2023-06-27T07:24:45.531308Z DEBUG vmm_task::io] copy_io: pipe stdout from to hvsock://vsock:2000
[2023-06-27T07:24:45.532399Z INFO containerd_shim::asynchronous::task] Create request for b3fdff9ae24160e1fd21a36c6e87af6a47c4cd49a300100867aeae86390c1c63 returns pid 96
Why is this needed?
Remove the redundant log header for vmm_task components log, make a more cleaner log output!
The text was updated successfully, but these errors were encountered:
What should be cleaned up or changed?
Currently, vmm_task's log is redirected into the host by vmm-sandboxer process.
However, vmm-sandboxer process just use the
debug!()
macro to print the vmm_task's logs into the stdout, which will add the redundant log header like this:What we want to achieve like this:
Why is this needed?
Remove the redundant log header for vmm_task components log, make a more cleaner log output!
The text was updated successfully, but these errors were encountered: