[Solved] virtual machines will not start

[sturkel]

After installing v3.0.2 I can't boot up any saved images or boot up newly created ones.
I tried reinstalling, repairing and even installed 2.2.4, but I can't load the images in any way.
I get a VERR_GENERAL_FAILURE error.
This is from the log entry:

Code: Select all

00:00:00.577 VirtualBox 3.0.2 r49928 win.x86 (Jul 10 2009 16:47:07) release log
00:00:00.577 Log opened 2009-07-21T09:10:49.265625000Z
00:00:00.577 OS Product: Windows XP Professional
00:00:00.577 OS Release: 5.1.2600
00:00:00.577 OS Service Pack: 3
00:00:00.578 Host RAM: 2047MB RAM, available: 1530MB
00:00:00.578 Executable: C:\PROGRA~1\Sun\XVMVIR~1\VirtualBox.exe
00:00:00.578 Process ID: 3312
00:00:00.578 Package type: WINDOWS_32BITS_GENERIC
00:00:00.584 SUP: Loaded VMMR0.r0 (C:\PROGRA~1\Sun\XVMVIR~1/VMMR0.r0) at 0x87eed060 - ModuleInit at 0000000087efd880 and ModuleTerm at 0000000087efd8f0
00:00:00.584 SUP: VMMR0EntryEx located at 0000000087efe4b0, VMMR0EntryFast at 0000000087efda50 and VMMR0EntryInt at 0000000087efda40
00:00:00.584 SUP: windbg> .reload /f C:\PROGRA~1\Sun\XVMVIR~1/VMMR0.r0=0x87eed060
00:00:00.664 VBoxSharedClipboard mode: Bidirectional
00:00:00.666 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={0a51994b-cbc6-4686-94eb-d4e4023280e2} aComponent={Console} aText={Unknown error creating VM (VERR_GENERAL_FAILURE)} aWarning=false, preserve=false
00:00:00.674 Power up failed (vrc=VERR_GENERAL_FAILURE, rc=E_FAIL (0X80004005))

I use Windows XP SP3 as host system, and tried several guest OS systems.
The host system has all the latest windows updates available installed.
It runs on a hp nc8230 system with 2gb ram with enough free space.
I tried google for a solution, but I found no items that correspondent with my issue.

[vbox4me2]

Did you see these http://www.google.nl/search?hl=nl&q=0X8 ... .org&meta= ?
4005 is pretty general but there are also lots of hits with possible solutions.

[sturkel]

Did you see these http://www.google.nl/search?hl=nl&q=0X8 ... .org&meta= ?
4005 is pretty general but there are also lots of hits with possible solutions.

I saw that page, but with no effort.
None of them applies to the general error, most of them are driver or security related in none-windows os.
So if someone have an idea in which direction I have to search, it would be great.

[sturkel]

The problem is SOLVED
When I tried running visual studio, I got an error that a ordinal couldn't be found in oleaut32.dll.
I checked that file in the system32 directory, and it was overwitten by a very old version.
I replaced it with a copy of a working windows installation (booted with knoppix) and now vs.net and virtualbox run w/o problems.