Newbox Mac OS

You can run MacOS in Virtualbox. Because? Because.

• Newbox Mac Os Downloads
• New Box Mac Os Catalina
• New Box Mac Os X
• New Mac Os Release 2020
• Newbox Mac Os X

In the pursuit of Hackintosh, you need a Mac. That’s well and great, but I didn’t want to screw around with my partner’s Macbook. So what if you want to sandbox something? Virtualbox!

I had no expectations that this was going to work. OS X has always been runnable in Virtualbox for a while, but the performance has normally been lacklustre. While it’s not exactly daily-driver level, the performance in Virtualbox wasn’t too bad!

In the sidebar, click “Send Birthday Greetings” and drag it to the work area. This will add a new box with birthday-specific images and an area to write a message. Select a specific image, or request a random image for each recipient, and then write a birthday greeting in the box presented. Pop open Virtualbox, and Create a new Virtual Machine. Name this MacOS Mojave, and set it to Mac OS X (64-bit). Set the RAM to 4096 MB (or higher if you can achieve it!). When creating the disk, you can use either format versions. Now type the name as “macOS Mojave“, type of OS as Mac OS X and the version of OS as Mac OS X (64-bit). And then Click on Next. Memory Size (RAM) Now select the amount of RAM to be allocated to the virtual machine. And to run macOS on Virtualbox, the minimum recommended RAM size is 2048Mb. Virtualbox has the option for a MacOS virtual machine in it’s New VM dialog, but we will need to make further adjustments to make it truly Mac-ready. Pop open Virtualbox, and Create a new Virtual Machine. Name this MacOS Mojave, and set it to Mac OS X (64-bit). 1GB = 1 billion bytes and 1TB = 1 trillion bytes; actual formatted capacity less. Actual rating of 99.8 watt-hours. Testing conducted by Apple in October 2019 using preproduction 2.3GHz 8-core Intel Core i9-based 16-inch MacBook Pro systems with 16GB of RAM and 1TB SSD.

The macOS Virtualbox option is designed for genuine Apple hardware. You will not get community support from Virtualbox if you have trouble with this process, as it’s against Apple ToS.

VMware more your jam? We’ve got this working in there too.

🤔️ What do I need?

You need a donor Mac to start this process. You will not need access to it permanently, but just during the process of creating an ISO for your VM to setup with. Else, you need:

• A Mac to create an ISO with.
• MacOS Mojave installer from the Mac App Store.
• Virtualbox (Windows, Linux or MacOS).
  • Virtualbox Extension Pack is required.
• At least 4GB of RAM (8GB or more recommended).
• 40GB of free disk space (more preferred).
• 2 core CPU or more.

This guide will discuss installing MacOS Mojave, however installation process should be similar for all MacOS versions.

⚠️ At the time of writing, Virtualbox and Hyper-V cannot co-exist on Windows. MacOS is also not installable on Hyper-V. I use Linux in my screenshots as I use Docker on Windows. This also includes Windows Subsystem for Linux, which tripped me up from installing.

💿 Creating the ISO

Virtualbox installs generally prefer to use an ISO file, which unfortunately will require some handiwork to get a hold of. Persevere and you will get there!

On the MacOS machine, download the Mojave installer. Don’t worry about actually running this application, as we’re going to use some terminal magic to build the ISO from the package.

This process is not affected by MacOS Installer expiry.If your MacOS installer has expired, you can continue with this guide.

Once the package has been downloaded, pop open Terminal (Utilities folder in Launcher), and run the following commands:

hdiutil create -o /tmp/Mojave.cdr -size 8000m -layout SPUD -fs JHFS+

This will create a virtual ‘disc’ stored in your temporary directory. This is what we’ll stuff the Mojave installation stuff into.

hdiutil attach /tmp/Mojave.cdr.dmg -noverify -nobrowse -mountpoint /Volumes/installer_goes_here

Now MacOS can ‘see’ your disc as an actual disc, ready for writing to!

asr restore -source /Applications/Install macOS Mojave.app/Contents/SharedSupport/BaseSystem.dmg -target /Volumes/installer_goes_here -noprompt -noverify -erase

We’re now grabbing the installation DMG from within the updater package, and storing it within the disc image. This will rename the disc image, so don’t panic that ‘installer_goes_here’ has vanished.

Now, detach the image from our MacOS. You can just eject it like regular DMGs. If not, run the command:

hdiutil detach /Volumes/OS X Base System

