VirtualBox

Ticket #1901 (closed defect: fixed)

Opened 4 months ago

Last modified 1 month ago

Huge log files fill up the host file system (PATM: ...) => Fixed in 2.0.4

Reported by: Fenix*NBK* Assigned to:
Priority: blocker Component: other
Version: VirtualBox 1.6.4 Keywords:
Cc: Guest type: other
Host type: other

Description

WARNING: DANGER !!!

VirtualBox 1.6.4 will crash your Windows computer, and render it unbootable !!!

I have been using VirtualBox 1.6.4 for several hours and the log file went up to 6GB (!!!) in size, tooking over my Windows partition, and leaving zero space. Of course, Windows refused to boot after reboot, and crashed with BSOD.

Sun: I really recommend building v1.6.4a as soon as possible.

-Technologov, 2.8.2008.

Change History

08/02/08 19:37:02 changed by Fenix*NBK*

Also, setting some maximum number of bytes for log file is a good idea.

It may be configurable in some internal *.ini file, if you want.

-Technologov, 2.8.2008.

08/04/08 23:10:13 changed by frank

  • summary changed from DANGER !!! VirtualBox 1.6.4 makes your Windows system unbootable ! to DANGER !!! VirtualBox 1.6.4 makes your Windows system unbootable (huge log files)!.

Confirmed.

08/14/08 13:18:31 changed by sandervl73

  • host changed from Windows to other.
  • summary changed from DANGER !!! VirtualBox 1.6.4 makes your Windows system unbootable (huge log files)! to Huge log files fill up the host file system.

08/14/08 13:18:58 changed by sandervl73

Applies to Linux as well. (hence the change in title) Marked 1956 as a duplicate.

09/02/08 14:43:29 changed by frank

  • status changed from new to closed.
  • resolution set to fixed.

10/19/08 18:34:51 changed by GoofyX

  • status changed from closed to reopened.
  • resolution deleted.

I am using the non-free version of VirtualBox 2.0.2 both for Windows and Linux (x86_64) and I sometimes get huge log files. For example, I've set up an Arch Linux guest vmachine and I get 500MiB of log file. This applies both for Windows and Linux.

Is it safe to delete these log files?

(follow-up: ↓ 8 ) 10/19/08 22:02:23 changed by frank

Sure. Do these log files contain of some repeating content? Could you attach a small part of such an log file to this defect?

(in reply to: ↑ 7 ) 10/19/08 22:32:57 changed by GoofyX

Replying to frank:

Sure. Do these log files contain of some repeating content? Could you attach a small part of such an log file to this defect?

Peaking through the file, there are thousands of lines with the following content:

04:27:44.676 PATM: Disabling IDT e patch handler c0319180 04:27:44.676 PATM: Disabling IDT e patch handler c0319180 04:27:44.676 PATM: Disabling IDT e patch handler c0319180 04:27:44.677 PATM: Disabling IDT e patch handler c0319180

and so on... Only the numbers (I guess it's a timestamp...?) change. These lines fill up the log.

10/19/08 22:36:43 changed by GoofyX

Also, is it a coincidence that in both cases (both Windows and Gentoo Linux as a host) the guest machine is Arch Linux when the log file grows up so big?

10/20/08 09:31:47 changed by frank

  • summary changed from Huge log files fill up the host file system to Huge log files fill up the host file system (PATM: ...) => Fixed in 2.0.4.

Yes, the problem with huge log files is guest-related. This problem will be fixed in 2.0.4.

10/24/08 10:18:30 changed by frank

  • status changed from reopened to closed.
  • resolution set to fixed.

© 2008 Sun Microsystems, Inc.
Contact – Privacy policy