Opened 14 years ago
Last modified 4 years ago
#7187 reopened defect
VirtualBox huge log file harvesting disk
| Reported by: | José Jorge | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 3.2.6 |
| Keywords: | big log files | Cc: | |
| Guest type: | Windows | Host type: | Linux |
Description
Using VirtualBox 3.2.6 r633112, Ubuntu 10.04 as host and Windows XP Professional as guest, I had problems starting a program (Mach3) inside Windows, I didn't open after three attempts but continued working with Firefox and other programs, after some time, I received an Ubuntu system message indicating my hard disk had very few available space, this surprised me since I was supposed to be using just 20 GB (for both Ubuntu and virtual WinXP) from my 160 GB disk. I forced VBox down and searched for the problem, I found four VBox log files in the Logs directory for my VM, two had sizes of 30 GB and 90 GB!
I'm not sure whether such a huge log file should be useful for debugging, but guess VBox could emit an alert when these logs grow too much so that the user can pay attention and take some actions before the host system becomes unresponsive.
Attachments (1)
Change History (4)
comment:1 by , 14 years ago
comment:3 by , 4 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
I got the same issue today on VirtualBox 6.1.4 r136177 (QT5.6.2) on Windows 10 host, the log file grown to over 40GB when I found the issue, I trim the first 200KB of log and attached here.
As the file shown, there are repeatly error message like
00:00:39.950369 Unhandled error 1617 00:00:39.950407 AssertLogRel F:\tinderbox\win-rel\src\VBox\Runtime\win\RTErrConvertFromWin32.cpp(448) int __cdecl RTErrConvertFromWin32(unsigned int): <NULL>
How to reproduce?
- On the Windows 10 host, in Settings => Devices => Bluetooth => More Bluetooth Options, add an incoming Bluetooth serial port, e.g. "COM5"
- Add a serial port to the guest, map it to host device, follow the last step, "COM5"
- Remove the virtual serial port "COM5" in "More Bluetooth Options"
- Turn off the guest, then there will be a huge log file.
Other issue caused by this bug?
After (step 3) virtual serial port has been removed , VirtualBox session will consume 100% of a CPU core.
Of course this is a bug but I've not seen a similar report from someone else. Please have a look at the log file. I suspect that it contains some repeating lines.