Page 8 of 9

Re: VM doesn't start on Mountain Lion

Posted: 21. Sep 2012, 16:23
by devrac
4.2.1 r80871 fixes the problem for me. Thanks for the quick turnaround on this one.

Re: VM doesn't start on Mountain Lion

Posted: 21. Sep 2012, 16:26
by loukingjr
michaln wrote:
loukingjr wrote:I had already downloaded and installed 4.2.1 and as it turns out it won't work now
Any specifics?
sorry. missed your question. if I try launching a VM with 4.2.1 it just tries to open and immediately quits. no error message although I didn't look at the console.

edit: here's the error log from Console

Re: VM doesn't start on Mountain Lion

Posted: 21. Sep 2012, 16:28
by joustin
Chiming in after a coworker asked me if I even knew that VirtualBox had a paid version - I didn't. Then I looked at the web site, and couldn't find it anywhere. I am a paid owned of both Fusion and Parallels, but I don't really use either of them because almost all of my VM usage is via Vagrant, which only supports VirtualBox at the moment.

Re: VM doesn't start on Mountain Lion

Posted: 21. Sep 2012, 16:57
by loukingjr
I just noticed I can no longer open more than one guest at a time. I don't normally do that but thought I would make a note of it. VB 4.2.0 & OSX 10.8.2

Re: VM doesn't start on Mountain Lion

Posted: 21. Sep 2012, 16:57
by jarty
devrac wrote:4.2.1 r80871 fixes the problem for me. Thanks for the quick turnaround on this one.
Same here. Thanks!

Re: VM doesn't start on Mountain Lion

Posted: 21. Sep 2012, 18:27
by michaln
loukingjr wrote:edit: here's the error log from Console
Is that really the right thing? I don't see anything related to VirtualBox there... just some QuickLook stuff.

Re: VM doesn't start on Mountain Lion

Posted: 21. Sep 2012, 21:20
by loukingjr
michaln wrote:
loukingjr wrote:edit: here's the error log from Console
Is that really the right thing? I don't see anything related to VirtualBox there... just some QuickLook stuff.
I really couldn't say. it's the output of the console when I tried opening a guest under VB 4.2.1.

Re: VM doesn't start on Mountain Lion

Posted: 22. Sep 2012, 00:54
by mukul
Upgrading my VB to the latest release fixed my problem!!!

Thanks guys for turning this around so quickly!

Re: VM doesn't start on Mountain Lion

Posted: 24. Sep 2012, 01:23
by KENTOSI
Yep, upgrading to the newer version fixes the issue for me too. Finally can install Win7 on my Macbook pro .. awesome :mrgreen:

Re: VM doesn't start on Mountain Lion

Posted: 24. Sep 2012, 21:10
by felix822
Can anyone post a link to the new extension pack? I can't find it on the website.

Re: VM doesn't start on Mountain Lion

Posted: 24. Sep 2012, 21:25
by BfdWx
Still unable to use VM with my mid-2011 iMac. System locks up and crashes.

Re: VM doesn't start on Mountain Lion

Posted: 25. Sep 2012, 09:56
by jonhen
I have the same problem since upgrade MacOS yesterday.

Failed to open a session for the virtual machine Windows7.
VT-x is being used by another hypervisor. (VERR_VMX_IN_VMX_ROOT_MODE).
VirtualBox can't operate in VMX root mode. Please close all other virtualization programs. (VERR_VMX_IN_VMX_ROOT_MODE).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: Console
Interface: IConsole {db7ab4ca-2a3f-4183-9243-c1208da92392}

It's the same problem with virtual machine with Oracle VM.

Environment:
Systemversion: OS X 10.8.2 (12C54)
Kernelversion: Darwin 12.2.0

Regards Jonas

Re: VM doesn't start on Mountain Lion

