Closed toelke closed 2 years ago
I added
( VBoxManage modifyvm "${vm_name}" --cpuidset 00000001 000106e5 00100800 0098e3fd bfebfbff >/dev/null 2>&1 )
( VBoxManage modifyvm "${vm_name}" --cpu-profile "Intel Core i7-6700K" >/dev/null 2>&1 )
after line 677 of the script, just before startvm
is called.
This seemed to be the most straight forward way to get everything to run correctly.
I wasn't sure about the procedure for setting the cpu-profile otherwise.
( VBoxManage modifyvm "${vm_name}" --cpuidset 00000001 000106e5 00100800 0098e3fd bfebfbff >/dev/null 2>&1 ) ( VBoxManage modifyvm "${vm_name}" --cpu-profile "Intel Core i7-6700K" >/dev/null 2>&1 )
I can confirm that this also works for the AMD Threadripper 3970X
I had to put the --cpuidset
into the script and use Intel Core i7-6700K
as the CPU and set the cpu count to 4. The Intel Xeon X5482 3.20GHz
did not work.
Hey,
when running the script I got an error:
I could fix it using
vboxmanage modifyvm macOS --cpu-profile "Intel Xeon X5482 3.20GHz"
.I have a: