Repository navigation
Address guest tracing improvements #964
Description
Activity
Trace/logs loss is an acceptable compromise
I think this is only true if the host can make the decision that they are willing to suffer log/trace loss.
Having the configuration option on the guest side, the guest can say how much space it is acceptable to use for traces/logs buffering.
Making VMExits to report traces has a performance penalty.Having the configuration option on the guest side, the guest can say how much space it is acceptable to use for traces/logs buffering. Making VMExits to report traces has a performance penalty.
Understood, I am saying that we should not make the decision on if to trade off data loss for perf for a host, they should make that decision themselves.
The current version using
opentelemetryis an incremental step, after which additionaltunablescan be added to improve usability.Improvements to be considered:
flatbuffersto serialize the data exchanged between the guest and host