VirtualBox can't start any VM

[retro01]

Hi all!

I still am trying to get VirtualBox to work with my computer. It doesn't matter what type of virtual mashine I use, i.e win8, android or ubunto, the start gets interrupted with a critical error message.

It doesn't matter which virtualbox version I use, the same message pops up if I try to start a vm. I tried the version 3.x - the current version.

I need the mashine to run android for development and i work on my laptop but not on my desktop mashine. VmwarePlayer works without any problems and I think to remember, that virtualbox worked for me a 1 or 2 years ago on the same desktop mashine, but now it doesn't.

The log-file of the newly created win8 mashine is attached.

[fb0001]

Same Problem

Running windows 8.1 as a host

[mpack]

@retro01
You have provided a log file from 4.2.12, was that intended?

VirtualBox VM 4.2.12 r84980 win.amd64 (Apr 12 2013 11:35:06) release log
00:00:01.800322 Installed Extension Packs:
00:00:01.800365 Oracle VM VirtualBox Extension Pack (Version: 4.3.0 r89960; VRDE Module: VBoxVRDP unusable because of 'VBoxExtPackRegister returned

Then the error :-

00:00:02.439100 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:02.439103 !!
00:00:02.439104 !! Guru Meditation -4014 (VERR_VMX_INVALID_GUEST_STATE)
00:00:02.439140 !!

Are you using a saved state with this VM? I'm interpreting the error as meaning that the VM is trying to restore a VMX context from a sav file, and this results in an invalid state for the guest. Try discarding the saved state if you are using one. This is especially important if the saved states were created by 4.3.0 as backwards compatibility is not intended.

@fb0001:
You are running a different version of VirtualBox, so I doubt you have the same problem.

[Ramshankar]

Not really the same problem. The original report is for VirtualBox 4.2.12 with an invalid guest state guru in an Intel box.

Your log indicates a triple-fault guru for VirtualBox 4.3 on an AMD CPU, which is quite different code. Could you please provide more details about the guest. It says "Ubuntu 64" but which version of Ubuntu is this, it would help us in replicating the problem.

[fb0001]

Xubuntu 13.10 64bit version

[retro01]

You have provided a log file from 4.2.12, was that intended?

Yes, it is intended. I deinstalled all virtualbox versions and tried the virtualbox version, which is shipped with Genymotion for a last try. At first I tried the current 4.3 version an downloaded the extention pack, but virtualbox wouldn't start any VMs. I deinstalled 4.3 and I tried to install an older Version.

Are you using a saved state with this VM? I'm interpreting the error as meaning that the VM is trying to restore a VMX context from a sav file, and this results in an invalid state for the guest. Try discarding the saved state if you are using one. This is especially important if the saved states were created by 4.3.0 as backwards compatibility is not intended.

I only created a new win8x64 VM to install win8 to test whether it works with another VM. I selected 'vmdk' as disk format. Like I said, I tried different virtualbox version from 4.3 down to some arbitrary 3.x version and everytime I get a critical error message with the given log output.

[mpack]

I'm not sure that you've understood the point that it's an error to use a newer extpack with older software (or any other extpack mismatch).

[mpack]

Xubuntu 13.10 64bit version

If your problem is not the same as the OPs then please start your own topic. If your problem is the same then there's no need for an additional discussion.

[retro01]

I'm not sure that you've understood the point that it's an error to use a newer extpack with older software (or any other extpack mismatch).

In that case, shouldn't virtualbox notify me that there would be a compatiblity issue because of the mismatch of virtualbox and expansion pack versions ?

But that doesn't matter. Again I uninstalled the 4.2 version of virtualbox with the expansion pack and installed the current 4.3 version. I've created a win8x64 VM and tried to start it. And again virtualbox failed with an critical error. Afterwards I installed the current version of the extension pack and created a win8x64 VM again. It failed again.

As far I understand, it doesn't matter which version I use.

Attached the last log output

[mpack]

Which template did you use when creating this VM? You mention going all the way down to VBox version 3.x, which would be unwise because the VM folder structure was incompatible, plus these older versions had no support for Win8 guests (naturally not, since 3.x precedes Win8 by years), and of course Win8 as a host was also not supported until recently.

I suggest that start again, install a recent version of VirtualBox - i.e. one which claims support for Win8 - and make sure that you have admin rights for the installation, and that your host is not configured to silently reject installation of non MS device drivers (Driver Signature Enforcement).

Oh, and make sure you don't have the Hyper-v feature enabled on your host, as that will prevent many VMs from running - including all Win8 VMs and all 64bit VMs.

[retro01]

Which template did you use when creating this VM?

For the win8 vm I used the current virtualbox version 4.3 because it supports the template. For the version 3.x I used the ubunto template to test.

I suggest that start again, install a recent version of VirtualBox - i.e. one which claims support for Win8 - and make sure that you have admin rights for the installation, and that your host is not configured to silently reject installation of non MS device drivers (Driver Signature Enforcement).

Oh, and make sure you don't have the Hyper-v feature enabled on your host, as that will prevent many VMs from running - including all Win8 VMs and all 64bit VMs.

I uninstalled virtualbox and disabled Driver Signature Enforcement (Hyper-V was already disabled). Afterwards I installed virtualbox 4.3 via an admin account. Under the admin account I created a win8x64 template. Virtualbox displayed the same behaviour: it stopped with a critical error. Log-file ist attached.

[mpack]

In that case I'm out of ideas. I suggest you raise a BugTracker ticket for it.