Remove All Ads from XDA

 View Poll Results: What type of OSX related Virtualization environment do you prefer?

Windows host with OSX or Linux guests
16 Vote(s)
OSX host with Windows or Linux guests
0 Vote(s)
Linux host with OSX or Windows guests
6 Vote(s)
other or none
0 Vote(s)

[INFO] How to install OSX Yosemite as a W81 VirtualBox VM

1,449 posts
Thanks Meter: 2,200
By E:V:A, Inactive Recognized Developer on 13th September 2014, 02:13 PM
Post Reply Email Thread
How to install OSX Mavericks (10.9.4) as a Windows 8.1 VirtualBox VM

Please note, this thread is only meant to share some personal notes
on what I did and how to get this working. It is not meant as a
support thread. In fact, I will not respond to any support questions.
The links found here will provide you with more information than you
could ever beg for.

Almost exactly one year ago, I posted some instructions on how to
install OSX Mountain Lion into a VirtualBox (VB) VM, running on an
old Windows Vista AMD laptop. This time I'll show you (briefly) how
to install OSX Mavericks to an Intel Laptop running Windows 8.1.

The installation procedure is divided into a few steps.

1. Pre-installation preparation
2. Install the Niresh OS X Mavericks (10.9.0) distribution.
3. Install the Official Apple OS X Mavericks (10.9.4) Update Combo
4. Post installation instructions

Some important Hackingtosh references:

Here is a mega-thread on OSX how-to's and help related items.
Especially the section on DSDT and SSDT:
13th September 2014, 02:18 PM |#2  
E:V:A's Avatar
OP Inactive Recognized Developer
Flag -∇ϕ
Thanks Meter: 2,200
1. Pre-installation preparation

Basic Hardware Info

Before you attempt to install your OSX into a VirtualBox VM (guest),
you need to find out some details about your own machine (host). Why?

Because every new OS X is depending on the Hardware to be very
"maxed out" and specific. You need to tune your VB VM to behave similar
to a real Apple machine in order to make the OS X think your machine
hardware is a real Mac. In addition, some PCI devices are passed on and
through to the VB VM engine.

For example, for a half decent running Mavericks installation,
you need to have at least 2-4 processor cores, 4 GB RAM and 30 GB HD
in your VM. Then your host need some memory as well... Then to get
correct audio, video, network, USB etc you need to know exactly what
HW your host have AND how that is presented by VB to a VM guest.
So how do you do that?

On your PC/Laptop (host):

Windows:        Use HWiNFO64 + RW-Everything + (Windows) Device Manager 

Linux:          Download and run a Live Linux distro and copy the 
                output of dmesg and lspci, lsusb, respectively. 
For this laptop we have:


From host HWiNFO64, we found:
Audio Adapter:                  Intel Lynx Point PCH - High Definition Audio Controller [C2]
Audio Controller Hardware ID:   PCI\VEN_8086&DEV_8C20&SUBSYS_11CD1043&REV_05
Audio Codec Hardware ID:        HDAUDIO\FUNC_01&VEN_10EC&DEV_0668&SUBSYS_00000000
DeviceInstanceId:               HDAUDIO\FUNC_01&VEN_10EC&DEV_0668&SUBSYS_104311CD&REV_1000\4&6BFDCFC&0&0001
We then look up these PCI IDs at one of the websites:
pci-ids or pci-database.

There we find that the host physical Audio Codec is a: Realtek ALC668 [10EC:0668]

So if we had a real Hackingtosh, we would have to find or make and
install the AppleHDA.Kext that has been built and tweaked to
correspond to this driver. Here are some relevant links:

On the VirtualBox VM (guest):

Boot up or install any minimal OS like Windows, Linux and use the
same method as above, but now running in the VM. As you will see,
the detected hardware will look different. That is basically
how OSX will see it as well.

So to help you along we'll jump ahead and I just show you
what an installed guest OS will see in terms of Audio HW.
I've ignored all other HW, since audio is what causes most
trouble to OSX guests.

On OSX 10.9.4 (Intel HD Audio):
# sudo lspci -m -v
Device:   00.05.0
Device:   82801FB (ICH6) High Definition Audio Controller
SVendor:  SigmaTel
SDevice:  Device 7680

