Error starting Virtual machines on virtualbox - Yosemite

[LinkRaider]

Hi,

I recently bought a MAC with Yosemite and I was trying to start virtual machines but I can't do it because a critical error shows up: http://screencast.com/t/xcLayPxs3

I thought that I was doing something wrong so I downloaded a .vdi sandbox (IE10 - Win7) from the but the error is exactly the same.

On this second machine (Windows7) I only created the VM and didn't even associated an ISO file, so the error that I should get should be "Error: No operative system found: System Halted!" but I don't even get there.

I've checked the log but I didn't found anything unusual (I might not have enough knownledge to know how to read them tho): https://drive.google.com/file/d/0B_0nd3 ... sp=sharing

My MAC is the MGX082 model, please note that before this I tried with vmware fusion 7 but it showed up a similar error. I've also commented this with a friend of mine and he said that he had to enable some things on his motherboard... but he's using a Windows computer.

Is he right? Do I have to enable something on my MAC in order to enable the virtualization?

Thanks in advance

[loukingjr]

Hi,

My MAC is the MGX082 model, please note that before this I tried with vmware fusion 7 but it showed up a similar error. I've also commented this with a friend of mine and he said that he had to enable some things on his motherboard... but he's using a Windows computer.

Is he right? Do I have to enable something on my MAC in order to enable the virtualization?

Thanks in advance

No, he is not right.
Try uninstalling VirtualBox using the VirtualBox_Uninstall.tool
Then run Disk Utility, Repair Disk Permissions.
Then reinstall VirtualBox 4.3.20.

[socratis]

1. Do NOT post links to 3rd party sites. Most people do not follow them.
2. Why did you change the "recipe" for the VM? From what I see in your logs, you have enabled EFI boot. Change it. And since you're new in this, you should be trusting the defaults until you know what they're doing.

[loukingjr]

I would be one of of those "most people". socratis is correct. EFI should be disabled.

[LinkRaider]

Thanks for all the fast replies

And yes I'm new at this, how do I disable the EFI boot? Is there a simple way to do it? When I search on google I just find "uefi boot", and I'm not sure if it's the same thing... :s

If that doesn't work, I'll try to reinstall it using the tool that loukingjr mentioned

[mpack]

You change it in the VM settings, the same place where you enabled it.

[loukingjr]

In the VirtualBox Manager: System>Motherboard uncheck "Enable EFI (special OSes only)

[LinkRaider]

Just a quick update: I disabled the option but I'm getting the same error.

Tomorrow I'll use the tool mentioned and try again, if it doesn't work I'll post a new log.

Thanks for all the help guys

[LinkRaider]

So, I managed to do the test sooner and after running the uninstall tool the behaviour persists.

This time I didn't change anything, I did a "next next next" installation with everything default without even selecting the .iso .

After that I started the VM, a window popped-up requesting for an .iso (or .img or wtv) and I selected my ISO file. After this, the machine crashed with the same critical error as before. The screen is all black.

I got a new log:
https://drive.google.com/file/d/0B_0nd3 ... sp=sharing


Suspecting that it could be an error directly related to the with my OS file I created a new VM and selected Ubuntu x64 without selecting any .iso . It popped-up a window asking for the .iso (again) but this time I didn't select anything. After this a message showed up on the black screen saying "IPXE (http://ipxe.org) 00:0D E200 PCI2.10" but a second later the same "critical error" message appeared.

I got that log right here:
https://drive.google.com/open?id=0B_0nd ... authuser=0

I'm out of ideas... what am I doing wrong?

[loukingjr]

socratis already mentioned you shouldn't be posting links to other sites and now you've posted two more. That is one thing you are doing wrong. You can attach screen shots and logs directly in your posts without us having to chase them on other sites.

See the Upload attachment tab below the message area when you are creating one.

screen shots and logs have to be 128k or less so you might have to compress a log and resize a screen shot.

Did you repair disk permissions?

[LinkRaider]

Yes I did but the error appeared anyway.

One thing weird tho, when I run the uninstall tool and then install virtualbox again the virtual machines still appear. If I change the path of the old VMs it just shows them as inaccessible... Shouldn't they disappear completely? I'm using an uninstaller after all...

Thanks guys. And I won't post links anymore

[loukingjr]

The guests aren't supposed to be uninstalled. Just the program and its files so you can still use them when you update VirtualBox. They become inaccessible because VirtualBox doesn't know where you moved them.

You don't have Fusion running by any chance when you've been testing VirtualBox? They can't be run at the same time.

[LinkRaider]

I installed Vmware Fusion before, and I had a similar error so I decided to uninstall it and try with Virtualbox.

Could it be that the Vmware Fusion wasn't uninstalled correctly? Since on Mac OS all the files are on the "filename.app" I think it was correctly uninstalled. Or am I wrong and there something like a regedit (kernel calls for instance?) that are preventing me from booting the VMs?

I honestly don't think that's the case because, like I said, VMware Fusion was also showing errors but please let me know your opinion

[loukingjr]

Fusion can be installed. You just can't run them at the same time.

In the last log you posted you got a guru meditation error…

00:00:25.873739 !! Guru Meditation -4014 (VERR_VMX_INVALID_GUEST_STATE)
00:00:26.912985 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'.

Why I don't know. My thoughts are at this point, there is something wrong with the sources you are trying to use to install guests or, some third party app is conflicting with VirtualBox. Maybe someone else knows.

[rpmurray]

Your logs show that the extensions pack hasn't been installed. Try installing it and see if that makes a difference.