virtualbox.org

Hi guys

I've been using VBox for a while to run a Windows 10 VM for an old finance app I use in Windows.

The iMac host is a 2014 iMac running OSX 10.15.7.

Starting the Windows VM take an age and then actually starting the app similarly takes a long time. Periodically while using the Windows app, it stops responding.

It's been like this for some while and I've just ignored it.

Decided to dive in a bit more to it today and found this forum.

I've since changed some settings on the VM:

4 GB RAM
2 CPUs
3D graphics enabled
256 MB video RAM
And "Use Host I/O Cache" for the SATA controller

All find on the forum.

I've restarted the host now and was excited but it's exactly the same.

Zipped log file attached - after the above changes were made and I've shut down the VM.

Even going to click the Windows home button to power down is very very very slow.

Any suggestions how I can improve things?

Thanks in advance.

-- Jason

For slow Mac performance, try this by "63BottlesOfBeer":

viewtopic.php?f=8&t=90446&start=75#p470879
viewtopic.php?f=8&t=91864&p=491209#p491209
1. Navigate to Apps folder. Choose VirtualBox.app
2. Right click on VirtualBox.app, Show Package Contents.
3. Contents -> Resources -> VirtualBoxVM.app (right click -> Get info)
4. Check the "Open in Low Resolution" checkbox.
5. Run the Virtual Machine in 100% scale mode.

Hello together,

I have the same issues. I tried the solution (editing the Info.plist file). Unfortunately terminates the Guest System does not start anymore. This is the error message:

Result Code:
NS_ERROR_FAILURE (0X80004005)
Component:
MachineWrap
Interface:
IMachine {300763af-5d6b-46e6-aa96-273eac15538a}

I use macOs Monterey 12.6.5 on MacBook Pro 2016

Has anyone an idea?

That Result Code is common to all Virtualbox errors. There was something above that Result Code that was the important part of the error message. No idea what to do so far.

rocknrolli wrote: I tried the solution (editing the Info.plist file). Unfortunately terminates the Guest System

This sounds like you made the edit while the VM was running. Not a really good idea to switch the foundation under a running app. Unless this really means something else.

Hi scottgus1,

I've tried a few more times. The VM didn't run. As soon as I make the change to the Info.plist, the VirtualBoxVM.app no longer starts. Resetting doesn't help either. I then uninstalled and reinstalled VirtualBox. Then it started again - but very slowly as usual.

This is the complete error message:
VM Name: Windows 10 Professional

The virtual machine 'Windows 10 Professional' has terminated unexpectedly during startup because of signal 9.
Result Code:
NS_ERROR_FAILURE (0X80004005)
Component:
MachineWrap
Interface:
IMachine {300763af-5d6b-46e6-aa96-273eac15538a}

Thanks! Unfortunately I'm not sure what to do with that error. Could be a bad bit of data in the plist file?

A Mac guru might be able to make something of this.

Assuming MacOS is the same as *nix, then signal 9 is "SIGKILL", which as far as I can tell means a deliberate termination of the app, i.e. something commanded the MacOS kernel to immediately kill that process. That could be because of some external fault, or perhaps Windows itself was unhappy for some reason.

FWIW, you're the second user reporting this issue this year. See Signal 9 for what to check in regard of code signing VirtualBoxVM.app.