Koos wrote:I have an old Mac Pro running Mac OS 10.7.5. Sadly thats the OS highest version it will run.
Then, according to my notes, you're talking about a MacPro1,1 or MacPro2,1. In the best case scenario, you have a MacPro2,1 which has a Intel Xeon 5300 series ("Clovertown") in there. And according to the log:
00:00:00.661 DMI Product Name: MacPro2,1
00:00:00.766 Full Name: Intel(R) Xeon(R) CPU X5355 @ 2.66GHz
Right on the money!

The
Xeon 5355 CPU is capable enough, including the most important feature, VT-x.
But, I believe that neither the OS (from 2012-10-04), nor VirtualBox could manage with the latest guest OSes. BTW, have you tried to run anything higher than 4.0.36? Because the manual states:
Support for Mac OS X 10.7 (Lion) and earlier was removed with VirtualBox 5.0.
which means that you
could run up to 4.3.40, from 2016-08-22. A whole lot newer version!
Of course the manual also states:
Support for Mac OS X 10.9 (Mavericks) was removed with VirtualBox 5.2.
which is completely bogus, because that's where I'm compiling and running VirtualBox on!
| Edit: Just got dev clarification; "it's not supported" doesn't mean "it won't run". I should have known better... |
I think that your main problem is VirtualBox and its version. Unfortunately, I cannot test at the moment 4.0.36, my OSX 10.11.6 is too new for such an old VirtualBox version. I urge you try 4.3.40, you got nothing to lose. The problem I think comes from this:
00:00:00.663 Package type: DARWIN_32BITS_GENERIC
I haven't seen one of those for ages. Not sure why you got the 32-bit one, because after 10.6, the whole thing was 64-bit...
00:00:00.758 [/Devices/ich9pci/0/] (level 3)
00:00:00.758 Trusted <integer> = 0x0000000000000001 (1)
Not only you have a way too old version, but you're using unsupported, experimental (even today) settings! Why did you enable the ICH9 chipset? Can you hover over the Chipset and read the tooltip?
So, in summary:
- Uninstall VirtualBox 4.0.36, install version 4.3.40.
- Remove the VM, including all its files (you got nothing to lose at this point) and create a new VM from scratch. Stick with the defaults!!!
- If none of the above works, try an older Mint release, your hardware/software combination is too old for the latest and the greatest.