-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Having some trouble getting the VM to recognize hard drive... #2
Comments
That is unfortunately the part which is failure-prone and so far I have been unable to find a way to make it stable. Placing the disk on an IDE controller might help. In any case, once you manage to boot the DVD image, enter Disk Utility immediately after choosing the language. Apparently if you go |
Well, I had success on one occasion. I installed this MacOS VDI disk driver https://www.paragon-software.com/home/vd-mounter-mac-free/, which loaded and initialized the VDI disk. I then attached it as the only device to an IDE controller and one time - it worked. It loaded, I installed the system onto the disk, and rebooted with hope -- but argh -- will not find that disk again. In a real Mac, I'd hold down the option key while booting to bless a certain disk. I wonder if it's some setting like that in the PRAM.... it there a way to reset the PRAM in this VM? |
IIUC on virtualbox the nvram is actually volatile (if you want to set bootargs, it is possible to do so through the EFI settings) so I would expect the same for the PRAM. The good news is that (in my experience) after completing the setup, the boot becomes more reliable. This has probably something to do with the timing of some operations and caching the kernel modules seems to affect it. |
Could you try performing a verbose safe boot? It should be possible to set it up by running
The boot will be slower, but it might provide more details about what is going on. |
Well - weirdly, when I'm having trouble getting it to recognize the hard drive, it seems to work more reliably if I turn on screen recording. I know- makes no sense. Might be coincidence. It works! I reinstalled a stock version of TigerVM strictly following your instructions, and although I had trouble getting it to load the hard drive again, with the screen recording trick, it loaded the hard disk. Then I turned screen recording off. I'm on a fast-ish MacPro 5,1 with SSD drives, if that matters at all. I uploaded a webm recording of the failed load, and then the successful one -- probably useless, but perhaps you might see something in it. |
I believe that the hard drive issue might be related to some kind of race condition. I will add a note about the need to open Disk Utility immediately after the language selection (it is something I tripped into several times while trying to figure out the process). |
Looks like there are a number of examples of this issue with MacOS guests, so it's not just this project. https://forums.virtualbox.org/search.php?keywords=Still+waiting+for+root+device&sid=9d9961952b4ed8abe161c360c53d2f37 |
Yes, that seems to be one of the most fragile phases of the boot sequence :( Side note: I added the warning about the need to run "Disk Utility" immediately in e5e89a1#diff-04c6e90faac2675aa89e2176d2eec7d8R84. |
In some cases, the
will set your root device to Instead of going with a trial-and-error approach, one can easily determine the partition Y with
In fact, the Tiger server boot image I used for the guide had the boot partition would require For "whole disk" images one would use no partition number, i.e. just |
Been at this about an hour - but nothing I do seems to get the Tiger VM to recognize the hard disk. It sometimes blocks at 'Still waiting for root device' - resetting it once or twice does then boot from the DVD image, though Disk Utility won't see the drive to format it.
Tried IDE, SCSI, different SATA controllers, different disk formats, but it just won't seem to accept the hard drive....at least so far. Hmmm...
The text was updated successfully, but these errors were encountered: