NOTE
Install OSX 10.13
1) I started from the Mojave Installer, downloaded from Applestore.
2) I have built an installation ISO file ( I have created the dmg with hdutil, then I have mounted it with hdiutil attach, then I have sudo createinstallmedia... at the and I have the .iso)
3) I have created a virtual box, with a 35G hard drive .vdi and also an optical disk, on controller SATA. On this optical disk I have connected my .iso image of the installer.
4) I have set the virtual box memory to 4G, disk memory to 128, removed the floppy, set 2 processors. I have also loaded the virtual box extended pack. I set USB3 in the ports, otherwise the mouse and keyboard were not working). Now mouse and keyboards are working![Image Image](https://www.macdigger.ru/storage/app/media/uploads/2010/07/SnowLeopardinVirtualBox01.jpg)
5) I have started the virtual box. I enter in a screen where I can select install or disk utility
6) I selected disk utility and I select EDIT/NEW on the virtual box disk. I use HFS+, but I tried also with APSF. No difference.
7) After disk utility I start the installation on the new disk, that now is properly recognized.
8) At the end of the process the system reboots but instead of proceeding it goes back to the same window for selection of disk util or installation. This means that it has rebooted from the same cdrom image and not from the hard disk.
9) I select Restart from the apple menu and I intercept the restart by Fn F12. In this way I enter a screen where I select the Boot Manteinance Manager.
10) On this page I select BootFromFile, and then select files down to the boot.efi.
11) I do continue
12) The second part of macOS installation now proceeds. It is longer than the 1st part but everything seems to go ahead properly.
13) At the end of this second part the system reboots but still the reboot is done on the CDROM. Here is the problem. I were expecting having a reboot from the new macOS installed on the hard disk. But instead it seems that the hard disk is no bootable.
14) Even if I remove the cdrom from the virtual box setting, I cannot boot. In this case, as there is no more boot disk ( the virtualbox hard disk is not recognized as a boot drive) it starts the EFI shell.
15) I exit from the EFI shell and I enter the boot manager, but now there is no .efi file to boot from.
16) If I set back the image of the cdrom and open the disk utilities, doing get_info on the hard disk I see that the hard disk is not set as bootable.
17) I tried also to select the hard disk as a starting disk, keeping both the cdrom image and the hard disk. At the startup it logs Boot Failed MACOS X, and then goes ahead with the boot from the CDROM.
In summary:
I think to have done all the proper steps.
I had the installation of the macOS both in phase1 and phase 2
At the end, anyway I end up by having a virtual hard disk that is not considered as bootable.
Everything is coherent to confirm this.
But basically I think to have done the proper installation.
Here I am stuck. No more ideas.
All the discussions I have found are focused on the preparation of the ISO installer and on the phase 2 of the installation.
On the other hand in my case the problem is AFTER the phase2 of the installation.
Thanks
Open it up and click the “New” button. Name your Virtual Machine “High Sierra,” and choose “Mac OS X” for the operating system and “Mac OS X (64-bit)” for the version (as of this writing, “macOS High Sierra” is not offered, but that’s fine.) Continue through the process. Which would seem to explicitly permit running Mac OS X 10.7 (Lion) non-server version as a guest under VirtualBox provided the VirtualBox host is also running Mac OS X. Attempts to boot the 10.7 installer under VirtualBox 4.1.0 running on a Mac OS X system that is supported by Lion results in a.
: The instructions to create an ISO from any OSX Install application are covered in another article.Install OSX 10.13
- Create a new VM with the 10.13 template. Accept the defaults, with the exception of RAM (at least 3 GB), number of vCPUs (at least 2) and amount of HD (according to your needs, no less than 10 GB). Also make sure that USB3 controller is selected under the Ports » USB. Choose the newly created ISO as your boot medium.
NOTE: Do NOT designate your virtual HD as an 'SSD'. The installation WILL fail if you do that, because the OSX installer will convert the filesystem to APFS, something that the VirtualBox EFI can not handle. - Start the VM. It may seem that the installation stalls but don't shut the VM, be patient. Specifically, right before you switch to the graphics with the Apple logo and the progress bar, you'll get stuck at the point where the OSX ≥ 10.12.4 gets stuck:
- After selecting the language, open 'Disk Utility'. For reasons that only Apple engineers understand, you will *not* see your hard drive! Instead you'll see a bunch of partitions that are of no interest to you whatsoever (see NOTE below). On the top-left side, click on the 'View' drop-down and select 'Show All Devices'. Now you'll see your 'VBOX HARDDISK Medium'. Select it and choose 'Erase' from the toolbar. Leave the defaults (HFS+J/GUID), except maybe the name, choose anything you like. Quit 'Disk Utility' once done.
NOTE: This 'glitch' has been fixed with 10.13.2. Now the hard disk shows properly when Disk Utility is opened. - Select 'Install macOS'. Continue and agree to the license. This will start a phase where the actual installer is copied to the Recovery Partition of the hard disk that you selected. That part is rather quick, lasting less than a couple of minutes on an SSD drive. After that your VM reboots. But, you won't re-boot into the OSX installation phase, you'll restart the whole installation again from scratch! Houston, we have a problem!!! If you're observant, you'll notice a quick message coming up, right before the VM boots again from the ISO to restart the whole installation process:
- Apple (another wise move) has modified the way that it reads/treats the different partitions in the EFI, something that currently VirtualBox cannot handle (as of 5.2.2). But, there is a solution. Once you find yourself up and running, right after the language selection step, shut down the VM and eject the 10.13 ISO that you booted from. Then boot the VM again. You get dropped in the EFI Shell.
- You need to keep resetting the VM (HostKey+R) and press any key until you get into the EFI menu screen. If you don't succeed, and you end up in the EFI shell, enter 'exit'. That will you get to the EFI menu, shown below:
- Select the 'Boot Maintenance Manager' option, then 'Boot from File'. Now, you should have two options. The first one is your normal Boot partition, but this is not yet working, because you haven't yet installed 10.13. This is where the VM should be booting up from normally, and this is why it fails to boot. The second partition however is your Recovery partition. This is the one you should boot from to do the installation. This could be also used to do a re-installation of 10.13, just like on a real system, should the need arise.
- BootFromFile.png (48.02 KiB) Viewed 58207 times
- Choose the second option, then '<macOS Install Data>', then 'Locked Files', then 'Boot Files', and finally 'boot.efi' and let the games begin!
- That second part of the installation is where 10.13 actually gets installed. This is going to take substantially more time, about 20-30 min with the VM consuming every available CPU cycle. The VM will reboot a couple of times but you should be all set.
1) I started from the Mojave Installer, downloaded from Applestore.
![Create Create](https://cdn.appstorm.net/mac.appstorm.net/files/2009/02/03_4_guest_additions-620x465.jpg)
3) I have created a virtual box, with a 35G hard drive .vdi and also an optical disk, on controller SATA. On this optical disk I have connected my .iso image of the installer.
4) I have set the virtual box memory to 4G, disk memory to 128, removed the floppy, set 2 processors. I have also loaded the virtual box extended pack. I set USB3 in the ports, otherwise the mouse and keyboard were not working). Now mouse and keyboards are working
![Image Image](https://www.macdigger.ru/storage/app/media/uploads/2010/07/SnowLeopardinVirtualBox01.jpg)
5) I have started the virtual box. I enter in a screen where I can select install or disk utility
6) I selected disk utility and I select EDIT/NEW on the virtual box disk. I use HFS+, but I tried also with APSF. No difference.
7) After disk utility I start the installation on the new disk, that now is properly recognized.
8) At the end of the process the system reboots but instead of proceeding it goes back to the same window for selection of disk util or installation. This means that it has rebooted from the same cdrom image and not from the hard disk.
9) I select Restart from the apple menu and I intercept the restart by Fn F12. In this way I enter a screen where I select the Boot Manteinance Manager.
10) On this page I select BootFromFile, and then select files down to the boot.efi.
11) I do continue
12) The second part of macOS installation now proceeds. It is longer than the 1st part but everything seems to go ahead properly.
13) At the end of this second part the system reboots but still the reboot is done on the CDROM. Here is the problem. I were expecting having a reboot from the new macOS installed on the hard disk. But instead it seems that the hard disk is no bootable.
14) Even if I remove the cdrom from the virtual box setting, I cannot boot. In this case, as there is no more boot disk ( the virtualbox hard disk is not recognized as a boot drive) it starts the EFI shell.
15) I exit from the EFI shell and I enter the boot manager, but now there is no .efi file to boot from.
16) If I set back the image of the cdrom and open the disk utilities, doing get_info on the hard disk I see that the hard disk is not set as bootable.
17) I tried also to select the hard disk as a starting disk, keeping both the cdrom image and the hard disk. At the startup it logs Boot Failed MACOS X, and then goes ahead with the boot from the CDROM.
In summary:
I think to have done all the proper steps.
I had the installation of the macOS both in phase1 and phase 2
At the end, anyway I end up by having a virtual hard disk that is not considered as bootable.
Everything is coherent to confirm this.
But basically I think to have done the proper installation.
Here I am stuck. No more ideas.
All the discussions I have found are focused on the preparation of the ISO installer and on the phase 2 of the installation.
On the other hand in my case the problem is AFTER the phase2 of the installation.
Thanks