VBox suddenly will not start, with error message.

[nijineko]

Macbook 5,2; OS X 10.6.8; VBox v4.3.6. VBox launches w/o error. Upon start of VM (Windows 7) the following error is received:

Failed to open a session for the virtual machine Astarael_w7.

Failed to map a memory object. (VERR_MAP_FAILED).

Result Code: NS_ERROR_FAILURE (0x80004005) Component: Console Interface: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}

Only recent change to machine is a change to the RAM from 2GB to 6GB. Prior to change in RAM, worked without error, if somewhat slow. Have perused forums, discovered proposed workaround of removing VBox* files from the Library directory with Terminal and reinstalling the latest version of VBox, however, this did not succeed in resolving the problem.

[nijineko]

Log from 3rd start attempt

[Frank Mehnert]

Please decrease the amount of RAM assigned to this VM. Your host runs in 32-bit mode and 2GB virtual RAM is sometimes too much.

[nijineko]

Modifying the available RAM has no effect. Same error message. Tried 2048 and 1024.

[Frank Mehnert]

Please attach the VBox.log file with 1024MB RAM.

[nijineko]

5th start attemp w- 1024 ram

[nijineko]

Please find VBox5.log attached, attempting to launch VM with 1024 ram assigned.

[nijineko]

*Bump* Anything?

[nijineko]

*Bump* Any progress on this ticket?

[Frank Mehnert]

Actually it's not the guest RAM in your case (2048MB is probably still too much but 1024MB should work) but it's the video RAM. Try to decrease the video RAM for this VM, start with 128MB. I know that for 3D the proposed value is 256MB but it might be that on 32-bit OS X this isn't possible at all.

[Frank Mehnert]

Ignore my last comment, it will not help either.

[bird]

A call to ​IOMemoryDescriptor::createMappingInTask with kernel_task as task and length=512KiB fails for some mysterious reason.

The simplest explanation is that the kernel is short on virtual address space for some reason. If that's the case, there isn't much we can do about it.

There is something you could try though, that's booting the 64-bit version of the kernel. See ​http://support.apple.com/kb/HT3773 for details how to do this.

[nijineko]

VM start attempt using 64bit kernel.

[nijineko]

That also apparently does not succeed; follow error received:

Failed to open a session for the virtual machine Astarael_w7.

Failed to map a memory object. (VERR_MAP_FAILED).

Result Code: NS_ERROR_FAILURE (0x80004005) Component: Console Interface: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}

...which appears to be the same error. Attaching the error log, just in case.

[bird]

VBox6.log is still with a 32-bit kernel. There are at least two clues in the log file, "Package type: DARWIN_32BITS_GENERIC" and "root:xnu-1504.15.3~1/RELEASE_I386". The latter can also be called forth on the command line by running uname -a.

[nijineko]

Well, well, well. It seems that despite enabling the 64 bit mode, it does not have the kernel and extension... as shown by System Profiler. I guess I misunderstood the Apple documentation about it. Sigh. Well, in any case, I have a new error with VB v4.3.8. I shall post it here, but I shall also swap the RAM chips in case it doesn't like the 4gb in the one slot for some reason. If that fails to work, I shall downgrade it to the old RAM chips and test again. If it still doesn't work after putting the old RAM chips back, I'm going to have to try to install a Type I hypervisor onto an old pc that I have and attempt to migrate the VM to that box. For your information, here is the most recent error:

Failed to open a session for the virtual machine Astarael_w7.

No error info.

Result Code: NS_ERROR_CALL_FAILED (0x800706BE) Component: ProgressProxy Interface: IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913}

Thank you all, for looking into this matter, and bearing with me.

[nijineko]

Using VB v4.3.8, before ram swap or downgrade.

[nijineko]

Perhaps not very sporting of my to switch versions mid-stream. Here are the two logs, still seems to be the same error message regardless of RAM configuration.

At this point, perhaps you could recommend a Type I hypervisor that I as a private individual could run on an old PC that will also be able to run this Win7 VID file? I'm seeing Citrix XenServer and RTS as my only options, unless I manage to find a x64, in which case I could add Xen to the list. Would you know of any other options for running this VM?

[nijineko]

Swapped RAM positions.

[nijineko]

Using old RAM.

[Frank Mehnert]

After you switched to a 64-bit kernel you probably need to re-install VirtualBox to get the 64-bit VirtualBox extensions installed. But as you don't plan to continue to work with VirtualBox I can probably close this ticket.