(That said, I suspect the problem is elsewhere, and the boot-uuid handling is correct. That might be worth trying, just to see if the native boot-uuid is somehow getting garbled. Rd=uuid boot-uuid=224959f4-8eee-4190-a8c5-d8a992daa778 (of course, you'd substitute your own boot-device's UUID for the one I used here). You can override the IORegistry boot-uuid with two boot-args: Waiting on IOProviderClassIOResourcesIOResourceMatchboot-uuid-media and Still waiting for root device usually mean that the root filesystem cannot be recognized, for any number of reasons. The fact that you only see it once suggests to me that the problem is elsewhere. If it's never found, it should iterate forever - mountAttempts doesn't get incremented within that loop, and absent a panic elsewhere, you should see Still waiting for root device messages repeated every 60 seconds.
VIRTUALBOX MAC OS X STILL WAITING FOR ROOT DEVICE MAC OS X
I have a copy of Mac OS X 10.6 Snow Leopard Server. I run pearpc with my config file and I get 'Still waiting for root device' over and over. From various websites and some created with on a linux box. What's interesting here is that the loop should only exit if the matching service is found. What does Still waiting for root device means It means that a driver/kext for the source from which you are booting is not detected properly by the mac operating system (USB kext not detected or loaded) Mac OS released prebuilt with the latest drivers that supports SATA out of. For example, a DMG image on the Mac OS X install disks created with the DiskUtility in Mac OS X itself will generate this message if you try to boot PearPC with it. so mountAttempts only gets incremented once every time IOFindBSDRoot() is called. If ((regEntry = IORegistryEntry::fromPath( "/chosen", gIODTPlane ))).