virtualbox.org

Hello,

I have installed VM VirtualBox 4.3.26 on Windows XP host.
Then I installed the extension pack related to that version.
After the installation I tried to start my guest virtual machine (OS: Windows XP SP 3) but I got the following error:

----------------------------------------------------------------------------------------------------------

Apertura di una sessione per la Macchina Virtuale Windows_XP non riuscita. (= Opening a session to the Virtual Machine Windows_XP failed.)

Implementation of the USB 2.0 controller not found!

Because the USB 2.0 controller state is part of the saved VM state, the VM cannot be started. To fix this problem, either install the 'Oracle VM VirtualBox Extension Pack' or disable USB 2.0 support in the VM settings (VERR_NOT_FOUND).

Exit Code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}

----------------------------------------------------------------------------------------------------------

I didn't change anything, I just upgraded the VM tool....

Appreciate any help to resolve this issue.

Regards,
K.

Install the Extension Pack. Yes, I saw where you said you already did that, but you are mistaken, or you shouldn't get that error.

The Extension Pack and the Guest Additions are quite different beasts serving quite different functions (the latter augments an individual guest OS, the former extends VirtualBox itself for all VMs).

If you believe I'm wrong then post a VM log file for the VM in question: right click the VM in the GUI. Select "Show Log". Save "VBox.log" to a file. Compress that file and attach it to a message here. Make sure the VM is fully shut down before taking a log.


Also, please note that the upgrading the VirtualBox software while a VM is in a suspended state... can be problematic. If all all fails then I'd suggest <right click on VM> : "Discard saved state" (or equivalent in Italian).

Hello mpack,

thank you very much for your hints.

Well, as you have read, I already installed the Extension Pack. The Guest Addiction are not yet installed because my VM doesn't start .

The Virtual Box has been upgraded while everything was in shutdown state.

Here you can find the log file of my VM: The "Discard saved state" is not available in my menu, so I will not be able to do that action if everything will fails .

K.

VBox.log wrote: 00:00:02.226989 Installed Extension Packs:
00:00:02.227009 Oracle VM VirtualBox Extension Pack (Version: 4.3.26 r98988; VRDE Module: VBoxVRDP unusable because of 'Failed to resolve exported symbol 'VBoxExtPackRegister' in the main module: VERR_SYMBOL_NOT_FOUND')

I don't recognize this problem, however you might want to download the extension pack again, and check the MD5 checksum on it.

Ok, let's start.

I downloaded the extension pack again, as you told me.
I checked the MD5 checksum of the file and it mached.
I first uninstalled the extension pack I have on my Virtual box application, and then I installed the downloaded checked extension pack file.

The problem is still the one you saw in the VBox.log I upgraded last time....

Any other suggestions?

K.

Ok, if it's not the extension pack then it must be the main VBox application. Is there anything unusual about it? E.g. it is not self compiled or anything?

Well, regarding the main VBox application I downloaded the version 4.3.26 r98988 (.exe file) from the main site, as suggested in the update information box that appears when a new version is available.
It is not a self compiled version.

K.

Well, I think you have no option but to raise a ticket on BugTracker (note that this is a separate login, though still OSSO).

Then you can revert to 4.3.12 as a temporary workaround. Remember to downgrade extension pack (on host) and GAs (in each guest) as well.

To OP: Was there some previous VirtualBox version which worked? Presumably yes... so which version was it?

Also, did you check if the Extension Pack was correctly downloaded (no file corruption)?

Frank Mehnert wrote:Also, did you check if the Extension Pack was correctly downloaded (no file corruption)?

I got him to do an MD5 checksum test - it's mentioned above in the messages after I saw the log file.

michaln wrote:To OP: Was there some previous VirtualBox version which worked? Presumably yes... so which version was it?

Yes, there was. The previous version which worked was the 4.3.24 .

mpack wrote:Well, I think you have no option but to raise a ticket on BugTracker (note that this is a separate login, though still OSSO).

Then you can revert to 4.3.12 as a temporary workaround. Remember to downgrade extension pack (on host) and GAs (in each guest) as well.

Ok, I'll downgrade the VM, and the extension pack. I'll let you know.

Thanks for all the help you gave me.


K.

Hello.

I have done the downgrade of the VM, extension pack, and guest addiction on my PC (after backuping all VM files).

Before downgrading to 4.3.12 version, I have done an intermediate downgrade from 4.3.26 to 4.3.22 version, but it didn't work.

So I downgraded to the 4.3.12 and now it works again.

I have just opened a ticket on the BugTracker (#14001), hoping that they can solve the problem.

K.