Panic(cpu 0 caller 0x003a8d2f): Unable to find driver for this platform: 'ACPI'. Iatkos 5i 10.5.5 Bueno, mi problema es que he intentado instalar iatkos 5i 10.5.5, sin conseguir nada. IPC 10.5.6 y nada tampoco he probado tambien con una version 10.4.8 tiger de Jas y nada el mismo problema.When it was done, I got this message on the screen UNABLE TO FIND DRIVER FOR THIS PLATFORM ACPI.
Panic Unable To Find For This Platform Acpi Install Disc InsertedDebugger called: Mac.(alot of weird stuff and codes in the form of 0xb973_: and some other stuffDarwin Kernel Version 8.6.2:Thu Apr 13 2006So thats what comes up when i try to start a rather new macbook. Its the only thing that comes up after the startup screen with the spinning dashed circle thing. We can't find any other screen, and have only been able to get to some other screen by holding down the 'c' key with the install disc inserted.I've tried two different VMs on two different Xserves. But I'm having trouble with Snow Leopard Server in a 32-bit VM. I've set up virtual machines running various 64-bit versions of macOS from Snow Leopard Server (10.6) to El Capitan (10.11) and they work fine. Hello, I have a number of 64-bit Apple Xserve3,1 servers running ESXi 6.0.0U2.I know this setup has some quirks but I'm accustomed to them. The other 32-bit VM was just set up a couple days ago, and was working until I edited the VM settings to increase the amount of RAM, and now no matter what I do, including changing the amount of RAM back, it kernel panics at boot.I have been managing ESXi using the Windows VMware vSphere Client version 6.0.0U2 running in wine on OS X El Capitan. The top line of the panic reads:Panic(cpu 0 caller 0x563ebd): "Unable to find driver for this platform: 32-bit VMs are configured with OS "Apple Mac OS X 10.6 32-bit" and the "monitor_control.disable_longmode" vmx option set to "true".One 32-bit VM was working fine for a week or two, until I edited the VM settings to increase the amount of VRAM, and now no matter what I do, including changing the amount of VRAM back, it kernel panics at boot. I don't know offhand whether newer versions of ESXi might still function correctly on the Xserve3,1 despite the lack of certification.I'm curious about your use of the "monitor_control.disable_longmode" option. (ESXi 5.5p07 and newer contain a fix for the spurious warning message you encountered.) As you've found, though, we no longer certified ESXi after version 5.0 on the Xserve3,1, which puts you in a bit of a bind, for which I don't have a ready solution. That spurious "more than one processor core" warning should only occur with 10.9.x and newer, but 10.9.x is only supported on ESXi 5.5U3 and newer. You are stuck between unsupported versions here. Thankfully, VMs don't need to strictly correspond with physical Mac configurations that Apple has manufactured, but the greater the difference, the more likelihood of running into some odd problem as a result.You might need to set bios.bootDelay = "5000" in the VM's configuration in order to have sufficient time to hold Shift to force OS X to boot in safe mode.I realize the last supported version of ESXi for the Xserve is 5.0.0, but 5.0.0 has some bugs, including a dialog box in vSphere Client that must be dismissed any time a VM using a recent version of macOS that is configured with more than one core is started or restartedHmmm. I could create a new virtual hard disk, install a new copy of the OS, and migrate the data from the old disk. The copy of Disk Utility on the Snow Leopard Server install DVD says the virtual hard disk appears to be fine. But I don't know why that would have happened or what to do about it. (Snow Leopard is only distributed as a "universal" OS, containing both 32-bit and 64-bit code.) It was this discovery that led me to search this forum and find the "monitor_control.disable_longmode" option which worked, to the extent that "sysctl hw.cpu64bit_capable" then returned "0" and the VM seemed in all respects to be a 32-bit system.This VM is still able to boot from the Snow Leopard Server install DVD, which seems to support your idea that the virtual hard disk is corrupted somehow. Free malware cleaner for macWhen the processor is 64-bit capable, Mac OS X can run both 32-bit and 64-bit applications even on a 32-bit kernel, so masking off that capability should only be required if you want to prohibit the use of 64-bit applications, as far as I can tell. For 32-bit selections, it should include "RELEASE_I386", and for 64-bit selections, it should include "RELEASE_X86_64".Choosing the 32-bit kernel does not mask off the virtual processors' 64-bit capability. You can check the kernel architecture by running "uname -a" at the guest's Terminal. Which is to illustrate why I don't take compatibility lists too seriously.The choice of 32-bit versus 64-bit versions of OS X determines the Darwin kernel architecture that ends up running inside the virtual machine. Odder still, Mac OS X 10.7 (32-bit), which does not exist (10.7 and later requires a 64-bit Mac), is also on the compatibility list. Inexplicably, the far more prevalent Mac OS X 10.6 (64-bit) is not. Have you installed OS updates inside the virtual machine recently? Is there sufficient free disk space on the VM's boot volume? I have no idea whether disabling long mode could somehow trigger this problem (perhaps indirectly), so if there is no need to disable long mode, it might be worth leaving it enabled in future, even if only to collect another data point regarding the problem. OS X 10.8 dropped the 32-bit kernel entirely, so it's only represented by the one entry in the guest OS selection (and the Compatibility Guide).It looks like your failing virtual machine has a corrupted (or otherwise non-functional) kernelcache on its boot volume. Again, using the "uname -a" command inside an OS X 10.7 guest should show a difference between the 32-bit and 64-bit guest OS selections. It's possible to force the use of the 32-bit kernel (even on a physical Mac) by holding down the "3" and "2" keys simultaneously when powering on the Mac â before the startup chime sounds. It includes a 32-bit kernel for compatibility with hardware for which only a 32-bit driver existed.
0 Comments
Leave a Reply. |
AuthorDale ArchivesCategories |