(it may change since OS X is legacy. To check, run ls /Volumes and see if it’s there, renamed).

Now for the final process, let’s convert our CDR image to an ISO!

Newbox Mac Os Downloads

hdiutil convert /tmp/Mojave.cdr.dmg -format UDTO -o ~/Desktop/Mojave.iso

You should now have a file on the Mac desktop called ‘Mojave.iso’. Congratulations, you have your installation disc! Copy this over to where your Virtualbox is setup. The Mac is no longer needed at this point.

🛠️ Setting up Virtualbox

⚠️ Before continuing, install the Virtualbox Extension Pack, if you haven’t already. This comes with a special USB 3 driver that without, the Mac simply won’t see USB devices.

Virtualbox has the option for a MacOS virtual machine in it’s New VM dialog, but we will need to make further adjustments to make it truly Mac-ready.

Pop open Virtualbox, and Create a new Virtual Machine. Name this MacOS Mojave, and set it to Mac OS X (64-bit).

Set the RAM to 4096 MB (or higher if you can achieve it!).

When creating the disk, you can use either format versions. Dynamic will not immediately take up the storage size you chose, whereas Static immediately reserves the chosen size for the VM. The latter is slightly better for performance.

Now you should have a new, primed MacOS machine. But you will need to run some commands now. This can be hit-and-miss, and may require some Google-fu. The following works for my AMD FX computer:

Windows? Change VBoxManage to 'C:Program FilesOracleVirtualBoxVBoxManage.exe' (if you didn’t change your Virtualbox install location).

The above does the following, in order of command:

• Sets a known CPU ID set that MacOS will recognise.
• Especially for AMD machines, changes what MacOS sees as your processor to something it supports.
• Tells MacOS you’re installing Mojave onto a mid-2010 iMac. You can change this to your preference.
• These two specify a fake DMI, typically found in Apple PCs.
• A device key to pass system checks.

Before starting the VM, open the VM settings and make the following changes:

• System > Processor > Processor(s) is 2 or more.
• System > Acceleration > uncheck Enable Nested Paging.
• Display > Screen > Video Memory is 128MB.
• USB > USB 3.0 Controller.
  • If greyed/not there, you did not install additions.

With all that done, we’re ready to start the VM!

You should be greeted with the following screen:

Click on the folder icon, and find your ISO created on the Mac before, then click Start.

And wait. yes, this process takes a long time. If your installation stops, try googling the last output message to see if there is a community fix, or post below… Otherwise, this is generally a slow process.

If all has gone well, you should be greeted by the MacOS installer language selection. If so, you’re almost there! On the top menu, open Utilities > Disk Utility.

There should be a disk named VBOX HARDDISK or similar. This is the VDI you created during the setup process, and not your actual hard drive. So go ahead and full-erase this disk, with Mac OS Extended (Journaled) and GUID Partition Map.

Once the disk formatting has completed, close it down. You should now be able to start the installation!

Once this is complete and you filled all the required details in, congratulations! You’re running MacOS Mojave within Virtualbox!

❓ What works?

✔️ Does

• Screen (No 3D).
• Regular input methods (mouse sharing).
• Networking.
• USB devices.
• Mac App Store.

At the end of the day it’s still a virtual machine, and a technically unsupported one at that. However, considering the matter it’s still impressive how Virtualbox can cope with MacOS.

Files can be shared using typical Windows share features. If you share a folder on your network from your host machine, your Mac VM should be able to connect to it.

🌟 Special Thanks

This required a lot of Googling, and these are the people who saved me at the end of the process!

• This How-to Geek article, that started this whole process. They have a much better step-by-step guide on this!
• Forchia on Reddit for a different instruction set.
• miranhasan on Reddit for AMD processors.
• kvotheV on Reddit for disabling nested paging.

🐛 Troubleshooting

New Box Mac Os Catalina

This is a difficult one, and will require investigation. I checked the logs as the error message said, and discovered:

HM: HMR3Init: Attempting fall back to NEM: AMD-V is not available

Obviously, check if this is enabled. If you’re on a legacy BIOS computer, it’s a straightfoward scan for AMD-V/VT-x in your settings. If it’s UEFI, you’re gonna have to Google it.

Strangely, on my machine it was enabled. Supposedly Virtualbox and Hyper-V can run side-by-side, so at this point I decided to remove Hyper-V, to see if that would improve. It didn’t, but I forgot something. For this to work, you must turn off Windows Subsystem for Linux!

