VirtualBox

Ticket #114 (closed defect: fixed)

Opened 7 years ago

Last modified 4 years ago

failed to load the global gui configuration - after setup host network

Reported by: ks2 Owned by:
Priority: major Component: other
Version: VirtualBox 1.3.6 Keywords: network local interface
Cc: Guest type: other
Host type: other

Description

I have changed the network configuration for a virtual machine from nat to localnetwork. after this i can not start virtualbox

my system: windows 2000 sp4, amd athlon 64 fx-62 dual core, 1gb ram

this is the error message: failed to load the global gui configuration

Assertion failed: [VBOX_SUCCESS (vrc)] at 'E:\vbox\1.3-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:1 Changed 7 years ago by techie

I can confirm. With NAT it was impossible to get access to/from virtual machine via network. The situation with Host Interface Networking is even worse. First there were several errors while installing interface and now there is this error above. The system is the same, except it is 32 dual core Intel.

comment:2 Changed 7 years ago by techie

The lines that cause failure are:

<Adapter MACAddress="0800270E65B1" cable="true" enabled="true" slot="0" type="Am79C973">

<HostInterface name="NewInter"/>

</Adapter>

comment:3 Changed 7 years ago by techie

Also while adding new host interface the following message is displayed:

Failed to set interface name (ret=0x80004005, pCfgGuidString='', cbSize=100).


Result Code: 
E_FAIL (0x80004005)
Component: 
Host
Interface: 
IHost {fd443ec1-000b-4f5b-9282-d72760a66916}

comment:4 follow-up: ↓ 6 Changed 7 years ago by techie

Strangely enough, but after this attempt "Local Area Connection 2" interface had appeared. Selecting it and closing VirtualBox yields in another error:

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

comment:5 Changed 7 years ago by sandervl73

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

There was a bug in the add and remove host interface method. This caused a crash and possible corruption of your xml files. (Windows host only) The fix will be included in the next version. (due out soon)

comment:6 in reply to: ↑ 4 Changed 7 years ago by negations

  • Status changed from closed to reopened
  • Resolution fixed deleted

Replying to techie:

Strangely enough, but after this attempt "Local Area Connection 2" interface had appeared. Selecting it and closing VirtualBox yields in another error:

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

I am getting the same on 1.3.8:

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:7 Changed 7 years ago by negations

I am getting the same on 1.3.8:

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}

Windows XP keeps refusing to load the tapi file and it has a yellow asterix marker in the hardware device panel.

comment:8 Changed 7 years ago by frank

  • Status changed from reopened to closed
  • Resolution set to fixed

This was fixed for 1.4.0 not for 1.3.8. Please try again and reopen if necessary.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use