Virtual Box Cpu Settings For Macos Average ratng: 8,1/10 4856 votes

Windows 10 is a great operating system. It has its quirks and annoyances, but which operating system doesn’t? Even if you’re beholden to Microsoft and Windows 10, you can still shop around.

Jan 28, 2017 C: Program Files Oracle VirtualBoxVBoxManage modifyvm 'BigSur' -–cpu-profile “Intel Core i7-6700K” Oracle VM VirtualBox Command Line Management Interface Version 6.1.10 (C) 2005-2020 Oracle Corporation. Oct 26, 2017  Select it, then click the big yellow “Settings” button. First, head to “System” in the left sidebar. On the Motherboard tab, make sure that “Floppy” is unchecked. Next head to the “Processor” tab, and make sure you have at least two CPUs allocated to the virtual machine. Jul 11, 2014 Virtualbox: This virtualization suite is free, and though it doesn’t offer official support for Mac OS X, it works well enough.; Mountain Lion bootable DVD: Unfortunately, the standard method for installing OS X Mountain Lion on PCs (which uses a paid copy of the Mountain Lion installer) doesn’t work with Virtualbox. Jul 05, 2017 Your computer’s CPU does all the work of running the virtual machine and its software, so the more CPU it can use, the better it will run. If you have a computer with a multi-core CPU, you can assign more cores to your virtual machine from its settings window.

What better way to do that than from the safe confines of your existing operating system with a virtual machine? This way, you can run macOS on Windows, which is perfect when you want to use Mac-only apps on Windows.

So, here’s how you install macOS in a virtual machine on Windows, making a virtual Hackintosh that lets you run Apple apps from your Windows machine.

What Files Do You Need to Create a macOS Virtual Machine on Windows 10?

Before delving into the “how-to,” you need to download and install the essential tools. The tutorial details how to create macOS virtual machines using both Oracle VirtualBox Manager (VirtualBox) and VMware Workstation Player (VMware Player).

Not sure which to use? Learn more about the differences between VirtualBox and VMware.

Download mojave for mac free. Apr 24, 2020  If your Mac isn't compatible with macOS Mojave, the installer will let you know. Make a backup. Before installing any upgrade, it’s a good idea to back up your Mac. Time Machine makes it simple, and other backup methods are also available. Learn how to back up your Mac. MacOS Mojave (/ m oʊ ˈ h ɑː v i, m ə-/ mo-HAH-vee) (version 10.14) is the fifteenth major release of macOS, Apple Inc.' S desktop operating system for Macintosh computers. Mojave was announced at Apple's Worldwide Developers Conference on June 4, 2018, and was released to the public on September 24, 2018. The operating system's name refers to the Mojave Desert and is part of a series of.

  • Download the latest version of VirtualBox. The tutorial uses VirtualBox 6.1.4
  • Download the latest version of VMware Player. The tutorial uses VMware Player 15.0.4

You need a copy of macOS, too. Catalina is the latest macOS version. You can find the download links for macOS Catalina in the next section.

This tutorial will focus on installing macOS Catalina in a virtual machine running on Intel hardware, using either VirtualBox or VMware Player.

Unfortunately, I do not have access to any AMD hardware, so I cannot provide a tutorial.

There is, however, the code snippet that anyone using an AMD system requires to boot a macOS Catalina using VMware on AMD hardware.

The process to launch the macOS Catalina virtual machine is the same as the Intel version but uses a slightly different code snippet. You can find the tutorial and the code snippet in the section below.

Virtual Box Cpu Settings For Macos

Furthermore, you will find links to several AMD macOS Catalina, Mojave, and High Sierra virtual machine tutorials, at the end of the article.

Download macOS Catalina Virtual Image

Use the following links to download macOS Catalina for both VirtualBox and VMware.

If the Google Drive reaches its download limit, right-click the file and select Copy to create a copy in your own Google Drive. You can then download the macOS Catalina virtual image from there.

