NOTE: The instructions to 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: IOConsoleUsers: gIOScreenLockState 3, hs 0, bs 0, now 0, sm 0x0. 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: Boot Failed. Mac OS X. 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.
Virtualbox lets you run Mac OSX within Windows by creating a virtual machine, which is a program that simulates a normal computer. Give your new virtual machine a name, and choose 'Mac OS X' for the OS Type. If your version of Virtualbox asks you to choose.
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. EFImenu.png (32.71 KiB) Viewed 27462 times. 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. Thank you the information but I'm not getting very far. I'm logged into the computer as a normal user. In terminal I logged in as the admin. I copied your script and created the.iso file.
I copied it to the /Shared folder and from there copied it onto the Desktop of the normal user. I created a new VM with RAM 8192, HD 50 and CPUs 2. (Also display 128).
I attached the.iso file to the first SATA CD and deleted the floppy option in the System:Motherboard pane. This should cause the ISO to be the boot medium?
Blank black screen. 1:06 I'm not seeing IOConsoleUsers: gIOScreenLockState 3, hs 0, bs 0, now 0, sm 0x0 or VBOX HARDDISK Medium in Disk Utilities Posts: 8 Joined: 25. Nov 2017, 06:25 Location: Colorado Primary OS: Mac OS X other VBox Version: OSE other Guest OSses: macOS High Sierra. ChipMcK, I imported your.vbox and changed only the VDI and the ISO (obviously).
It booted just fine. You have 1595 MB available, not a good sign if you want to dedicate 2048 MB. You have 2 CPUs, both of them assigned to the VM. Which it needs it BTW. I don't know what '/Volumes/MacCard-2' is, but if it's USB3, or not your local SSD you have to waaaaaaiiiiiiitttttt. You got stuck during the USB initialization phase. Try to switch to xHCI, aka USB3, although I highly doubt that this is the reason.
That was the last step, there is plenty of I/O after that which is what might slow you down. Keep the ActivityMonitor open at the Disk I/O tab to monitor what's going on Your MacBookAir is not that powerful to begin with. It will at the low end minimum side to run 10.13 standalone, imagine in a VM. Expect delays.
00:60 IEM: rdmsr(0x35) - #GP(0)Now this doesn't look good. IEM is the 'instruction interpreter' part of VirtualBox.
There is a chance that with your processor ([email protected]) VirtualBox doesn't know how to handle that instruction (rdmsr) at that stage. I don't think there's a lot you can do at this point, except either file a bug report, or wait until Monday till the developers get in.
One last thing to try. With the VM shutdown, open up Terminal and issue the command: VBoxManage modifyvm 'High Sierra' -cpu-profile 'Intel Core i7-6700K'That will force VirtualBox to present a different, older CPU than the one you have. It's worth a shot, it might work. But don't hold your breath.
@scocratis I issued the command VBoxManage modifyvm 'High Sierra' -cpu-profile 'Intel Core i7-6700K' and made some progress. I got as far as installing High Sierra from what looked like the Restore disk.
(Still nothing has shown up in Disk Utility). I'll attach some screen shots and logs. Thanks for your help, db PS, screen shots are too big. I'll try attaching to another message. Attachments logs and High Sierra.vbox (123.79 KiB) Downloaded 72 times Posts: 8 Joined: 25. Nov 2017, 06:25 Location: Colorado Primary OS: Mac OS X other VBox Version: OSE other Guest OSses: macOS High Sierra.
@socratis It worked!!! After multiple tries with different results I didn't recognize a key instruction. Open Disk Utilities means open Disk Utilities in the Guest VM Thanks, db I've adjusted your instructions slightly to highlight the bits I got lost on. Thanks for all your help. I'll include the adjusted text below.
My changes/suggestions in - a) Download 'Install macOS High Sierra.app' from Apple. By default it will be placed in the '/Applications' folder. when you cancel the install process the.app file won't be deleted. NOTE: The script will not work if you are a Standard user. You have to be an Administrator in order for the 'sudo' to work, since Standard users cannot sudo. If you are a Standard user, first do a 'su Administrator' before running the script.
If you login into the admin account the iso file will end on on the admin Desktop. You can move/copy this to the user account via the /Shared folder. Also note the size change in the first command. A) Create a new VM with the 10.13 template. Accept the defaults, with the exception of RAM 4096+, number of vCPUs 2+, amount of HD 40+, display memory 128.
Choose the newly created ISO as your boot medium. Quit VirtualBox and issue the command (iMac 27' 2017) VBoxManage modifyvm 'High Sierra' -cpu-profile 'Intel Core i7-6700K' from the terminal. B) Start the VM. It may seem that the installation stalls but don't shut the VM, be patient. Specifically, right before after 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: IOConsoleUsers: gIOScreenLockState 3, hs 0, bs 0, now 0, sm 0x0 I didn't notice this Posts: 8 Joined: 25.
Nov 2017, 06:25 Location: Colorado Primary OS: Mac OS X other VBox Version: OSE other Guest OSses: macOS High Sierra. Glad you got it going! Of course the instructions talk about the VM, once the installation has started. I added a 'Cancel the 10.13 installation'. Thanks for the tip, I thought that you didn't want to upgrade the host and you'd cancel out, that's why I didn't include it.
You have a huge, fast system. Not everyone does. You can increase the minimum offered from the template at will.
But let's keep the recipe as per the defaults. The -cpu-profile is a.very.
specific instruction that applies.only. to your system. It's a workaround until VirtualBox fixes it. Otherwise it's going to end up like every other outdated blog out there that proposes blindly the -cpuid modification. Not what you want. You didn't 'see' the message because you have a monster of a host and it flew over.
The message.is. there, trust me For me the most important lesson from your setup was the -cpu-profile and the fact that it made it work. Again, glad you're up and running!
@socratis I had tried a few things with various results so when I started to see the Recovery Partition window in the VM with the choice of Installing the System I went down the rabbit hole. B) I picked up some of the potential template increases from somewhere in my travels, maybe another thread on this forum even. One that seemed to be stressed was increasing the display memory to the max (128). I tried 4 CPUs but that stressed my machine a 'little' with the fans running hot so I've dropped back to 2 for now c) Well done with the -cpu-profile that made it work. D) There is a lot of 'stuff' on the screen.I trust you. My plan is to use the macOS guest to explore some debugging techniques (from a book - I'm just learning) which seems to require disabling System Integrity Protection.
As suggested in the book I plan to do much of this in the VirtualBox guest VM. Thanks again for you help. Your instructions worked as written (with the -cpu-profile addition for my machine). Posts: 8 Joined: 25. Nov 2017, 06:25 Location: Colorado Primary OS: Mac OS X other VBox Version: OSE other Guest OSses: macOS High Sierra.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |