End user forums for VirtualBox
https://forums.virtualbox.org/
socratis wrote:You missed a couple of things. Especially the bold one...socratis wrote:Take a look at OSX on OSX and see some tips on changing the CPUID (look for posts from rpmurray). Again, post the .vbox and the appropriate log.
Already told you where to look and in there it describes how to change it. Apparently you didn't bother taking a look at it:Orion's Bell wrote:As far as CUPID, I seriously don't understand. Where is it? What should I change it to? How do I change it?
As far as what the CPUID is, in short it describes the capabilities of the processor available in your system. By modifying it via the command line, you're presenting a different CPU to your guest than the one that you actually have on your host. Where does that help you? If you want to install an older version of OSX on a newer CPU, it might fail (see your problem). By modifying the CPUID, an older, more compatible CPU is presented to your VM, thus allowing it to work (but not always).socratis wrote:Take a look at OSX on OSX and see some tips on changing the CPUID (look for posts from rpmurray). Again, post the .vbox and the appropriate log.
Basically you need to run this command in your Mac's terminal…Orion's Bell wrote:I did look at it.
I don't understand it.
Code: Select all
VBoxManage modifyvm <vmname> --cpuidset 00000001 000006fb 00000800 80000209 078bfbffloukingjr wrote:Basically you need to run this command in your Mac's terminal…Orion's Bell wrote:I did look at it.
I don't understand it.You need to replace <vmname> with the name of your VM. Enclose it in quotes if it has spaces. I.E., "Snow Leopard".Code: Select all
VBoxManage modifyvm <vmname> --cpuidset 00000001 000006fb 00000800 80000209 078bfbff