Posted: 26. Sep 2012, 16:02
by gboswellsac
First Kudo's to Oracle/VirtualBox for the responses and fixes for what is an Apple failure to test before sending out products and software updates. Steve Jobs is being missed a lot now days. I have the infamous Mid 2012 IvyBridge 13" MBP and had to upgrade to 10.8.2 to be able to use the projectors in the classroom. That did solve that problem but the VB still will not work. 4.1.23-80 will install but gives erro when trying to start virtual (worked with Lion on pre-ivy bridge):
> Failed to open a session for the virtual machine Fedora 13 TEST.
>The virtual machine 'Fedora 13 TEST' has terminated unexpectedly during startup with exit code 1.
>Result Code: NS_ERROR_FAILURE (0x80004005)
>Component: Machine
>Interface: IMachine {5eaa9319-62fc-4b0a-843c-0cb1940f8a91}

Also separate error shows up as :
>RTR3init failed with rc=-1912 (rc=-1912)

I removed the 4.1.23-80 and tried to install the 4.2.1-80871 and get the Installation Failed to Install contact the Manuf.....

Sorry to be asking for assistance but I have several students with the same problem and I need to find a solution. Will attempt anything you might suggest. As Faculty I have Parallels and Fusion but I have been a VirtualBox promoter for those with Linux and OS X platforms for years and in our Virtual intro OS classes the VirtualBox sometimes is the only answer many students can afford and/or use. Thanks for any assistance.

BTW I would go to Apple about this but when I did about the Projector problem I was told "Live with It" , MacRumors had fix in 4 hours the upgrade to 10.8.2 but now VB does not work. May be my last Mac.

I see most others with Mt Lion now work may be just the IvyBridge.

Re: VM doesn't start on Mountain Lion

Posted: 26. Sep 2012, 16:27
by loukingjr
gboswellsac wrote:First Kudo's to Oracle/VirtualBox for the responses and fixes for what is an Apple failure to test before sending out products and software updates.
I just have a comment about this post. I have been around computers all my life and I don't remember any OS that had a major update where some piece of software didn't break. Usually many will and do break. It is near impossible for any manufacturer to test all possible configurations of hardware and software. Most problems an individual may run into has to do with what software is installed. I have owned Macs since the mid 80s and if and when something broke, I certainly didn't think to myself, "Apple dropped the ball on this one", and decide I would never purchase any more Apple products. It defies logic to me. If you do find a perfect OS and hardware where everything works despite major changes let me know.

Re: VM doesn't start on Mountain Lion

Posted: 26. Sep 2012, 19:42
by gboswellsac
loukingjr wrote:
gboswellsac wrote:First Kudo's to Oracle/VirtualBox for the responses and fixes for what is an Apple failure to test before sending out products and software updates.
I just have a comment about this post. I have been around computers all my life and I don't remember any OS that had a major update where some piece of software didn't break. Usually many will and do break. It is near impossible for any manufacturer to test all possible configurations of hardware and software.
I stand corrected in the light of your experience but I've come to expect that when a manufacturer has 100% control of the hardware and 100% control of the OS running on it that maybe I could expect most everything to work out of the box on the equipment, and from my first OS X in 2006 this was for the most part true with Apple. Yes much better than the work necessary to get Linux to work on a system as it has no control of hardware and unlike Windows who can financially twist arms to provide the drivers or personel to achieve success. With my new "IvyBridge" model I've had to make several upgrades and modifications just to do what I did normal on the 2011MBP with Lion. Every time I turn around now something that worked with Leopard or Lion (pre IvyBridge) does not work on this box. Now I had to upgrade to 10.8.2 just to be able to plug into a generic projector without shutting down the complete system and rebooting (Apple support said "just live with it", but now the VB does not work nor some other items. I love the Mac but I have come to expect for the $ paid that things just work, and that is no longer the case. Yes I expect glitches on the bleeding edge of Linux but I see a increasing lack of testing of new products by Apple and it disturbs me, as I believe it should others. VirtualBox has been the prime virtual on just about every Mac I and my students have used, 1 for the economy and 2 for the diversity of functions. Now maybe Oracle does not pay Apple to test or have engineers on staff but it should be tested by Apple as a key product that has allowed Apple to move into the realm of Windows users, boot camp or dual booting is old tech.

Apologies for the comments to all, but yes I expect more from Apple and I applaud VirtualBox for filling in the gaps for the failure of Apple to functionally test a new OS on a New platform using a product that is used by more than a minor number of Mac users.