Dr. T wrote:However, the installation process now hangs when it gets to a screen reading "Welcome"...
Then hang - I cannot click on anything, it is just stuck.
The point that you were getting stuck seemed weird from the beginning. Then I remembered that this is the point where sound is played for the first time during the installation!!!
So, I downgraded to 4.3.40
(it still works fine in 10.11.6), and I run my own 10.6 guest. It run fine, it even ignored the --cpu-profile key as it should
[1]. And then I compared the two logs. And I did
*not* like the following from your log:
00:00:00.743028 CoreAudio: Using input device: USB Audio Device (UID: AppleUSBAudioEngine:C-Media Electronics Inc.:USB Audio Device:fd124300:2,1)
00:00:00.763188 HdaCodec: can't open in fmt(freq: 44100)
00:00:00.763634 CoreAudio: Using output device: Built-in Output (UID: AppleHDAEngineOutput:1B,0,1,1:0)
00:00:00.764042 HdaCodec: can't open out fmt(freq: 44100)
I see two problems there; 1) you're using a USB audio device, try to get rid of it, and 2) there is complain about the frequency both in the input and the output stream.
First thing to try? Disable the Audio in your VM. See if that gets you any further. After you're up and running (hopefully), you can try and re-enabling it again. Then try without the USB Audio device. See if that makes a difference.
Generally speaking, OSX and Audio are not the best friends. One key contributor to these forums (an OSX "zealot"
), decided to actively abstain from any further discussions until the audio issues are resolved. Just to give you a hint, in the latest 5.1.2x series, if you have audio enabled,
almost all OSX VMs crash and burn
(I need to file a bug report for this one when I get some free time).
I had an old post about
OSX on OSX. It hasn't been updated in a long, long time. But, one of the key advice in there was:
- You'd better disable audio in the VM settings. If it is detected, it is prone to kernel panics on the guest (10.6) and performance issues.
I should have remembered that earlier. It would have saved us a lot of grief...
[1]: The code for the "CPU compatibility" is completely different in the 5.x series, that's why the key is not required in the 4.3.x series.