On 05/20/2015 08:43 AM, Eric Blake wrote:
>
> I'd rather stick with UTC in logs (but perhaps make it more obvious that
> the timestamp is UTC by actually sticking that string as part of the
> timestamp - libvirt is not currently doing that).
Actually, here's a libvirt log timestamp:
2015-05-17 0
On 2015/5/20 22:43, Eric Blake wrote:
> On 05/20/2015 12:29 AM, Gonglei (Arei) wrote:
>> Hi,
>>
>> At present, Qemu use g_time_val_to_iso8601() to get the UTC added to
>> error_report()
>> (commit 5e2ac5191), TBH this way is very simply, we just need invoke
>> standard glib functions to
>> comple
On 05/20/2015 12:29 AM, Gonglei (Arei) wrote:
> Hi,
>
> At present, Qemu use g_time_val_to_iso8601() to get the UTC added to
> error_report()
> (commit 5e2ac5191), TBH this way is very simply, we just need invoke standard
> glib functions to
> complete the job.
local time is ambiguous (dayligh
On 2015/5/20 17:00, Daniel P. Berrange wrote:
> On Wed, May 20, 2015 at 06:29:55AM +, Gonglei (Arei) wrote:
>> Hi,
>>
>> At present, Qemu use g_time_val_to_iso8601() to get the UTC added to
>> error_report()
>> (commit 5e2ac5191), TBH this way is very simply, we just need invoke
>> standard g
On Wed, May 20, 2015 at 06:29:55AM +, Gonglei (Arei) wrote:
> Hi,
>
> At present, Qemu use g_time_val_to_iso8601() to get the UTC added to
> error_report()
> (commit 5e2ac5191), TBH this way is very simply, we just need invoke standard
> glib functions to
> complete the job.
>
> But in the
Hi,
At present, Qemu use g_time_val_to_iso8601() to get the UTC added to
error_report()
(commit 5e2ac5191), TBH this way is very simply, we just need invoke standard
glib functions to
complete the job.
But in the cloud computing and data center scenarios, there are many
Other open source compo