I completely forgot that WSL uses Hyper-V, and apparently still does when it’s disabled. Unfortunately, it would seem (for me at least) you need to trade it off for macOS in Virtualbox.

I will retest this when WSL2 is launched.

I'm currently using OS9.2.2 on my powerbook and it's time to upgrade. I'm putting in extra RAM so I'll have 640M with 7 gigs hard-drive space available. Does anyone know of any complications re loading on OSX - should I wipe the hard drive and do a clean install??
Thanks, davidac

Try asking your question here:
http://forums.macosxhints.com/

I'd be careful trying this if you aren't always going to be connected to the main server.

I was thinking about the same problem, as I would like to have my TiBook do this while on the same LAN as my Cube, but then I would have problems when I took it mobile. Writing a script to store some backup mobile prefs and switch between them would be trivial, but the only hangup I had was how to create a hook so the script would run everytime I go mobile/come home. My LAN is an Airport network, so I figured that based off the status of the network connection I could determine which settings to use. Does anyone know how to do this, either via Applescript or a shell script?

Panther will have much improved abilities in this regard. The idea of caching stuff (including the authentication stuff) for when you go mobile has been a MAJOR sticking point to getting a managed desktop useable. As I have heard it described in Panther you could in theory set up your Mac with a 'roaming profile' and never rely on the presence of the server again. The credentials and etc. are cached indefinitely. But, on the other hand if the server is present when the user is connected, the stuff will automatically synchronize. So admittedly this is a server based comment to a serverless 'hint', but it illustrates how essential the presence of a server box is becoming in OSX. Fortunately Apple is not milking it's customers as badly for it's server products as Microsloth. In fact it's practically free with the purchase of an XServe.
---
Mark Moorcroft
ELORET Corp. - NASA/Ames RC
Sys. Admin.

As well, watch that if you end up using both systems at the same time you could corrupt your data files when two processes fight over updating them...

The best way is via an applescript that contains your name and password, as well as the path to the share.
However, a seamless mount is not really needed. Making the mount point a login item that prompts for a password is enough. The important thing is that you don't try and use this system until the mount has been loaded and the links work.

New Box Mac Os X

Isn't this procedure just using his main Mac as a server; there's certainly a server component in this hint. Wouldn't the title be more correct as 'Roaming Profiles without OSX Server software.' Or maybe I'm just missing something...
--> John

I'm trying to do something similar with my iPod. I work in two places (home and office) and want to use my iPod as my document universe that follows me around whereever I go.
So I mount my iPod on the desktop on both machines. Then I sync my Documents folder using IMSafe - that works great. Presumably i can using iSync to synchronize iCal and Address Books across my two computers.
For Safari, Firebird, Thunderbird and Fire, I did this:
- at home: move the data files for each of these applications (mostly in ~/Library somewhere) to my Documents folder and use ln -s to create a symbolic link from their original home to their new localtion.
- when leaving home: run IMSafe to sync my Documents folder onto the iPod
- at work: mount the iPod on the desktop, then have a symbolic link from the original location to poin to the location on my iPod
This works for iCal but not for Fire, Safari, Firebird or Thunderbird. I'm using the ln -s approach, not the Make Alias method.
I wonder if this is some permission problem. Any suggestions?

I have something similar setup with one addition. It is not a totally foolproof setup, but works well and any errors (my screw ups) are easily corrected.
I do much the same. Store Mail.app files, etc. on a remote volume on my 'basement server'. When at my desktop or on my TiBook at home, everything is up to date since all is on the same remote volume.
The additional thing I have set up is a Disk Image with the same name as the volume on my server (I append the host computer's name during sync operations). When on the road I mount the disk image, which provides the correct path names. While away and using the disk image, all works the same, but it is a local volume instead of a remote one.
If I screw up and launch Mail.app while neither the remote or disk image is mounted, OS X simply creates a folder by the name of the missing volume in the invisible folder /Volumes/ (which I keep an alias to in my Home folder). Just quit the app, delete the bogus folder in /Volumes/, and all is well.
Rob

New Mac Os Release 2020

For that why dont you just make a sym link to your whole home directory?
ln -s /Volumes/main_mac/Users/userName /Users/userName

Newbox Mac Os X

the one reason that I would not is the Library folder. Different apps on different machine etc. etc.
---
----------------------------------------
Ian Sheridan mailto:ians@vminc.net
----------------------------------------

Newbox Mac OS