# sudo lspci -m -n -vvv
Class:    0403
Vendor:   8086
Device:   2668
SVendor:  8384
SDevice:  7680
On Linux Mint (ICH AC97):
# sudo lspci -b -nn -v
00:05.0 Multimedia audio controller [0401]: Intel Corporation 82801AA AC'97 Audio Controller [8086:2415] (rev 01)
        Subsystem: Intel Corporation Device [8086:0000]
        Flags: bus master, medium devsel, latency 64, IRQ 11
        I/O ports at d100
        I/O ports at d200
        Kernel driver in use: snd_intel8x0

On Linux Mint (Intel HD Audio):
00:05.0 Audio device [0403]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller [8086:2668] (rev 01)
        Subsystem: SigmaTel Device [8384:7680]
        Flags: bus master, fast devsel, latency 64, IRQ 11
        Memory at f0804000 (32-bit, non-prefetchable)
        Capabilities: [50] Power Management version 2
        Kernel driver in use: snd_hda_intel
On Windows 7 (Intel HD Audio):
Audio Controller Hardware ID:   PCI\VEN_8086&DEV_2668&SUBSYS_76808384&REV_01
Audio Codec Hardware ID:        HDAUDIO\FUNC_04&VEN_0000&DEV_0000&SUBSYS_00000000
Clearly the guest driver presented is a SigmaTel with PCI ID: 8384:7680.
Further research reveals it is based on a: SigmaTel STAC9221 [8384:7680]

Thus, for any audio success on running OSX on a VirtualBox VM, we need
to find a Kernel Extension (Kext) that is compatible with this driver.
The best way is to find a tweaked AppleHD.Kext to match this driver.

HOWEVER! Lo-and-behold! The Realtek (!) linux sources seem to suggest
that this driver is used in several Macs:

From: ..\alsa\alsa-kernel\pci\hda\patch_sigmatel.c:

/* Apple Intel Mac (Mac Mini, MacBook, MacBook Pro...) */
SND_PCI_QUIRK(0x8384, 0x7680, "Mac", STAC_INTEL_MAC_AUTO),
/* codec SSIDs for Intel Mac sharing the same PCI SSID 8384:7680 */
static const struct snd_pci_quirk stac922x_intel_mac_fixup_tbl[] = {
    SND_PCI_QUIRK(0x106b, 0x0800, "Mac", STAC_INTEL_MAC_V1),
    SND_PCI_QUIRK(0x106b, 0x0600, "Mac", STAC_INTEL_MAC_V2),
    SND_PCI_QUIRK(0x106b, 0x0700, "Mac", STAC_INTEL_MAC_V2),
    SND_PCI_QUIRK(0x106b, 0x0e00, "Mac", STAC_INTEL_MAC_V3),
    SND_PCI_QUIRK(0x106b, 0x0f00, "Mac", STAC_INTEL_MAC_V3),
    SND_PCI_QUIRK(0x106b, 0x1600, "Mac", STAC_INTEL_MAC_V3),
    SND_PCI_QUIRK(0x106b, 0x1700, "Mac", STAC_INTEL_MAC_V3),
    SND_PCI_QUIRK(0x106b, 0x0200, "Mac", STAC_INTEL_MAC_V3),
    SND_PCI_QUIRK(0x106b, 0x1e00, "Mac", STAC_INTEL_MAC_V3),
    SND_PCI_QUIRK(0x106b, 0x1a00, "Mac", STAC_INTEL_MAC_V4),
    SND_PCI_QUIRK(0x106b, 0x0a00, "Mac", STAC_INTEL_MAC_V5),
    SND_PCI_QUIRK(0x106b, 0x2200, "Mac", STAC_INTEL_MAC_V5),
{ .id = 0x83847680, .name = "STAC9221 A1", .patch = patch_stac922x },
So when you first boot and install your Niresh Mavericks, you should
probably leave out any Audio related hacks, and certainly avoid
installing the VooDooHDA related Kext. It's possible (and I didn't
bother to check) that audio would then work out-of-the-box as well.

Finding a suitable "distro"

Next, you need to find and download a suitable ISO version of the
OSX Mavericks Installation disk. Apple uses the DMG format to
distribute all their installation "Disks". So to avoid having to
mess with the conversion of a 3.5+ GB DMG image to ISO, we just
try to find a torrent of one already made. But because of the
inherent complications of booting and setting up your own
"Hackingtosh" from a vanilla (original) Apple disk, we prefer to
use one that come as a distribution ("distro") which is more
flexible and much more likely to install from first try. And
usually have some sort of support forum connected to it.