Please note that these links may stop working from time to time. If that is the case, please leave a comment, and I’ll fix them as soon as possible.

After the virtual image finishes downloading, right-click, and extract the file using your favorite archive tool. For instance, right-click, then select 7-Zip > Extract to “macOS Catalina.”

How to Create a macOS Catalina Virtual Machine with VirtualBox

Before creating the macOS virtual machine, you need to install the VirtualBox Extension Pack. It includes fixes for USB 3.0 support, mouse and keyboard support, and other useful VirtualBox patches.

Download: VirtualBox Extension Pack for Windows (Free)

Scroll down, select All supported platforms to download, then double-click to install.

Create the macOS Catalina Virtual Machine

Open VirtualBox. Select New. Type macOS.

VirtualBox will detect the OS as you type and will default to Mac OS X. You can leave this as is.

Regarding the virtual machine name, make it something memorable yet easy to type. You’ll need to input this name in a series of commands, and it is frustrating to type a complicated name multiple times!

Next, set the amount of RAM the macOS virtual machine can use. I would suggest a minimum of 4GB, but the more you can give from the host system, the better your experience will be.

Remember, you cannot assign more RAM than your system has available, and you need to leave some memory available for the host operating system. Learn more about how much RAM does a system need?

Now, you need to assign a hard disk, which is the virtual image downloaded previously. Select Use an existing virtual hard disk file, then select the folder icon. Browse to the VMDK file, then select Create.

Edit the macOS Catalina Virtual Machine Settings

Don’t try and start your macOS Catalina virtual machine yet. Before firing the virtual machine up, you need to make a few tweaks to the settings. Right-click your macOS virtual machine and select Settings.

Under System, remove Floppy from the boot order. Ensure the Chipset is set to ICH9.

Select the Processor tab. Assign two processors. If you have a CPU with power to spare (such as an Intel Core i7 or i9 with multiple extra cores), consider assigning more. However, this isn’t vital.

Make sure the Enable PAE/NX box is checked.

Under Display, set Video Memory to 128MB.

Now, under Storage, check the box alongside Use Host I/O Cache.

Finally, head to the USB tab and select USB 3.0, then press OK.

Use Command Prompt to Add Custom Code to VirtualBox

It still isn’t quite time to fire up your macOS Catalina virtual machine. In its current configuration, VirtualBox doesn’t work with your macOS VMDK.

To get it up and running, you have to essentially patch VirtualBox before the macOS virtual machine will function. To do this, you need to enter some code using the Command Prompt. All the details are below.

Start by closing VirtualBox. The commands will not execute properly if VirtualBox or any of its associated processes are running.

Once closed, press Windows Key + X, then select Command Prompt (Admin) from the menu.

If your menu only shows the PowerShell option, type command into your Start menu search bar. Then right-click the Best Match, and select Run as Administrator.

The following code works for VirtualBox 5.x and 6.x.

Use the following command to locate the Oracle VirtualBox directory:

Now, enter the following commands, one by one. Adjust the command to match the name of your virtual machine. For instance, my virtual machine name is “macoscat.” Here are the commands:

After the completion of the commands, and presuming you encountered no errors, close the Command Prompt.

Boot Your macOS Mojave Virtual Machine

Reopen VirtualBox. Double-click your macOS virtual machine to start it. You will see a long stream of text, followed by a gray screen.

The gray screen can take a moment or two to clear, but don’t panic. Once the screen clears, macOS Catalina will begin installing. When it resolves, you will arrive at the macOS “Welcome” screen.

From here, you can set your macOS Mojave virtual machine up as you see fit.

Pro Tip: Take a snapshot of your virtual machine once it passes the gray screen. If anything goes wrong down the line, you can return to the Welcome screen setup and start the process again.

Once you complete the macOS setup, take another one so you can jump straight into your macOS installation. Head to Machine > Take Snapshot, give your snapshot a name, and wait for it to process.

