Ticket #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
comment:2 Changed 16 years ago by achimha
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 Changed 16 years ago by petur
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 Changed 16 years ago by sPENKMAN
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 Changed 16 years ago by sandervl73
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 Changed 16 years ago by sPENKMAN
Good to hear this problem has been solved, I presume this is fixed in version 1.3.8?
You have to administrator. We will address this in a future release.