VirtualBox

Opened 17 years ago

Closed 17 years ago

#5 closed defect (fixed)

Unable to launch Virtualbox

Reported by: realtebo Owned by:
Component: other Version: VirtualBox 1.3.8
Keywords: Cc:
Guest type: other Host type: other

Description

i created a new net adapter on my xp host with vboxmange createhostif "myHostcard"

now i launch virtualbox and this is the error that appears, and the app exits !

" Assertion failed: [VBOX_SUCCESS (vrc)] at 'E:\vbox\w32-rel\src\VBox\Main\VirtualBoxImpl.cpp' (1620) in VirtualBox::GetExtraData. VERR_OPEN_FAILED (-101) - File/Device open failed.. Please contact the product vendor!.

Result Code: E_FAIL (0x80004005) Component: VirtualBox Interface: IVirtualBox {e1d95593-f579-4f47-b489-0b67181014e1}"

Change History (8)

comment:1 by Achim Hasenmueller, 17 years ago

You have to administrator. We will address this in a future release.

comment:2 by Achim Hasenmueller, 17 years ago

Actually I didn't read your error message correctly. It seems to be an issue with the configuration files. They appear to be gone or inaccessible.

comment:3 by petur, 17 years ago

I just encountered the exact same error in the exact same circumstances (except I run W2K). After creating an adapter things went boom :(

comment:4 by sPENKMAN, 17 years ago

A problem like this here to, just downloaded VB and installed Win2k3 and tried to add a host interface with which I removed and added again.

Now I can't change anything, not in the Win2k3 install, but the other VM's are inaccesable as well (exact same error).


Assertion failed: [VBOX_SUCCESS (vrc)] at 'E:\vbox\1.3-w32-rel\src\VBox\Main\MachineImpl.cpp' (4087) in Machine::openConfigLoader. VERR_OPEN_FAILED (-101) - File/Device open failed.. Please contact the product vendor!.

Result Code: E_FAIL (0x80004005) Component: Machine Interface: IMachine {fd443ec1-0009-4f5b-9282-d72760a66916}


comment:5 by Sander van Leeuwen, 17 years ago

There was some bad heap corruption (windows host only) in the host interface remove case. Possibly with creation as well. This may have resulted in corrupted xml files. Fixed now.

comment:6 by sPENKMAN, 17 years ago

Good to hear this problem has been solved, I presume this is fixed in version 1.3.8?

comment:7 by Frank Mehnert, 17 years ago

No, 1.3.8 still does not contain the fix. Please wait patient for the next release (most probably 1.4).

comment:8 by Sander van Leeuwen, 17 years ago

Resolution: fixed
Status: newclosed
Version: VirtualBox 1.3.2VirtualBox 1.3.8
Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use