One such distro is that from Niresh. We will use that one.

It is important to mention that, today Apple OS X Maverick is free
of charge for download and use, but you need an OSX based computer,
in order to get it from the Apple Store. And if you're willing to
jump through the Apple hoops, you can also get the latest
OSX Yosemite (10.10.0) and try that. But you need to signup
to the Apple Store with a credit card! So I just used my untraceable
NSA credit card to signup. It has a picture of Obama and the Logo of
Google on it. In the states you can usually find those in the bottom
of some randomly selected Kellogg's Corn-Flakes Packages.
13th September 2014, 02:18 PM |#3  
E:V:A's Avatar
OP Inactive Recognized Developer
Flag -∇ϕ
Thanks Meter: 2,200
2. Installing the Niresh OS X Mavericks distro

Fortunately all this hard work has already been described in great
detail on the MacBreaker website in:

"How to install OS X Mavericks in Virtualbox with Niresh"

However, before you go there and rush through the instructions, please
listen to this first. If you're a smart-ass who think you can outsmart
the apple bootloaders and the many precise VirtualBox settings needed
to boot OSX, you are very likely to fail and will have serious booting
trouble and subsequent OSX driver issues. And as with all Apple products,
if you're not an expert yourself, nobody will/can help you, especially
since Googling any OSX related installation issues will give you millions
of hits.

So take good time to read every step in those instructions and carefully
examine all the screenshots to know exactly how you have to setup and
tune your VirtualBox VM to your device. I will provide some additional
pictures on a few things I found working for my setup.

You need to signup (or find a torrent) to download the file:
"Niresh Mac OS X Mavericks 10.9 with AMD & Intel USB"

This OSX distribution works on both Intel and AMD based machines, and
can be run on native Hackingtoshes, VirtualBox and VMware machines.
Very Important Note:
OSX Mavericks is now free from the Apple Store, so if you are looking for the latest update, or original distribution, don't try to use this. This is a distribution that is made to be run on Hackingtoshes or VMs. It is not up-to-date nor maintained in any way. That's why it is in ISO format and not in native Apple DMG. If you already know you want to use VMware, then perhaps you're better off trying to use the VMware Mavericks Image.
Google for: "OS_X_Mavericks_10.9_Retail_VMware_Image"

Converting a DMG to ISO:

If you want to convert a DMG to ISO from within OSX run the following,
in an OSX Terminal:

cd Desktop
sudo hdiutil convert ./InstallESD.dmg -format UDTO -o InstallESD
mv InstallESD.cdr InstallESD.iso
sudo hdiutil makehybrid -iso -joliet -hfs -o OSXMavericks.iso OSXMavericks.dmg
I found the following "script" on the web. It is used to convert a Yosemite
DMG image to ISO. But it doesn't look like a real script, so probably it should
be entered one item at the time. (Also, I can't find the original author. So if you are, just let me know an I'll give you credit for it.)
# ==============================================================
# 10.10 How to make an ISO from the
# ==============================================================
# Mount the installer image. It assumes that the installation app is called "Install OS X"
# located in your "Applications" folder. If not, change the first command accordingly.
hdiutil attach /Applications/Install\ OS\ X\ -noverify -nobrowse -mountpoint /Volumes/install_app

# Convert the boot image to a sparse bundle
hdiutil convert /Volumes/install_app/BaseSystem.dmg -format UDSP -o /tmp/Yosemite

# Increase the sparse bundle capacity to 8GB to accommodate the packages
hdiutil resize -size 8g /tmp/Yosemite.sparseimage

# Mount the sparse bundle for package addition
hdiutil attach /tmp/Yosemite.sparseimage -noverify -nobrowse -mountpoint /Volumes/install_build

# Remove Package link and replace with actual files
rm /Volumes/install_build/System/Installation/Packages
cp -rp /Volumes/install_app/Packages /Volumes/install_build/System/Installation/
cp -rp /Volumes/install_app/BaseSystem.* /Volumes/install_build/

# Unmount the installer image
hdiutil detach /Volumes/install_app

# Unmount the sparse bundle
hdiutil detach /Volumes/install_build

