I'm attempting to install Snow Leopard Server 10.6.3 on Parallels Desktop 5.0.9376, however almost immediately after powering on the VM to boot from the installation DVD, the Apple logo shows and then Parallels crashes. The crash report ID is 9261141 I'd put the details in this post, but I can't seem to find where the Parallels crash reporter saves its reports. I tried the same steps on my old MacBookPro3,1 and the installer is running fine. The software environment is exactly the same, since I used the OSX Migration Wizard when I got the new one. Which leads me to believe that Parallels perhaps doesn't support the new i7 processor or something else hardware-related? Hardware Overview: Model Name: MacBook Pro Model Identifier: MacBookPro8,2 Processor Name: Intel Core i7 Processor Speed: 2.2 GHz Number of Processors: 1 Total Number of Cores: 4 L2 Cache (per Core): 256 KB L3 Cache: 6 MB Memory: 8 GB Boot ROM Version: MBP81.0047.B0E SMC Version (system): 1.69f1 Any ideas?
OK, I found the logs (~/Library/Logs/Parallels/Problem Reports/). This may be the relevant parts of vm.log: 13:14:32.673 F /vm:12793:1d03/ Vm {eb220e06-50f0-4e19-83f2-504c745ff10a} processed command DspCmdVmInitiateDevStateNotifications with status 1 13:14:33.880 F /vm:12793:6903/ Virtual machine is ready to boot! Chipset Type i965, 1 CPU(s) (NORTH HUB DID&VID=0x808629A0) $#HPET INIT FirstStartInit is OK [1f:0] Secondary bus number 0xff [1f:0] Secondary bus number 0xd0 [ept] Loading PDPTEs on VCPU 0 Events history for VCPU 0: - VM-exit EPT violation (48) - VM-exit EPT violation (48) - VM-exit EPT violation (48) - VM-exit EPT violation (48) - VM-exit EPT violation (48) - VM-exit EPT violation (48) - VM-exit EPT violation (48) - VM-exit triple fault (2) [Abort] VMCS revision identifier: 0x10 [Abort] VMX abort indicator: 0x0 [Abort] VM-instruction error code: 0x0 ABORT at Core\VtxWork.cpp:5316 <PANIC@56.14(0x2)>, flushing log buffer ------------ Monitor Abort ------------ mon.abort.message = PANIC@56.14(0x2) mon.abort.vcpu = 0 mon.abort.FastMonCall = command '-' cs:eip 0:0000000000000000 ss:esp 0:fffff00000000000 mon.abort.FarJmp = 0:0000000000000000 modeId -1 - mon.info.version = 5.0.9376.599993 mon.info.build = Fri, 27 Aug 2010 13:24:33 mon.info.assertions = off mon.info.extended = HVT: ON ( VTX - ON ; SVM - OFF ) MonitorLin: x64 Primary OS MacOS x64 mon.info.cpu = GenuineIntel 062A7 [ Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz] (id=1) mon.info.vtx_features: TPR shadow, MSR bitmaps, virtual APIC, EPT, VPID, unrestricted, preemption timer mon.info.paravirt state=0 m_ver=4.1 mon.info.hyperv 0 ------------ Monitor Parameters ------------ <snip> 13:57:30.912 F /vm:12984:6703/ Monitor issued Abort command! 13:57:30.912 F /MCDException:12984:6703/ (!) Error: Throwing exception id=2147484160 (PRL_ERR_VM_MONITOR). 13:57:30.976 F /vm:12984:3707/ Event loop terminated - deinited 13:57:30.976 F /vm:12984:3707/ Setting ASYNC_REQ_SHUTDOWN for Vm 13:57:30.977 F /vm:12984:3707/ Terminating CPU #0 ... 13:57:31.044 F /vm:12984:3707/ [Devices] Terminating... Attached is the full vm.log file.
Just to follow up on my own message again, I think I may know what the issue is. I am attempting to install Snow Leopard Server 10.6.3 on a Core i7 system. But 10.6.3 apparently doesn't support the i7. More details: http://kb.vmware.com/selfservice/mi...nguage=en_US&cmd=displayKC&externalId=1026103
One final follow-up... I took the Parallels VM that had been upgraded to 10.6.8 on my old macbook and copied it to the new one. It works fine (so far). So I'd say that my hunch was correct. Parallels could handle the situation more gracefully, though.
"so far" was the key phrase there. The OSX guest will run for somewhere between 1 and 30 minutes before kernel panicking. This is on either my old or new macbook. How can Parallels even advertise support for running Snow Leopard as a guest?