How to Create a macOS Catalina Virtual Machine Using VMware Workstation Player

Prefer VMware over VirtualBox? You can create a macOS Catalina virtual machine using VMware that works exactly the same as VirtualBox. And, just as with VirtualBox, VMware also requires patching before the macOS Catalina virtual machine will work.

This part of the tutorial works for Intel and AMD systems. AMD users must use the second code snippet when editing the virtual machine VMX file. Read through the tutorial to see what this means exactly.

Patch VMware Workstation Player

In the “macOS Catalina Virtual Image” section is the VMware Player Patch Tool. Before commencing any further, download the patch tool.

Then, browse to the location you downloaded the patch tool to. Extract the contents of the archive. This process works best when the folders are on the same drive (e.g., the VMware root folder and extracted archive are both found on the C: drive).

Make sure VMware is completely closed. Now, in the patcher folder, right-click the win-install command script and select Run as Administrator. The script will open a Command Prompt window, and the patch-script will run.

Do pay attention. The script whizzes by, and you need to keep watch for any “File not Found” messages.

The most common reason for a “file not found” or a “system cannot find the file specified” message is installing VMware Workstation Player in a different location to the default folder, and executing the patch from a different directory.

Once the patch completes, you can open VMware.

Create the macOS Catalina Virtual Machine with VMware

Select Create a New Virtual Machine. Choose I will install the operating system later.

Now, select Apple Mac OS X, and change the Version to macOS 10.14. If you don’t see the macOS options, it is because the patch didn’t install correctly.

Next, you need to choose a name for your macOS Catalina virtual machine. Choose something easy to remember, then copy the file path to somewhere handy—you’re going to need it to make some edits in a moment.

On the next screen, stick with the suggested maximum hard disk size, then select Store virtual disk as a single file. Complete the virtual disk creation wizard, but do not start the virtual machine just yet.

Edit the macOS Mojave Virtual Machine Settings

Cpu

Before you can boot the virtual machine, you must edit the hardware specifications. Plus, you need to tell VMware where to find the macOS VMDK.

From the main VMware screen, select your macOS Catalina virtual machine, then right-click, and select Settings.

Like VirtualBox, bump the virtual machine memory up to at least 4GB. You can allocate more if you have RAM to spare.

Under Processors, edit the number of available cores to 2.

Now, under Hard Disk (SATA), you need to remove the hard disk created earlier. Select Remove and VMware will remove the disk automatically.

Now, select Add > Hard Disk > SATA (Recommended)> Use an existing disk. Browse to the location of the macOS VMDK and select it.

Edit the macOS Catalina VMX File for Intel Hardware

This section is for Intel users and it involves the final set of edits you need to make before switching your VMware macOS Catalina virtual machine on!

Close VMware. Head to the location you stored the macOS virtual machine. The default location is:

Browse to macOS.vmx, right-click, and select Open with…, select Notepad (or your preferred text editor). Scroll to the bottom of the configuration file and add the following line:

Save, then Exit.

You can now open VMware, select your macOS Mojave virtual machine, and fire it up!

Edit the macOS Catalina VMX File for AMD Hardware

This section is for AMD users. Like the above section, AMD users must also edit the VMX file before proceeding. The AMD edit involves a few more lines than the Intel version, but you can copy and paste the data into the file.

Close VMware. Head to the location you stored the macOS virtual machine. The default location is:

Browse to macOS.vmx, right-click, and select Open with…, select Notepad (or your preferred text editor). Scroll to the bottom of the configuration file and add the following lines:

Save, then Exit.

You can now open VMware, select your macOS Mojave virtual machine, and fire it up!

Install VMware Tools to Your macOS Catalina Virtual Machine

You now need to install VMware Tools, which is a set of utilities and extensions that improve mouse handling, video performance, and other useful things.

With the macOS virtual machine running, head to Player > Manage > Install VMware Tools.

