VirtualBox

Ticket #11102 (closed defect: wontfix)

Opened 8 years ago

Last modified 8 years ago

Unexpected errors in VBoxSVC.log

Reported by: Armando Owned by:
Component: other Version: VirtualBox 4.2.0
Keywords: Cc:
Guest type: all Host type: Windows

Description

Host = WinXP x 64, VBox 4.2.0

I noticed in Document&Settings\...\.Virtualbox the presence of ten VBoxSVC.log.x files. I opened the main VBoxSVC.log and found many error messages.

That surprised me, as all my VMs ("old" pre-VBox4 included) seem to be running well. I did some testing. I deleted the log file, launched VBox Manager and checked the new log, finding no error messages. I then started an "old" VM (in saved state) and the following line appeared in the log:

00:00:42.688000   ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={22781af3-1c96-4126-9edf-67a020e0e858} aComponent={Machine} aText={Machine is not locked for session (session state: Unlocked)}, preserve=false

I closed the VM (saving its state) and no new lines appeared. I started another VM (a 4.x one, also in saved state) and the log showed a new line which was exactly the same as the previous one. The same happened with any other VM.

When I closed VBox Manager, the log showed many new lines, each referring to a different vdi file and looking like:

00:09:35.047000 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={29989373-b111-4654-8493-2e1176cba890} aComponent={Medium} aText={Medium 'C:\VirtualBox_VMs\VMname\VMname.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false

These lines only refer to 4.x VMs: one line for every vdi file, snapshots included. I also noticed that the aIID={29989...} code is the same in all these lines, similarly to what happens for the other error lines, where the aIID={2781a...} code is always the same. I found similar error messages also in another PC (VBox4.1.20+Win2008Server). In both computers VBox and VMs seem to run with no problems.

Is this a bug or a normal (?) behaviour?

Change History

comment:1 Changed 8 years ago by frank

  • Status changed from new to closed
  • Resolution set to wontfix

This is not really a bug. You don't need to care these messages as long as your VMs work as expected.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use