[Solved]VirtualBox cant boot VM/No session

[memcpy]

Solved, Install the latest pre-release of VirtualBox and then install the extension pack!


i have an issue with my virtual machines, they wont boot at all. Before i go in futher detail im going to post some specifications and what if already have tried.

Host Machine
OS: Windows 8.0 Enterprise 64 bit
CPU: i7 860
RAM: 8 GB
GPU: HD 5850
SSD/HDD: Samsung Evo 840 & Samsung HD502J
Current VirtualBox version: 3.1.0
Previosly installed versions: 4.0.24 & 4.3.10

Guest Machine
OS: Linux / Other Linux ( To install Linux Mint 16 x86)
RAM: 1024 MB (Enabled IO-APIC)
CPU: 1 Processor ( Enabled PAE/NX + Enabled VT-X/AMD-V)
GPU: 25MB ( 2D and 3D Acceleration )
Storage: 80 GB HDD on IDE.
Network: 1 NAT Adapter.
No guest addition installed!

No logs where created by the virtual machine

Actions taken:
- Run in compatiblity mode (Windows 7, Vista)
- Run as Administrator.
- Change Guest machine OS (Windows 7,XP and Ubuntu)
- Disabling settings on VM one by one.
- Deinstalling VirtualBox (+ All settings and VM). And tryed older and newers versions. (+ Extension pack).
- Changed virtualization settings in BIOS (on and off).

Symptons:
I start VirtualBox and this works like normal, starts propperly. I click the (already added) virtual machine and start it up. Once i double click it after a few seconds a new instance of VirtualBox window (not the Virtual Machine Window), and on the first window is says "Spawing session 0%". Once i close the windows that VirtualBox opened, there will be a error message on the screen saying "Virtual Machine has terminated unexpectedly during startup (E_FAIL 0x80004005)". Nothing furthers happen.

Screenshots:
- Inital windows when VBox starts:

1.PNG (45.86 KiB) Viewed 1188 times

- When i start the VM:

2.PNG (66.49 KiB) Viewed 1188 times

- When i close the opened window:

3.PNG (11.92 KiB) Viewed 1188 times

I think this has probaberly to do with the Windows 8 host system. Can you guys help me out with this?
Have been looking for a few days now on the interwebs but with no luck. Im a IT student, so dont hold down on the technical jargon +)

Thanks in advance,

Alex Bouma

[Perryg]

Missing two key pieces of the puzzle
Post the guests log file ( as an attachment )
Post the complete name of the install file for the guest.

[memcpy]

Missing two key pieces of the puzzle
Post the guests log file ( as an attachment )
Post the complete name of the install file for the guest.

The virtual machine does actually not create an log, in the map there is only a .vdi file. I just noticed that my .vbox file is missing ;o
And sound a bit dumb but wich "Install file". I just made a new VirtualMachine with a empty hdd etc.

@Update now trying a version "VirtualBox-4.3.10-93012"

Thanks for your awnser.

[mpack]

If the starts to run at all then it creates a log in the "Logs" subfolder.

If yours isn't even getting that far then you can't have installed the software properly. Make sure you use "Run as administrator" to run the installer, and install for the correct user (i.e. not user "admin"). And don't leave any optional components out.

Finally, make sure the hosts "Driver Signature Enforcement" feature is not configured to silently discard non-MS drivers.

[memcpy]

Then you probably need to reinstall the software. Make sure you use "Run as administrator" to run the installer, and install for the correct user (i.e. not user "admin").

I will verify that for you.

@Update We have installed newest version of VirtualBox ( i believe its a pre-release ).
We seem to make progress due the fact he actually create's a Log folder, log files and a .vbox file.

The problem now is when the virtual machine starts it shows up and goes away almost immediately, giving the same error as before (0x80004005)

Here are the logs:

Linux Mint.zip

(20.92 KiB) Downloaded 1 time

And could it be that i have my VirtualBox installation on the HDD and my Virtual Machine on the other SSD drive (2 separate drives)?

@Oh god i solved it, just installing extension pack and VirtualBox worked like a charm. Thanks guys for the efford you put in

[mpack]

That can't be the complete story - VirtualBox doesn't require the extension pack unless you use one of the special features, in which case I would expect a less generic error. This is the kind of error I might expect if you try to restore a saved state - which of course might be relying on the presence of a valid extension pack.