VB 4.1 won't run newly configured OSX

[budy]

Hi,

when I configure a new OS X guest, regardless of whether it being 32 or 64 bit, I am getting this error when starting up the VM:

VirtualBox 4.1.0 r73009 solaris.amd64 (Jul 19 2011 12:19:28) release log
00:00:15.364 Log opened 2011-08-13T06:23:54.867170000Z
00:00:15.364 OS Product: SunOS
00:00:15.364 OS Release: 5.11
00:00:15.364 OS Version: 151.0.1.8
00:00:15.364 DMI Product Name: MacPro1,1
00:00:15.364 DMI Product Version: 1.0
00:00:15.368 Host RAM: 32754MB RAM, available: 22539MB
00:00:15.368 Executable: /opt/VirtualBox/amd64/VirtualBox
00:00:15.368 Process ID: 25948
00:00:15.368 Package type: SOLARIS_64BITS_GENERIC
00:00:15.378 Installed Extension Packs:
00:00:15.378 Oracle VM VirtualBox Extension Pack (Version: 4.1.0 r73009; VRDE Module: VBoxVRDP)
00:00:15.382 SUP: Opened VMMR0.r0 (/opt/VirtualBox/amd64/VMMR0.r0) at 0xfffffffff85e0020.
00:00:15.393 Using MWAIT extensions
00:00:15.394 Using XKB for keycode to scan code conversion
00:00:15.404 VMSetError: /home/vbox/tinderbox/sol-rel/src/VBox/VMM/VMMR3/VM.cpp(362) int VMR3Create(uint32_t, const VMM2USERMETHODS*, void (*)(VM*, void*, int, const char*, unsigned int, const char*, const char*, __va_list_tag*), void*, int (*)(VM*, void*), void*, VM**); rc=VERR_FILE_NOT_FOUND
00:00:15.404 VMSetError: File not found.
00:00:15.404 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={1968b7d3-e3bf-4ceb-99e0-cb7c913317bb} aComponent={Console} aText={File not found. (VERR_FILE_NOT_FOUND)}, preserve=false
00:00:15.437 Power up failed (vrc=VERR_FILE_NOT_FOUND, rc=NS_ERROR_FAILURE (0X80004005))
00:00:15.514 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={1968b7d3-e3bf-4ceb-99e0-cb7c913317bb} aComponent={Console} aText={The virtual machine is not powered up}, preserve=false

What does cause this?

Thanks,
budy

[Martin]

What does cause this?

Maybe http://forums.virtualbox.org/viewtopic.php?f=22&t=31104 ?

[budy]

No - as you can see from the VBox.log VirtualBox is running on a MacPro1,1. This is definetively within Apple's SLA. We do also run Parallels BareMetal for Mac, in this case the host OS is Linux and not OS X or SLEx11, but this is completely seperated from the SLA for Leopard Server and SL Server, since the SLA doesn't refer to the underlying host OS.

Otherwise, running Parallels BareMetal for Mac would impose a SLA violation as well, which is not the case.

Cheers,
budy

P.S. I did some more testing and this issue is definetively caused by activating "EFI-Support". Seems that somehow the EFI support has been yanked from the 4.1 release of VBox, either by accident or intentionally.

[budy]

So, this seems not to be directly related to trying to run OS X Leopard/Snow Leopard Server VBox 4.1. Instead simply turning on EFI-Support results in this error, even woth earlier versions of VBox. I tried 4.0.12 and 4.0.4 and both of them throw the exact same error, when trying to start up an EFI-enabled guest.

Could be something specific to my installation, so I'd like to ask moderators to move this thread back to the Solaris host section of the forum.

Thanks,
budy