# Resize the partition in the sparse bundle to remove any free space
hdiutil resize -size `hdiutil resize -limits /tmp/Yosemite.sparseimage | tail -n 1 | awk '{ print $1 }'`b /tmp/Yosemite.sparseimage

# Convert the sparse bundle to ISO/CD master
hdiutil convert /tmp/Yosemite.sparseimage -format UDTO -o /tmp/Yosemite

# Remove the sparse bundle
rm /tmp/Yosemite.sparseimage

# Rename the ISO and move it to the desktop
mv /tmp/Yosemite.cdr ~/Desktop/Yosemite.iso
VirtualBox Installation Instructions:

Follow the MacBreaker installation instructions EXACTLY. When
installing on a Haswell based PC host, you MUST run the VBoxManage
commands to make your VM think it has an older/supported processor.
Before trying this, or if you get an error, make sure:

  1. That your Windows system PATH contains both your Windows home directory and the VirtualBox
    program directory:
    a) "%HOMEDRIVE%%HOMEPATH%;" and
    b) "C:\Program Files\Oracle\Virtualbox"
  2. That after creating your OSX VM, that you close VirtualBox and restart it, in order to make all
    the new settings take effect and get registered in the *.vbox file, used by VBoxManage.exe.
    The location of the *.vobx settings file is the same as where you have the VB images.
    (This used to be VirtualBox.xml in VB < 4.0.)
To test, open a CMD or Cygwin shell as administrator and run:
VBoxManage.exe list hostcpuids
If it works without any error, go on and change the CPU ID of the VM where you're installing OSX with:

