Il 10/07/2013 19:52, Luiz Capitulino ha scritto: > From: Seiji Aguchi <[email protected]> > > [Issue] > When we offer a customer support service and a problem happens > in a customer's system, we try to understand the problem by > comparing what the customer reports with message logs of the > customer's system. > > In this case, we often need to know when the problem happens. > > But, currently, there is no timestamp in qemu's error messages. > Therefore, we may not be able to understand the problem based on > error messages. > > [Solution] > Add a timestamp to qemu's error message logged by > error_report() with g_time_val_to_iso8601(). > > Signed-off-by: Seiji Aguchi <[email protected]> > Reviewed-by: Stefan Hajnoczi <[email protected]> > Signed-off-by: Luiz Capitulino <[email protected]>
What about removing the option, and instead: - logging no timestamp until the virtual machine has started - always logging timestamps after the virtual machine has started ? Paolo
