Page 1 of 1
How can I better understand VirtualBox log files?
Posted: 10. Feb 2016, 16:07
by free4ever
Hi,
A virtual machine crashed and I tried to look into its log file VBox.log. I went to the section titled: "Guest state at power off" but I could not understand the dump.
Can you please advise on how I can understand a virtual machine dumps?
Best regards,
Re: How can I better understand VirtualBox log files?
Posted: 10. Feb 2016, 18:00
by mpack
You can look at the source code and/or look at many VM log files and get a feel for what is normal and what isn't.
Another thing you can do is zip it and attach the zip to a message here, so that others can review it for you, after you give a better description of the problem.
And bear in mind that the log file is mostly only useful for diagnosing VirtualBox issues, not issues with the guest OS.
Re: How can I better understand VirtualBox log files?
Posted: 10. Feb 2016, 22:37
by free4ever
Thank you mpack for your reply.
I left my virtual machine running last night, but it was off this morning. I'm trying to find out what was the cause of the shutdown.
I attached the log file.
Re: How can I better understand VirtualBox log files?
Posted: 11. Feb 2016, 11:15
by mpack
Right on the first line I see you are using VirtualBox v5.0.0, which is by definition the buggiest member of the v5 family. If I was you I would install the latest maintenance release and then we can look at this again. See the Downloads area.
Next, I see that you don't have the extension pack installed. Let's hope you aren't using any USB devices, because they'd be working at USB1 speeds.
Next, I see that you assigned 3 cores (out of 4 available) to the VM. I would have assigned no more than 2. Let's hope the host doesn't need to do anything substantial.
I also see this in the log :-
VBox.log wrote:
34:44:52.150846 AsyncCompletion: Task 0x0000000f77c1c0 completed after 14 seconds
34:44:52.679132 AsyncCompletion: Task 0x0000000f9c5dc0 completed after 14 seconds
34:45:08.003483 OHCI#0: Lagging too far behind, not trying to catch up anymore. Expect glitches with USB devices
34:45:40.933207 OHCI#0: Lagging too far behind, not trying to catch up anymore. Expect glitches with USB devices
34:58:45.029889 AsyncCompletion: Task 0x0000018f649f80 completed after 11 seconds
34:58:47.350895 AsyncCompletion: Task 0x0000018f573dc0 completed after 11 seconds
34:58:47.365881 AsyncCompletion: Task 0x0000000f9c58c0 completed after 13 seconds
34:58:47.367463 AsyncCompletion: Task 0x0000018f581e00 completed after 13 seconds
Do you have some heavy backup process that kicks in after X hours? If so then perhaps what I said about cores comes into play here.
Let's see what happens if you take care of the first three items.