The installation digavsc will appear on the macOS desktop. When the option appears, select Install VMware Tools, then allow it access to the removable volume. Follow the guided installer, which will require a restart on completion.

Troubleshooting

There are a couple of things that can go wrong during the macOS virtual machine installation in VMware Player Workstation.

  1. If you cannot see “Apple Mac OS X” during the virtual machine creation wizard, then you need to revisit the patch process. Ensure every process associated with VMware Player is off.
  2. If you receive the message “Mac OS X is not supported with binary translation” when starting the virtual machine, there is a strong chance you need to activate virtualization in your BIOS/UEFI configuration.
  3. If you receive the message “VMware Player unrecoverable error: (vcpu-0)” when starting the virtual machine, you need to head back to the macOS.vmx configuration file to ensure you added the extra line and saved the edit.
  4. If you’re running AMD hardware and get stuck at the Apple logo, first power off the virtual machine. Now, head to Settings > Options > General. Change the Guest operating system to Microsoft Windows, and the Version to Windows 10 x64. Press OK, then attempt to power up the virtual machine again. Once the Apple logo passes, power down the virtual machine, then set the Guest operating system option back to Apple Mac OS X, selecting the correct version.

macOS Virtual Machines for AMD Hardware

Apple uses Intel hardware to power desktops and laptops. Configuring a macOS virtual machine using Intel hardware is easier because the hardware specifications are very similar.

With AMD, the opposite is true. Because Apple does not develop macOS on AMD hardware, creating a macOS virtual machine on an AMD system is trickier.

Adding to this, I don’t have an AMD system to test macOS virtual machines on, so I cannot give you a detailed tutorial. I can, however, point you in the direction of several macOS AMD virtual machine tutorials that do work, so long as you are patient and follow each step accordingly.

  • Mojave AMD Vanilla Guide From Windows via AMD OS X
  • High Sierra 10.13.1 VM for VMware Player for Ryzen/FX/APU via AMD OS X
  • Mojave AMD VirtualBox via AMD OS X

The AMD OS X forum is a great resource for macOS virtual machines. You can find many more forum threads regarding AMD macOS virtual machines, too.

macOS Catalina Virtual Machine Installation Complete

You have two options to choose from for your macOS Catalina virtual machine. Both options are great if you want to give macOS a try before making the switch from Windows and enjoy some of the best Apple apps on offer.

You can use a virtual machine to test other operating systems too. For instance, here’s how to install a Linux distro in a virtual machine.

Are you looking to learn more about virtual machines?

Check out our VirtualBox User’s Guide, which teaches everything you need to know, or our guide to creating a virtual machine using Windows 10 Hyper-V.

Read the full article: How to Run macOS on Windows 10 in a Virtual Machine

In Oracle VM VirtualBox, a virtual machine and its settings are described in a virtual machine settings file in XML format. In addition, most virtual machines have one or more virtual hard disks. These are typically represented by disk images, such as those in VDI format. The location of these files may vary, depending on the host operating system. See Section 3.1.1, “The Machine Folder”.

Global configuration data for Oracle VM VirtualBox is maintained in another location on the host. See Section 3.1.2, “Global Settings”.

By default, each virtual machine has a directory on your host computer where all the files of that machine are stored: the XML settings file, with a .vbox file extension, and its disk images. This is called the machine folder.

By default, this machine folder is located in a common folder called VirtualBox VMs, which Oracle VM VirtualBox creates in the current system user's home directory. The location of this home directory depends on the conventions of the host operating system, as follows:

  • On Windows, this is the location returned by the SHGetFolderPath function of the Windows system library Shell32.dll, asking for the user profile. A typical location is C:Usersusername.

  • On Linux, Mac OS X, and Oracle Solaris, this is generally taken from the environment variable $HOME, except for the user root where it is taken from the account database. This is a workaround for the frequent trouble caused by users using Oracle VM VirtualBox in combination with the tool sudo, which by default does not reset the environment variable $HOME.

    A typical location on Linux and Oracle Solaris is /home/username and on Mac OS X is /Users/username.

