VM log, time stamps problem
Posted: 11. Dec 2015, 17:49
VBox.log
The time stamps of generated log lines change after host desktop lock-unlock. Host is Windows 7 64Bits.
Used Virt. Box ver. 4.3.26.
All VBox.log files were deleted before starting any virt. mach., this just to have a clean situation reg log files.
Then two virt. machines were started at two near points of time.
Short after both virt. machines were up and operating, the log windows were checked.
At that time of point, the logs time stamps read from 0 to nearly 1 seconds after log start.
Exact the same log state both logs showed nearly 3 hours later, shortly before leaving for the break, users makes break in his work.
For the duration of user's absence the host machine's desktop was locked.
Back from the break users unlocks the host and checks the logs again.
Now the log time stamps read 1 second after log start-up to 3 hours 16 minutes.
The duration of host desktop lock was approx 20 minutes.
Problem : time-stamps in logs do not show the range 0 seconds to nearly 1 seconds after host desktop lock-unlock cycle.
However the top second log line - log payload "Log opened...." still shows the original time stamp in log point payload.
Thus the conclusion is, the log lines got not lost, they just changed for some unclear reason their time stamps.
A known issue?
The time stamps of generated log lines change after host desktop lock-unlock. Host is Windows 7 64Bits.
Used Virt. Box ver. 4.3.26.
All VBox.log files were deleted before starting any virt. mach., this just to have a clean situation reg log files.
Then two virt. machines were started at two near points of time.
Short after both virt. machines were up and operating, the log windows were checked.
At that time of point, the logs time stamps read from 0 to nearly 1 seconds after log start.
Exact the same log state both logs showed nearly 3 hours later, shortly before leaving for the break, users makes break in his work.
For the duration of user's absence the host machine's desktop was locked.
Back from the break users unlocks the host and checks the logs again.
Now the log time stamps read 1 second after log start-up to 3 hours 16 minutes.
The duration of host desktop lock was approx 20 minutes.
Problem : time-stamps in logs do not show the range 0 seconds to nearly 1 seconds after host desktop lock-unlock cycle.
However the top second log line - log payload "Log opened...." still shows the original time stamp in log point payload.
Thus the conclusion is, the log lines got not lost, they just changed for some unclear reason their time stamps.
A known issue?