VBoxManage.exe modifyvm "name_of_your_vm" --cpuidset 00000001 000306a9 00020800 80000201 178bfbff
(Technically you're entering: [--cpuidset <leaf> <eax> <ebx> <ecx> <edx>].)

If you're having trouble, you can also edit <name_of_your_vm>.vbox file
directly, by adding/removing the following lines:
                <CpuIdLeaf id="1" eax="1787" ebx="2048" ecx="2147484169" edx="126614527"/>
(As you can see these are the same values in Dec as those in Hex above.)

When successful, restart VirtualBox to make sure your changes has
taken effect. After starting the properly setup OSX VM on a Haswell
machine, the only bootflag you may want is: "-v" for verbose bootup.

3. Install the Official Apple OS X Mavericks (10.9.4) Update Combo

Go into the OSX control panel and disable automatic updates. Then go to Apple Store and
download the latest Mavericks Combo Update. Updating should not change any of your
working settings, but to be safe, make a snapshot before doing this. Once downloaded,
just open and run the update. Installation will take a while.

4. Post installation instructions

So now that you got your basic OSX system running, the first thing to
do is to make a VirtualBox Snapshot, so that you can revert to this
point in case any of the subsequent procedures fails or mess up your
working system.

Once you are up and running with your virtual OS X machine you need to
do a couple of housekeeping tasks to ensure your virtual machine does
not freeze. Firstly go to "System Preferences" and select "Energy Saver"
and set "Computer sleep:" and "Display sleep:" to Never and also uncheck
"Put hard disks to sleep when possible", "Wake for Ethernet network
access" and "Allow power button to put the computer to sleep". In
"Desktop & Screen Saver" set "Screen Saver" to "Start after:" Never.

Then there are 3 things everyone have to have:
  1. Shared folders between the host and guest OS.
  2. Shared clip-board data, so that you can copy/paste between host and guest OS.
  3. Change the default Display size
Since the VirtualBox maffia refuse to release the Guest Additions (GA)
for OSX, we have to work around these issues. Or if you are a brave OSX
developer, you can try to patch and compile the GA from their sources
and if you're successful, don't forget to share and give us a way to
send you some gold donations.

Folder Sharing

Folder sharing is most easily accomplished by setting up a network
share between host and guest OS. There are many ways and variations
on how to do this. But what most instructions miss, is that you would
probably like to keep your host more secure than your guest. This
means that the guest should be configured as the server and the
host as a client. (Which is contrary to most simpler instructions.)

So here are 3 easy ways to accomplish this.
1. Use Windows 8.1 and OSX internal file sharing capabilities.
2. Use Dropbox to share a folder and enable LANsync to make it fast.
3. Use one of the 3rd party tools below.

Of these, I prefer to use something where I don't need to depend on
an internet connection and having to sign up with any new services.

The easiest way I found to accomplish folder sharing using method (1)
was to use Windows 8.1 built in NFS functionality. To use this, you
need to enable NFS sharing of a folder in your OSX VM and then mount
this folder in your W81 host.

Setup OSX NFS (guest):
(Thanks to linoceros post at forums.)

(a) Check your network conection with 'ifconfig" and note your IP
on the local network. (I use a bridged-ethernet interface.)

(b) Read the OSX man pages for "export".


"The -alldirs flag allows the host(s) to mount at any point
within the file system, including regular files if the '-R'
option is used on nfsd."

(c) Find the UID and GID of the OSX user you are using.
$ id
uid=501(eva) gid=20(staff) groups=20(staff),
(d) Edit the file: /etc/exports (usually not present.)
In this file, the syntax is basically:
<shared folder> <options> <client IP>

$ sudo vi /etc/exports
/Users/eva/Desktop/winshare -mapall=501:20 -alldirs
(You may need to change this for more security...)

(e) Edit the file: /etc/nfs.conf (usually already present.) And add the following line:

$ sudo vi /etc/nfs.conf

nfs.server.mount.require_resv_port = 0
(f) Then let NFS know you've made a change by running:
$ nfsd update

Setup on Win8.1 (host):

(g) Now go to your Windows host and in "This PC" (or equivalent)
left-click and select "Add a network location". You will be asked to
provide a an "internet or network location". There you simply write
the IP you noted in step (a) and the "shared" folder you selected
in step (d). Written in windows notation as:

NOTE: Do not try to "edit" the files in the share. The behavior is a
bit unpredictable, so it's better to copy to another location and
then back again after edit. Not sure at the moment why that is...

Clip-board sharing

To keep things simple we should limit ourselves and be satified
with copy/paste operations. Just like before, here there are many
variations on KMS (Keyboard-Mouse-Screen) sharing solutions from
3rd parties. Even Apple themselves has a lame solution called
"Back To My Mac" that require you to sign up to, and use iCloud
before being able to have all your stuff snatched up by Apples
NSA employees. Here are the links.

[1] "How to set up Back To My Mac..."
[2] "Set up and use Back to My Mac"
[3] "Set up security options for Back to My Mac"

BUT No thanks! Let's find another solution.

So what we need, is a way to only share the clipboard data over
the local network. We don't need mouse sharing as all that already
works great in VB, unfortunately its not so easy to find something
with only clipboard sharing. So we choose the most easy one, which
means the one with best instructions, and that is ShareMouse.

The most popular and free ones are:
ShareMouse    (cross-platform mouse-keyboard-file share)    
Synergy        (cross-platform mouse-keyboard-file share)    
ShareClipboard    (Node.js based OSX/WIN clipboard sharing)    
Other solutions to consider.

Ducto R6    (cross device file/clipboard share)
IP.SHARE    (web based file/clipboard share)
ClipboardSync    (Google Chrome Clipboard Sync)    [instructions]
Installation of ShareClipboard:

ShareClipboard depend on the Node.js API which can be downlaoded and
installed from HERE. It's available for all platforms and need to be
installed on each VM. One done, it is easy to starts the clip-board
sharing. There are two ways to use this:

1. Use as client-to-client sharing.
2. Use a server to act as a redirector, broadcasting the clipboard
text from a ShareClipboard client to the other ones, while the
server clipboard is left untouched.

To use ShareClipboard with Clients only (1):
a) Install the copy-paste module with the Node Package Manager*: 
        npm install copy-paste

b) Open a terminal and run the script with one of the following: 
        node share-clipboard.js 
        node share-clipboard.js <IP_ADDRESS> 

c) If you haven't specified the IP address in the previous step, 
   connect other Share Clipboard (or Share Clip) instances to 
   this instance .
d) Now you can copy among the Share Clipboard clients.
To use your host as the ShareClipboard Server (1):
a) Open a terminal and run the script with: 
        node share-clipboard-server.js

b) Connect the ShareClipboard clients to the server IP.
c) Now you can copy among the Share Clipboard clients.
* Reagrdless of the BS written on their FAQ, "npm" IS a Node package manager.

Changing Display size

To change the default video/display size, from 1280x1024 (or 1024x768)
to 1920x1080, you need to edit the OSX bootloader plist.

