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
{{ message }}
This repository has been archived by the owner on Oct 24, 2022. It is now read-only.
I guess this might be a wider policy question but when implementing a new daemon should we have a way to enable logging in the backend crate. At the moment I'm stuck trying to diagnose where in the vhost-user sequence something is missing by using gdb. Perhaps we should use log! macros so debug builds can be more verbose if required?
The text was updated successfully, but these errors were encountered:
This is a question that affects all rust-vmm crates and has already popped up a couple times. We could perhaps bring this to the next rust-vmm meeting to see if we can reach an project-wide agreement about it.
Good idea! Let's chat about it at the next rust-vmm sync. In the vmm-reference we're going to try logging with the log crate as we've been also using it in Firecracker and is turns out to be very flexible. Other log crates are built on top so it.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I guess this might be a wider policy question but when implementing a new daemon should we have a way to enable logging in the backend crate. At the moment I'm stuck trying to diagnose where in the vhost-user sequence something is missing by using gdb. Perhaps we should use log! macros so debug builds can be more verbose if required?
The text was updated successfully, but these errors were encountered: