- Install Dmg File In Virtualbox Windows
- Install Dmg File In Virtualbox Download
- Install Dmg File In Virtualbox Windows 7
- Install Dmg File In Virtualbox Windows 10
- Install Dmg File In Virtualbox
Scroll down to “Update and Solution” to see how to get this to work.
Step 3: Install & Update VirtualBox Extension. This step is not 100% necessary but it’s highly recommended to do this step because macOS Catalina might not be compatible with VirtualBox and for this reason, it might cause problems during the installation. I've used it to create a dmg and I'm trying to use the dmg with virtualbox. I converted the dmg to a vdi file like so: VBoxManage convertdd /Desktop/osx-10.10.1-14B25.hfs.dmg auto.vdi. Then I created a new VM in VirtualBox and chose the vdi as the drive. And disabled EFI. But VirtualBox says FATAL: No bootable medium found! Jun 18, 2019 Save the DMG installation VirtualBox image (VirtualBox-6.0.8-130520-OSX.dmg in this case) to the custom folder. Shut down all VMs and close the window of your old VirtualBox version. Open the DMG image and double click on the VirtualBox.pkg icon to run the VirtualBox package installer.
Apple recently released new installers for Mac OS X/OS X/mac OS to deal with expired certificates:
Three of the six are links to the Mac App Store:
The other three are URLs to download DMGs:
- macOS Sierra – InstallOS.dmg
- OS X El Capitan – InstallMacOSX.dmg
- OS X Yosemite – InstallMacOSX.dmg
Today I tried (and failed) to create a new Virtual Machine in either Parallels or VMware Fusion using one of these DMGs, specifically, the El Capitan one.
I will explain what I did, and where I got stuck, in the hopes that someone else might figure out what I did wrong and point me in the right direction.
Download the DMG
Apple has created three DMGs for Yosemite, El Capitan, and Sierra, but couldn’t be bothered to give them useful names, so Yosemite and El Capitan are called ‘InstallMacOSX.dmg’ and Sierra is ‘InstallOS.dmg’.
Likewise the DMGs aren’t named usefully when you mount them either, so make sure you name the DMGs well when you download them to avoid confusion. Here’s how to download it and rename it at the same time
Mount the DMG
Open the ‘~/Downloads/InstallElCapitan.dmg’
That will leave you with
“/Volumes/Install OS X/InstallMacOSX.pkg”
Extract the App
Don’t try to install from that .pkg file, it probably won’t work unless the Mac you’re using is capable of running El Capitan:
Instead, open it with Suspicious Package which will let you examine the contents of the .pkg file, as shown here:
Note the area in the red box. Obviously that’s not the full installer, despite the .dmg being over 6 GB. But let’s export it anyway:
Save it to /Applications/ (or wherever you prefer, but that’s where I’ll assume it is for the rest of these instructions).
Don’t eject “/Volumes/Install OS X/InstallMacOSX.pkg” yet, we still need to get the actual .dmg from it.
Get the other DMG
Download The Archive Browser if you don’t already have it (it’s free!) and use it to open “/Volumes/Install OS X/InstallMacOSX.pkg”.
It will look like this:
Click on the triangle to the left of “InstallMaxOSX.pkg” to reveal its contents, and select the “InstallESD.dmg” file from it.
Once it is selected, choose “Extract Selected” from the bottom-left. Save it to ~/Downloads/ (it won’t be staying there long).
Ok, this part could be confusing…
When The Archive Browser exports the file, it will not just export the “InstallESD.dmg” file. First it creates a folder “InstallMacOSX” and then it created “InstallMacOSX.pkg” inside that folder, and the “InstallESD.dmg” file is put inside the .pkg… but you can’t see it, because the .pkg file won’t let you open it.
That’s OK, because we’re going to use Terminal.app to move the file into place anyway.
First we need to create a directory inside the ‘Install OS X El Capitan.app’ which we previously saved to /Applications/. We’re going to use the same folder for two commands and we want to make sure we get it exactly right both times, so we’ll make it a variable:
Then use the variable with mkdir to create the folder:
and then we need to move the “InstallESD.dmg” file into that folder
Note: you probably want to trash the ‘~/Downloads/InstallMacOSX/InstallMacOSX.pkg’ (and its parent folder) now that it is empty, to avoid confusion later
Now if you look at the ‘Install OS X El Capitan.app’ in the Finder, it should show itself as 6.21 GB:
So close, and yet…
VMWare was willing to start trying to make a virtual machine using the app, but it failed when it came to the actual installation part:
I don’t know what to try next. Parallels would not use either the ‘Install OS X El Capitan.app’ or the ‘InstallESD.dmg’ to try to create a new virtual machine.
Update and Solution
I posted a question on the VMware Fusion support forum asking how to do this, and someone came up with a very clever solution, which I will replicate here in case others are interested. The idea is simple, but I never would have thought of it.
- Create a virtual machine of any version of macOS, even the current version that you are using on your Mac.
Inside the VM, download the .dmg (see below) and mount it.
Launch the .pkg inside the .dmg.
The .pkg seems to understand that it is inside a VM, and will install the app, which it would not do outside of the VM. Note that the Installer.app says that it will only take a few megabytes, but that is incorrect.
Find the “Install OS X El Capitan.app” (or whatever the app name is) in the /Applications/ folder inside the VM. It should be over 6 GB in size.
Copy the “Install….app” from the VM out to your actual Mac.
Create a new VM using the “Install….app” from the /Applications/ folder on your Mac.
Step #4 is the part that I never would have guessed. The .pkg would not install the app outside of a VM, but will install it inside of a VM.
This worked perfectly with the El Capitan .dmg file, and I’m currently doing the same with Yosemite and Sierra. Then I’ll try the older versions of Mac OS X from old installers that I have from before they disappeared from Apple’s servers.
Update 2
Turns out that Rich Trouton wrote about this technique back in early 2017:
But I wasn’t working with VMs at the time, so I must not not stored that in my long-term memory.
Update 3
I had saved the older installers for Lion, Mountain Lion, and Mavericks, which are no longer available for download.
Each of them still installed as a VM. Apparently they were not signed with the certificates that expired.
Older versions of Mac OS X (10.6.8 and before) are not available to virtualize.
Scroll down to “Update and Solution” to see how to get this to work.
Apple recently released new installers for Mac OS X/OS X/mac OS to deal with expired certificates:
Three of the six are links to the Mac App Store:
The other three are URLs to download DMGs:
- macOS Sierra – InstallOS.dmg
- OS X El Capitan – InstallMacOSX.dmg
- OS X Yosemite – InstallMacOSX.dmg
Today I tried (and failed) to create a new Virtual Machine in either Parallels or VMware Fusion using one of these DMGs, specifically, the El Capitan one.
I will explain what I did, and where I got stuck, in the hopes that someone else might figure out what I did wrong and point me in the right direction.
Download the DMG
Apple has created three DMGs for Yosemite, El Capitan, and Sierra, but couldn’t be bothered to give them useful names, so Yosemite and El Capitan are called ‘InstallMacOSX.dmg’ and Sierra is ‘InstallOS.dmg’.
Likewise the DMGs aren’t named usefully when you mount them either, so make sure you name the DMGs well when you download them to avoid confusion. Here’s how to download it and rename it at the same time
Install Dmg File In Virtualbox Windows
Mount the DMG
Open the ‘~/Downloads/InstallElCapitan.dmg’
That will leave you with
“/Volumes/Install OS X/InstallMacOSX.pkg”
Extract the App
Don’t try to install from that .pkg file, it probably won’t work unless the Mac you’re using is capable of running El Capitan:
Instead, open it with Suspicious Package which will let you examine the contents of the .pkg file, as shown here:
Note the area in the red box. Obviously that’s not the full installer, despite the .dmg being over 6 GB. But let’s export it anyway:
Save it to /Applications/ (or wherever you prefer, but that’s where I’ll assume it is for the rest of these instructions).
Don’t eject “/Volumes/Install OS X/InstallMacOSX.pkg” yet, we still need to get the actual .dmg from it.
Get the other DMG
Download The Archive Browser if you don’t already have it (it’s free!) and use it to open “/Volumes/Install OS X/InstallMacOSX.pkg”.
It will look like this:
Click on the triangle to the left of “InstallMaxOSX.pkg” to reveal its contents, and select the “InstallESD.dmg” file from it.
Once it is selected, choose “Extract Selected” from the bottom-left. Save it to ~/Downloads/ (it won’t be staying there long).
Ok, this part could be confusing…
When The Archive Browser exports the file, it will not just export the “InstallESD.dmg” file. First it creates a folder “InstallMacOSX” and then it created “InstallMacOSX.pkg” inside that folder, and the “InstallESD.dmg” file is put inside the .pkg… but you can’t see it, because the .pkg file won’t let you open it.
That’s OK, because we’re going to use Terminal.app to move the file into place anyway.
First we need to create a directory inside the ‘Install OS X El Capitan.app’ which we previously saved to /Applications/. We’re going to use the same folder for two commands and we want to make sure we get it exactly right both times, so we’ll make it a variable:
Then use the variable with mkdir to create the folder:
and then we need to move the “InstallESD.dmg” file into that folder
Note: you probably want to trash the ‘~/Downloads/InstallMacOSX/InstallMacOSX.pkg’ (and its parent folder) now that it is empty, to avoid confusion later
Now if you look at the ‘Install OS X El Capitan.app’ in the Finder, it should show itself as 6.21 GB:
Install Dmg File In Virtualbox Download
So close, and yet…
VMWare was willing to start trying to make a virtual machine using the app, but it failed when it came to the actual installation part:
Install Dmg File In Virtualbox Windows 7
I don’t know what to try next. Parallels would not use either the ‘Install OS X El Capitan.app’ or the ‘InstallESD.dmg’ to try to create a new virtual machine.
Update and Solution
I posted a question on the VMware Fusion support forum asking how to do this, and someone came up with a very clever solution, which I will replicate here in case others are interested. The idea is simple, but I never would have thought of it.
- Create a virtual machine of any version of macOS, even the current version that you are using on your Mac.
Inside the VM, download the .dmg (see below) and mount it.
Launch the .pkg inside the .dmg.
The .pkg seems to understand that it is inside a VM, and will install the app, which it would not do outside of the VM. Note that the Installer.app says that it will only take a few megabytes, but that is incorrect.
Find the “Install OS X El Capitan.app” (or whatever the app name is) in the /Applications/ folder inside the VM. It should be over 6 GB in size.
Copy the “Install….app” from the VM out to your actual Mac.
Create a new VM using the “Install….app” from the /Applications/ folder on your Mac.
Install Dmg File In Virtualbox Windows 10
Step #4 is the part that I never would have guessed. The .pkg would not install the app outside of a VM, but will install it inside of a VM.
This worked perfectly with the El Capitan .dmg file, and I’m currently doing the same with Yosemite and Sierra. Then I’ll try the older versions of Mac OS X from old installers that I have from before they disappeared from Apple’s servers.
Install Dmg File In Virtualbox
Update 2
Turns out that Rich Trouton wrote about this technique back in early 2017:
But I wasn’t working with VMs at the time, so I must not not stored that in my long-term memory.
Update 3
I had saved the older installers for Lion, Mountain Lion, and Mavericks, which are no longer available for download.
Each of them still installed as a VM. Apparently they were not signed with the certificates that expired.
Older versions of Mac OS X (10.6.8 and before) are not available to virtualize.