1. Use Finder to open the file: /Extra/org.chameleon.Boot.plist
in Editor or use Terminal App in shell with:

sudo vi /Extra/org.chameleon.Boot.plist
2. Then between the <dict> and </dict> tags, in the file, insert the
following lines:

    <key>Graphics Mode</key>
3. Save and shutdown VM, but keep VirtualBox open.
4. Similarly as above, open an administrative CMD/Cygwin shell and issue the command:

vboxmanage setextradata "name_of_your_vm" "CustomVideoMode1" "1920x1080x32"
5. Restart VirtualBox.

PS. I found 1600x900x32 in non-scaled mode, more useful on this Laptop.

Additional Enhancements and Fixes

  • To remove window flickering in Safari, remove the zero byte file:

Good Luck!
13th September 2014, 02:19 PM |#4  
E:V:A's Avatar
OP Inactive Recognized Developer
Flag -∇ϕ
Thanks Meter: 2,200
< Let there be even more dragons>
13th September 2014, 02:40 PM |#5  
FireWall123's Avatar
Senior Member
Flag Kuwait
Thanks Meter: 927
I have installed OSX Mavericks 10.9 using VMware Workstation.
my first intention was to install OS X 10.9 on an external HDD and boot it from there instead of "virtual", but couldnt find answers.
I have intel , BTW.
20th September 2014, 10:38 PM |#6  
E:V:A's Avatar
OP Inactive Recognized Developer
Flag -∇ϕ
Thanks Meter: 2,200
Booting Yosemite (10.10.x) Public Beta 2 in VirtualBox

Just for the hell of it, I decided I wanted to run the latest Yosemite Public Beta 2 in a VirtualBox VM under Windows 8.1. After all sorts of trouble, I finally learned that Yosemite has implemented more compatibility changes that blocks older Apple hardware from using it. So the way to work around is to hack your VM in such a way that it acts like recent Apple HW. Fortunately, VirtualBox is very flexible in this area, but very poorly documented and extremely poorly supported, as Oracle (VirtualBox) forum have decided to avoid any forms of Apple litigation's, by simply banning any questions related to running OSX on any HW not from Apple.

So here I will present the simple steps to get Yosemite to run on a recent (Intel) Haswell-based Windows 8.1 host. There are two ways to do this.
  1. Use another Mac/Hackingtosh to download the latest Public Beta (PB) or Developer Preview (DP) from Apples Developer/Beta site. You need to sign up and so on. Then run script to convert into DMG format.
  2. Download an already made bootable Yosemite Public Beta in DMG format from some torrent site.
Once you have obtained (1) or (2) you're ready to install your Yosemite VM.
Do the following:

For Option 1


For Option 2

First download your Yosemite Public Beta in bootable DMG format from your favorite torrent site. In my case it was called YB2VB.dmg. Then create your new VirtualBox VM according to:
- Create a VM disk with > 40 GiB
- Under General > Basic:Version, use "Mac OS X (64bit)"
- Under System > Motherboard
    : Base Memory, select 6 GiB VM RAM
    : Chipset, use PCIIX 
    : Extended Features, select all to use EFI, ACPI, and UTC
- Under System > Processor, select only 1 CPU
- Under System > Acceleration: Hardware Virtualization, select all.
- Under Display > Video:Video Memory, use 128 MB, and do not select any Extended Features (2D/3D)
- Under Storage > Storage Tree, select the "Empty" (CD icon) and go to:
  "CD/DVD Drive" selector and click on the right-most CD icon for a 
  drop-down menu. On that menu, browse to and select your *.dmg 
  image you downloaded above. Also select the "Live CD/DVD" option. 
- Save and close VirtualBox.
Next you need to tune VB to impersonate some recent Apple HW.
First re-start VirtualBox. Once started, run an administrative command shell and run these:

VBoxManage.exe modifyvm "YourVMname" --cpuidset 00000001 000306a9 04100800 7fbae3ff bfebfbff
VBoxManage setextradata "YourVMname" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "MacBookPro11,3"
VBoxManage setextradata "YourVMname" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0"
VBoxManage setextradata "YourVMname" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "IHateApple"
VBoxManage setextradata "YourVMname" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc"
VBoxManage setextradata "YourVMname" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1
Close VB for changes to take proper effect. Restart and start you VM.
Be very patient, and after some error messages your OSX should bootup
to start the setup process.