For simplicity, we abbreviate the location of the home directory as $HOME. Using that convention, the common folder for all virtual machines is $HOME/VirtualBox VMs.

As an example, when you create a virtual machine called 'Example VM', Oracle VM VirtualBox creates the following:

  • A machine folder: $HOME/VirtualBox VMs/Example VM/

  • In the machine folder, a settings file: Example VM.vbox

  • In the machine folder, a virtual disk image: Example VM.vdi.

This is the default layout if you use the Create New Virtual Machine wizard described in Creating Your First Virtual Machine. Once you start working with the VM, additional files are added. Log files are in a subfolder called Logs, and if you have taken snapshots, they are in a Snapshots subfolder. For each VM, you can change the location of its snapshots folder in the VM settings.

You can change the default machine folder by selecting Preferences from the File menu in the Oracle VM VirtualBox main window. Then, in the displayed window, click on the General tab. Alternatively, use the VBoxManage setproperty machinefolder command. See VBoxManage setproperty.

Virtualbox Cpu Settings For Mac Os X

In addition to the files for the virtual machines, Oracle VM VirtualBox maintains global configuration data in the following directory:

  • Linux and Oracle Solaris:$HOME/.config/VirtualBox.

  • Windows:$HOME/.VirtualBox.

  • Mac OS X:$HOME/Library/VirtualBox.

Oracle VM VirtualBox creates this configuration directory automatically, if necessary. You can specify an alternate configuration directory by either setting the VBOX_USER_HOME environment variable, or on Linux or Oracle Solaris by using the standard XDG_CONFIG_HOME variable. Since the global VirtualBox.xml settings file points to all other configuration files, this enables switching between several Oracle VM VirtualBox configurations.

In this configuration directory, Oracle VM VirtualBox stores its global settings file, an XML file called VirtualBox.xml. This file includes global configuration options and a list of registered virtual machines with pointers to their XML settings files.

The following table gives a brief overview of the configuration data locations on an Oracle VM VirtualBox host.

Table 3.1 Configuration File Locations

Setting

Location

Default machines folder

$HOME/VirtualBox VMs

Default disk image location

In each machine's folder

Machine settings file extension

.vbox

Media registry

Each machine settings file

Media registration is done automatically when a storage medium is attached to a VM


Oracle VM VirtualBox uses XML for both the machine settings files and the global configuration file, VirtualBox.xml.

Virtualbox Cpu Settings For Mac Os 7

All Oracle VM VirtualBox XML files are versioned. When a new settings file is created, for example because a new virtual machine is created, Oracle VM VirtualBox automatically uses the settings format of the current Oracle VM VirtualBox version. These files may not be readable if you downgrade to an earlier version of Oracle VM VirtualBox. However, when Oracle VM VirtualBox encounters a settings file from an earlier version, such as after upgrading Oracle VM VirtualBox, it attempts to preserve the settings format as much as possible. It will only silently upgrade the settings format if the current settings cannot be expressed in the old format, for example because you enabled a feature that was not present in an earlier version of Oracle VM VirtualBox.

In such cases, Oracle VM VirtualBox backs up the old settings file in the virtual machine's configuration directory. If you need to go back to the earlier version of Oracle VM VirtualBox, then you will need to manually copy these backup files back.

We intentionally do not document the specifications of the Oracle VM VirtualBox XML files, as we must reserve the right to modify them in the future. We therefore strongly suggest that you do not edit these files manually. Oracle VM VirtualBox provides complete access to its configuration data through its the VBoxManage command line tool, see VBoxManage and its API, see Chapter 4, Oracle VM VirtualBox Programming Interfaces.

Copyright © 2004, 2020 Oracle and/or its affiliates. All rights reserved. Legal Notices