virtualbox.org

While doing some system maintenance, I noticed in Document&Settings\...\.Virtualbox the presence of ten VBoxSVC.log.x files.
I opened the main one (VBoxSVC.log) and found many error messages.

That surprised me, as all my VMs (the "old" pre-VBox4 ones together with the newest VBox4.2 ones) seem to be running well.
So I went for some testing. I launched VBox Manager and then I checked the log file, finding no error messages.
I then started an "old" VM (in saved state) and the following line appeared in the log:
I closed the VM (saving its state) and no new lines appeared.
I started another VM (this time a "new" 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:
I noticed that these lines only refer to "new" rel4+ VMs; there is 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 finally looked in another PC with different software (VBox4.1.20+Win2008Server, while I'm using VBox4.2.0+XPx64) and I found similar error messages there too. In both computers VBox and VMs seem to run with no problems.

So my questions are:

• - Where do these errors come from? What is causing them?

• - Should I worry about them?

• - How can I get rid of them, anyway?

Thanks for any help.

I've recently noticed the same thing. However I've never made a habit of checking the VBoxSVC log so I can't say when it started happening. My guess is that it started with v4.2.0, given that nobody else reported it either, before then.

I also initially thought it could be a 4.2.0... side feature but, as I said, I found quite similar messages in another PC running release 4.1.20, so that assumption proved wrong.

I also did not usually check that log. As long as VMs are running well there is actually no motive for checking log files, unless you get there by chance or for some special reason.
Maybe nobody else reported it before because nobody noticed it; maybe someone noticed but did not bother to report or maybe thought it was a normal behaviour, since everything appeared to be running fine.

Anyway, maybe I'm misreading words, but from my point of view an ERROR event can hardly be regular; if it was "normal" then it would not be an "error", would it? That's why I'd like to understand and to get some answers to my questions.

Let's hope someone will provide some technical explanation.