Formatting the (new) VM disk/parition

Once the boot process start loading, you'll have to select language and then the boot disk to use. But since you don't have a boot disk, but only the mounted CD-ROM (DMG) image, you'll have to go into Disk Utility and format the VM disk partition and give it a name like this.


Now you can exit DIsk Utility and continue installing by selecting your new disk...

Once installation is finished, the system will reboot and you will be asked a few setup questions. After that the following assistant will aks you signup. Forget it by force closing it.

Then you can run the System Information App to find what you got:

and the Terminal App to see what kernel you're using:

You can now Google yourself senseless to tweak your new OSX to all the requirements you need. Keep an eye on the Mavericks post above as a guide or reference. However, before doing so, you may want to download and install the latest updates and the latest Beta, which is Beta 3 (at the time of this writing.)

Good Luck!
Attached Thumbnails
Click image for larger version

Name:	OSXz_install1.png
Views:	242249
Size:	217.4 KB
ID:	2944548   Click image for larger version

Name:	OSXz_install2.png
Views:	242186
Size:	236.1 KB
ID:	2944549   Click image for larger version

Name:	OSXz_install3.png
Views:	241022
Size:	182.6 KB
ID:	2944550  
Attached Images
File Type: jpg OSXz_feedback_x.jpg - [Click for QR Code] (206.2 KB, 241811 views)
File Type: jpg OSXz_vanilla_x.jpg - [Click for QR Code] (193.5 KB, 113661 views)
File Type: jpg OSXz_vanilla2_x.jpg - [Click for QR Code] (193.6 KB, 44 views)
File Type: jpg OSXz_vanilla3_x.jpg - [Click for QR Code] (199.8 KB, 114347 views)
22nd October 2014, 08:11 AM |#7  
Junior Member
Thanks Meter: 1
does anyone know any kext i can use for virtualbox VGA ? The graphics performance on the OS X VM is too low.
23rd October 2014, 02:13 PM |#8  
E:V:A's Avatar
OP Inactive Recognized Developer
Flag -∇ϕ
Thanks Meter: 2,200
Originally Posted by renatofdds

does anyone know any kext i can use for virtualbox VGA ? The graphics performance on the OS X VM is too low.

What do you mean "too slow". Works just fine for me. Maybe you have a slow PC and not enough RAM allocated for you VM. If you wanna find the driver used, look in the drivers detected on any VM guest OS, like linux or windows.
23rd October 2014, 11:02 PM |#9  
Junior Member
Thanks Meter: 1
Originally Posted by E:V:A

What do you mean "too slow". Works just fine for me. Maybe you have a slow PC and not enough RAM allocated for you VM. If you wanna find the driver used, look in the drivers detected on any VM guest OS, like linux or windows.

The 3D performance of the generic driver (VESA) uses a software rasterizer wich is too low on performance. I have assigned 8GB of RAM and 4 cores to the VM, on an i7 Haswell, its not insufficient hardware.
Try executing launchpad and you will know what i'm talking about.
25th October 2014, 11:18 PM |#10  
E:V:A's Avatar
OP Inactive Recognized Developer
Flag -∇ϕ
Thanks Meter: 2,200
@renatofdds Unfortunately I don't think a kext could fix that problem. It seem to be either a poor video driver from Oracle, or wrong cpuid settings, that doesn't allow for native correct 3D graphics on the processor. (I have the same setup as you.) So my best bet is that you head over to the Virtualbox support forum at Oracle, and look under "OSX" guest on "OSX" hosts. And see how they do it, or ask for help there. (They don't allow for OSX guests on Win hosts.)
27th October 2014, 01:15 PM |#11  
Junior Member
Thanks Meter: 1
Originally Posted by E:V:A

@renatofdds Unfortunately I don't think a kext could fix that problem. It seem to be either a poor video driver from Oracle, or wrong cpuid settings, that doesn't allow for native correct 3D graphics on the processor. (I have the same setup as you.) So my best bet is that you head over to the Virtualbox support forum at Oracle, and look under "OSX" guest on "OSX" hosts. And see how they do it, or ask for help there. (They don't allow for OSX guests on Win hosts.)

OK man, tks for the suggestion.
Post Reply Subscribe to Thread

mavericks, osx, virtualbox, windows8

Guest Quick Reply (no urls or BBcode)
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes