Jump to content

Search the Community: Showing results for tags 'VirtualBox'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • InsanelyMac Lounge
    • Front Page News and Rumors
    • Reader News and Reviews
    • Forum Information and Feedback
  • OSx86 Project
    • New Releases and Updates
    • New Users Lounge
    • Developers Corner
    • Tutorials (The Genius Bar)
    • Technical FAQ
    • OSx86 Installation
    • Post-Installation
    • DSDT and SSDT
    • Hardware Components and Drivers
    • Complete Desktops
    • Notebooks
    • Netbooks
    • Tablets
    • MacMod of the Month
    • Multi-booting and Virtualisation
  • International
    • Your Language
    • Deutsch
    • Español
    • Français
    • Italiano
    • Português
    • Русский
  • Apple World
    • Mac OS X
    • Apple Computers and Hardware
    • iOS Devices
    • Mac Applications
    • Mac Programming and Development
    • iOS Programming and Development
    • Mac Gaming
    • Mac Accessories
  • Discuss and Learn
    • Windows Discussion
    • *nix
    • Apple Opinions and Discussion
    • The Great Debates
    • Internet(s), Servers, and Networks
    • Buying Thoughts, Reviews, and Recommendations
    • Mods and Overclocking
    • The Big Issues [Real Life]
  • Everything Else
    • Creativity
    • Thunderdome (Random Stuff)
    • Laughs
    • The Marketplace


  • Kexts
    • Graphics Cards
    • Audio
    • LAN and Wireless
    • Other
  • Kernels
  • Bootloaders
  • DSDTs
    • Patches
  • Pandora
  • Apps
  • Miscellaneous
  • Customization

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start




Website URL







Found 47 results

  1. VMQemuVGA display adapter driver for OSx86 running as a VirtualBox guest. The binary should work on all OSs from Snow Leopard up to Yosemite 10.10. It allows to set different screen resolutions in VirtualBox from System Preferences. The changes I've made to the fork have been minimal. GitHub project page Binary and source releases Special thanks: PureDarwin probonopd rafirafi Zenith432 VMware, Inc
  2. Run Vanilla OS X El Capitan, Sierra or High Sierra in VirtualBox 5.0.34 on a Windows Host Following on from my previous guide on how to create a VMware virtual machine running Vanilla OS X El Capitan in Windows, I’ve decided to write a similar guide for creating a VirtualBox El Capitan VM. The virtual machine should be useful for testing El Capitan and also for creating installers for use on a real machine/hackintosh. There are other tutorials and videos on the net about running OS X on Windows machines using pre-made VMDK disk images but you can never guarantee what else is in there…. I’ve gathered info for this guide from several threads in the Multibooting and Virtualisation section of this forum and also the wider internet eg @colt2 HOW TO: Create a bootable El Capitan ISO for VMware @dsmccombs comment on faking Ivybridge Processor @E:V:A http://forum.xda-developers.com/showpost.php?p=55572430&postcount=6 @Tech Reviews video tutorial https://www.youtube.com/watch?v=t7X07U63lwg. VirtualBox Forum: Status of OSX on OSX Requirements Intel PC with four or more CPU cores running Windows 7 X64 or later OS (2 or more cores needed for OS X) 4GB or more RAM (2GB or more will be needed for OS X) Hard Disk with at least 40GB free for Virtual Machine Oracle VM VirtualBox v 5.0.34 Install OS X El Capitan app and Mac or Hack to prepare installation iso <-- Now, no longer necessary to have previous access to a Mac or Hack by building the Installer.app from scratch - see post#75 16GB or larger exFAT formatted USB stick to transfer El Capitan iso from Mac/Hack to Host PC Prepare Installation ISO on your Mac or Hack 1. On your Mac or Hack, download "Install OS X El Capitan.app" from the App Store into your Applications folder. 2. Download and unzip the CECI.tool (attached to this post) into your ~/Downloads folder. The commands in this executable script are shown below for informational purposes. Note: you will need approx 16GB of free space on your hard disk for the script to complete. 3. Open OS X terminal, then run the following commands to execute the script: cd downloads chmod +x CECI.tool ./CECI.tool 4. At the end of the process, you will have an El Capitan iso on your desktop - copy this onto an exFAT formatted USB for use on the PC Host later. Create an El Capitan Virtual Machine in VirtualBox 1. Open the VirtualBox program and click the "New" button to create a new VM. 2. Select Mac OS X and Mac OS X 10.11 El Capitan (64 -bit) for Operating System type and version. I named my Virtual Machine "El_Capitan", then clicked next... 3. Leave the Memory size at the recommended 2048 MB, then click next. 4. Choose to "Create a virtual hard disk now", then click the create button. 5. For the hard disk file type, the default is VDI (VirtualBox Disk Image) but I have selected VMDK for inter-operability with VMWare. Click next... 6. For Storage on physical hard disk, I have chosen the default Dynamically allocated (grows larger to a set limit as you need more disk space). 7. On the File location and size screen, you can set the location of the new virtual hard disk and its size - I recommend changing disk size to 40GB or larger. When you click the create button, you will now see your new VM in the VirtualBox main GUI. 8. Click the settings button on the Main Menu to tweak a few settings.... a. On the System/Motherboard tab in Boot Order, you can uncheck the Floppy Drive (who has these now?) b. On the System/Processor tab, you can increase the allocated CPU cores to 2 c. On the Display tab, you can increase the allocated Video Memory to 128MB d. On the Storage tab, click on the icon of the Optical Drive and select "Choose Virtual Optical Disk File". Navigate and select the El Capitan ISO we created earlier... e. Click the OK button to finalise the VM settings. Patch El Capitan vbox configuration file with DMI Settings from a Mac 1. From the start menu, type cmd and click run as administrator to open an administrative command prompt. 2. Choose a Mac Model similar to your host system, then type the following lines, followed by <enter> after each line. Make sure you first close all VirtualBox Windows and the VirtualBox program, otherwise any changes you make won't stick... Eg iMac11,3 cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac11,3" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F2238BAE" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 MacBookPro11,3 cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "MacBookPro11,3" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-2BD1B31983FE1663" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 Macmini6,2 cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "Macmini6,2" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F65AE981FFA204ED" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 3. Optional- For some host systems eg those with Haswell and newer CPUs, you might have to spoof an older CPU to avoid VirtualBox errors. You can try from one of the following if this happens: To spoof Lynnfield i5 750 CPU VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000106e5 06100800 0098e3fd bfebfbff To spoof IvyBridge CPU VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 04100800 7fbae3ff bfebfbff or VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 00020800 80000201 178bfbff 4. Close the command prompt window. Installation of El Capitan We are now ready to start the El_Capitan Virtual Machine.... Installation should be relatively straight forward, just following the prompts of the OS X installer: 1. Select language, agree to legal terms 2. Use Disk Utility from the Utilities Menu to erase and format the virtual hard drive as a single partition GUID Mac OS X Extended. I named my drive "Macintosh HD" but you can enter whatever you like eg El_Capitan. 3. Quit DU and choose Macintosh HD to install El Capitan on. 4. After 20-30 min (depending on how fast your system is), the installation will complete. At this point, unmount the El Capitan ISO by clicking the Devices menu from the VM window, click Optical Drives, then choose Remove disk from virtual drive. The VM is now ready to reboot into OS X from the virtual hard drive. 5. At the welcome screen, choose your country and keyboard layout. You can skip transfer information, location services and logging in with your Apple ID if you wish… 6. Create a User Account and select your Time Zone. You can skip sending diagnostics and usage data to Apple…. 7. Finally, you will arrive at the El Capitan Desktop. 8. Network/internet and audio should work OOB but on my system, the sounds were distorted. Unfortunately, there is no QE/CI and the VM resolution will be fixed without the ability to dynamically resize the VM window (no VirtualBox additions for OS X guests atm). Customization with VBoxManage 1. You can change the default resolution of 1024*768 (after shutting down the VM) with the VBoxManage command from the Windows Administrative Command Prompt: cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" VBoxInternal2/EfiGopMode N (Where N can be one of 0,1,2,3,4,5) referring to the 640x480, 800x600, 1024x768, 1280x1024, 1440x900, 1920x1200 screen resolution respectively. Update: For VirtualBox 5.2.x, the command for changing screen resolution has changed... VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution XxY (where X=Horizontal screen resolution, Y=Vertical screen resolution) eg VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution 1280x1024 2. Adding serials and other SMBIOS details for the System Information Screen VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemSerial" "W8#######B6" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardSerial" "W8#########1A" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVendor" "Apple Inc." VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemFamily" "iMac" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBIOSVersion" "IM112.0057.03B" A listing of known issues with Mac OS X guests can be found in the VirtualBox Manual - link https://www.virtualbox.org/manual/ch14.html. Vanilla Mavericks and Yosemite, Snow Leopard from Retail DVD The same VM settings for El Capitan will also boot and run vanilla installations of OS X Mavericks and Yosemite . Attached to this post are installer scripts to create bootable Mavericks (CMI.tool) and Yosemite (CYI.tool) ISOs for VirtualBox and VMware. With the respective OS X installer apps in the Applications folder, download and run the installer tools using terminal ie To create a Mavericks ISO on your desktop cd downloads chmod +x CMI.tool ./CMI.tool To create a Yosemite ISO on your desktop cd downloads chmod +x CYI.tool ./CYI.tool Here is a screenshot of the VM running Mavericks 10.9.5... Finally, those without a Mac/Hack to prepare the install media can purchase a retail Snow Leopard DVD directly from Apple and install OSX 10.6.3 on their virtual machines (Snow Leopard, Lion and Mountain Lion run quite happily in VirtualBox with 1 CPU, 1-2 GB of RAM and the rest of the settings unchanged from above). Once you update by combo update to SL 10.6.8, you can directly download El Capitan from the App Store for free . UPDATE macOS Sierra 10.12 to 10.12.6: For macOS Sierra, use CSI.tool in post#51. UPDATE macOS High Sierra 17A365: For macOS High Sierra, use CHSI.tool in post#73. Good luck and enjoy CECI.tool.zip CYI.tool.zip CMI.tool.zip
  3. For Public Beta Version I found this script from agentsim who is GitHubGist user. It Works for me on Windows 10 Workstation 12.5.7 # Generate a BaseSystem.dmg with High Sierra Beta Installer Packageshdiutil attach /Applications/Install\ macOS\ High\ Sierra\ Beta.app/Contents/SharedSupport/InstallESD.dmg -noverify -mountpoint /Volumes/highsierrahdiutil create -o /tmp/HighSierraBase.cdr -size 7316m -layout SPUD -fs HFS+Jhdiutil attach /tmp/HighSierraBase.cdr.dmg -noverify -mountpoint /Volumes/install_buildasr restore -source /Applications/Install\ macOS\ High\ Sierra\ Beta.app/Contents/SharedSupport/BaseSystem.dmg -target /Volumes/install_build -noprompt -noverify -erasecp -R /Volumes/highsierra/Packages /Volumes/OS\ X\ Base\ System/System/Installationhdiutil detach /Volumes/OS\ X\ Base\ System/hdiutil detach /Volumes/highsierra/mv /tmp/HighSierraBase.cdr.dmg /tmp/BaseSystem.dmg# Restore the High Sierra Beta Installer's BaseSystem.dmg into file system and place custom BaseSystem.dmg into the roothdiutil create -o /tmp/HighSierra.cdr -size 8965m -layout SPUD -fs HFS+Jhdiutil attach /tmp/HighSierra.cdr.dmg -noverify -mountpoint /Volumes/install_buildasr restore -source /Applications/Install\ macOS\ High\ Sierra\ Beta.app/Contents/SharedSupport/BaseSystem.dmg -target /Volumes/install_build -noprompt -noverify -erasecp /tmp/BaseSystem.dmg /Volumes/OS\ X\ Base\ Systemrm /tmp/BaseSystem.dmghdiutil detach /Volumes/OS\ X\ Base\ System/hdiutil convert /tmp/HighSierra.cdr.dmg -format UDTO -o /tmp/HighSierra.isomv /tmp/HighSierra.iso.cdr ~/Desktop/HighSierraPublicBeta.isorm /tmp/HighSierra.cdr.dmg
  4. After i finished updating macOS High Sierra on HP x360 15-u011dx Haswell HD4400 i7-4510u, I started to update my daughter Dell Inspiron 7352 Broadwell HD5500 i7-5500u. It was a little harder but it works quite nicely. The new Clover is Buggy with the cache that cause "Error loading Kernel Cache..." that I had to re-install the OS. Kernel Panic all the time until I got the config.plist and kexts correctly. Now it's a perfect little 13" MacBook Air7,2. If you have anything thing with a "u" at the end of the CPU, don't use macbook pro, it doesn't do you any good. I'll have full tutorial soon. Make sure to have en0 built-in without Ethernet Built-in Cheers, Louis
  5. Creating a Hackintosh Linode instance seems entirely achievable after reviewing the steps in creating a Windows linode instance here: https://github.com/ClickSimply/docs/blob/windows-on-linode/docs/tools-reference/windows-on-linode/installing-windows-on-linode-vps.md Getting macOS running on VirtualBox doesn't seem to be much of a challenge (example), yet getting to the hfs+ resizing step could be a little trickier (unless perhaps we create an additional boot volume that has something like iPartition on it to resize the primary volume). Any thoughts on achieving this? It should be pretty cost effective to fire up Linodes with macOS / Hackintosh on them. I'll probably go with the 8192 size (8GB with a quad core Xeon and 96 GB SSD storage), but a little smaller could work.
  6. Hello. I've never done VirtualBox for hackintosh, and am having trouble getting my VM to run. I been working on it for day, and still can't get it running. I enabled Virtualization tech in my bios, and still nothing. This time, I tired the guide here: http://www.macbreaker.com/2012/02/snow-leopard-virtualbox.html I followed every step, and when I get to the Step 4, I always get this error on VBox: cdboot: init cdboot: file size: 00042300 cdboot: reading sectors: 00000085 cdboot: loading....................... cdboot: done cdboot: init cdboot: BIOS disk read error at sector: 00000011 cdboot: error_ I'm not sure what to do anymore, because each guide I've done ended up like this. Could it be because I put the .vdi on an external harddrive while VBox is on my internal? Could it be hardware related? I don't have very much room on my main harddrive, but I'll make room if that's the case! This is my first time trying this. Also, if it helps, I'm running Windows 10 with an i7 4710HQ, Nvidia 860m, and 8 gb RAM. It's a Lenovo y50 from 2014.
  7. rolloLG

    Virtualbox just 4MB vram

    I've successfully installed an original MacOS Sierra iso on Virtualbox 5.1.22 r115126... no special hackintosh custom distro installed, apparently was an original image. my only problem is reported VRAM inside virtualbox is just 4MB VRAM, despite I've set in virtualbox settings 256MB. For this reason emulation is VERY sluggish. Please can some kind soul instruct me how to increase that value?
  8. Hi, this is my first post in this forum and maybe my first or second post in a forum also , I decided to wite this post after looking in the web and doing lot of research without any good result to it, and i was so enthusiastic about building my hackintosh laptop that i finally found the way to my problem. I dont have access to real macbook or mac, so following one of the hundred post of internet about running osx in virtualbox I got my first osx run, i inmediatly downloaded sierra app [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url], clover conf and all necessary tools, and started my long way to the obtention of a bootable usb. Every method i tested([url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url], vanilla, clover, etc) failed copying files to the usb, despite I had installed extension packs and all necessary stuff to get usb working on the vm (also I tested doing it in ubuntu vbox) failed in copyng installer files, base system or any other step, in fact the usb unmounted after 20-30 min, so finally I ended up testing to create a "virtual usb" and fantastically it done all the steps without problems, so then i managed to get that virtual usb data to a physical usb here are the steps: First of all you need vbox running osx and all the necessary stuff to build the usb with your prefered method, then you need to install qemu-img for your host OS (i tested perfectly in windows and ubuntu) and finally you will need to install optionally win32diskimagger, a tool to write any img files to usb in windows (qemu support writing directly to usb device but the absence of progress bar stressed me , in case you use ubuntu no porblem write directly). We start creating the new virtual drive to our mac vm: 1. Go to vm settings 2. Enter to storage tab and create the drive as the following images: 3. Select disk type (I always tested with vmdk cause i knew it was supported by qemu-img). 4. Choose fixed size. 5. Press next and select folder, name and size, I recommend to select 8,5GB as size, the default folder is vm folder 6. Afther that your vm has a new virtual device that behave exactly as a physical device plugged in, so next steps are on your own doing the usb bootable with your prefered method but selecting the virtual drive as target. The information will be stored in vmdk file in host system drive. 7. After successfully complete the previous steps, you should have two partitions in the virtual device (usually EFI and System installation partition), so now you can exit and power off the vm. 8. In ubuntu open a terminal in the folder where the vmdk is stored(default is virtual machine folder), in widows I recommend to move vmdk to the folder where reside the quemu-img.exe files, then type cmd in the path bar. 9. In the terminal type the command to convert the vmdk to img in windows, in ubuntu ask the quemu-img to write directly to the usb device, so you need to insert the real usb pendrive to write. Windows command: qemu-img.exe convert usb.vmdk -O raw disk.img Ubuntu command: qemu-img convert test.qcow2 -O raw /dev/sdbX (type "sudo df" command to get /dev path of the usb, is different to the /media path) In both OS the process takes some minutes, when it finishes the terminal will be ready to type new command. In case you did it with ubuntu method your UBS is READY TO BOOT!! 10. In windows open Win32DiskImagger, select img file, target drie(usb letter), and pres WRITE! Congrats! You are done!, now you have a bootable usb of OSX, now you are ready to fight with kernel panics, :beachball: of death, missing kext and all that stuff that need to be done before reaching your runnin hackintosh :lolno::crazy:. Thanks for reading I hope it was useful for you, this is my first important contributon to a forum. PD: sorry my bad english. PD2: any question suggestion or corrections are welcome. PD3: if you have problem finding the required stuff just let me know, i attached qemu for 64bit , win32diskimagger is easily downloadable via sourceforge. PD4: the original idea was to publish this via TM but they banned because talking about VM´s, anyway I think is big problem unsolved before this publication hope you like guys. qemu-img-win-x64-2_3_0.zip
  9. VirtualBox Introduction: Codes to get your OS to run full screen. Intro; As far as i understood the rules i am not allowed to share links here. So i can't link the articles where i learned these things, but find it fair to say that i did not invent these tricks. I only added some extra info to make the procedure understandable for beginners as well. This is the first thing your confronted with if you install Mac OS on VirtualBox, a less then full screen resolution. So this is the first hack you want to learn ones you move into the world of Virtual Operating Systems. I bet like me for many this is the first step before you install OS X on a new partition on your hard disk. The Virtual machine you can create a full clone off, So that is a perfect way to get used to coding concerning hacintosh. I hope to smoothen your first experience while using your tool by sharing my experiences Start: VirtualBox has fixed resolution sizes, so ones you create an OS on VirtualBox then most times you start with 640x480. But you can change your code inside VirtualBox to get different screen sizes. In this step by step Tutor you will learn how you can get a full screen on your VirtualBox. There are 2 ways to do it. 1) Use one of the fixed sizes that VirtualBox offers. 2) A trick to use your own custom size. 1) Use one of the fixed sizes that VirtualBox offers. Example: cd "C:\Program Files\Oracle\Virtualbox" VBoxManage setextradata "VM Name" VBoxInternal2/EfiGopMode N Where N can be one of 0,1,2,3,4,5 referring to the 640x480, 800x600, 1024x768, 1280x1024, 1440x900, 1900x1200 0 1 2 3 4 5 NOTE: You can ONLY chose one of the above options as these are the resolutions that VBox works with. So if you have 1366x768 you need to pick one of them 1) Replace and edit the code that is named as “VM Name” to your macOS Virtual machine name, be sure it’s the same. Example: VBoxManage setextradata "Mac OS X Sierra Clone" VBoxInternal2/EfiGopMode N 2) Choose the resolution of your screen monitor from the list. To choose one just clean N and type the number of that resolution size. My size is 1366x768x32, So mine is not in the options thus i chose 3 = 1280x1024 VBoxManage setextradata "Mac OS X Sierra Clone" VBoxInternal2/EfiGopMode 3 Where N can be one of 0,1,2,3,4,5 referring to the 640x480, 800x600, 1024x768, 1280x1024, 1440x900, 1900x1200 3) Make sure VirtualBox is not still running, close it completely ! Press Windows button + X and click on Command Prompt (Admin). Admin prompt starts with C;/WINDOWS, normal prompt starts with C;/User, to know the difference. On Youtube tutors you sometimes see many replies where people can not get their OS X to install. I saw various examples where the reason was that people used as admin when normal prompt was needed. And they did it as normal prompt while admin was needed. So knowing the difference is important ! 4) Direct command prompt towards VirtualBox, So copy & paste the command to Command Prompt(CMD) then hit enter. Example: C:\WINDOWS\system32>cd "C:\Program Files\Oracle\Virtualbox" 5) Prompt will then open a second line showing that your commands are now directed towards VirtualBox. Now Copy & paste the fix screen resolution code to Command Prompt(CMD) then hit enter. Note: Be sure that you have selected a fix resolution for your monitor screen and choice the amount of N. Example: C:\Program Files\Oracle\Virtualbox>VBoxManage setextradata "Mac OS X Sierra Clone" VBoxInternal2/EfiGopMode 3 6) Enter after pasting the code to virtual-box then close all tabs. 7) Start the installed macOS Sierra virtual machine from VirtualBox. Now your screen size is at the size you entered How to set your custom resolution on VirtualBox. See Reply for Custom Size Step by Step Extra Info: I'm here to learn more about the function of bootloaders to know if they are needed when you want to add Kext [drivers mac]. And ones i get my audio running after learning how to fix it, then i will again make a step by step tutor like this. I put in these extra words to explain Why, we have to put certain code in to help you to understand. Following instructions to get it done is what we want obviously, but it is handy to know why you need to take the steps you need to take. As far as i have seen you need to patch-fix your OS every time when the OS gets updated. And then understanding why you do it is important else you need to keep asking help each time you get an update on your OS. Beginner TIPS: VirtualBox: How to put your material on the mac. The second problem you confront is that you can not drag and drop needed tools from your PC to the Mac. And you also don't have the option of using a shared folder. So how do we deal with that ? USB, in VirtualBox you can activate virtual devices. Thus you put a USB stick, or USB hdisk in your USB and look in the devices list. There you pick your usb stick and it will be mounted on your desktop. Sometimes it wont show up at your desktop, so how do you find it then ? You go to Go\Enclosing Folder, On the left you see the mounted disks or images. You go to Go\Computer and you will find your hard disk. My hard disk is not mounted on the desktop, so took me some time to find it's location haha Click on the Apple icon\System Preferences - For your system Go\Applications or Utilities for the programs Greets Passie
  10. I was woundering if anyone could help me/provide knowledge on integrating clover into VirtualBox for native OS X/USB Drive boot support. I was thinking perhaps doing it to have the first Hackintosh Virtulization program, and the nice thing is that Virtualbox supports Linux/Windows/OS X. Download links for VBox VirtualBox latest stable release sources VirtualBox Latest sources (perhaps unstable) VirtualBox SDK How to build VirtualBox How to build VirtualBox on Linux How to build VirtualBox on Windows How to Build VirtualBox on OS X
  11. Hi all... I saw a thread about getting Tiger on VirtualBox and was interested in it, so i downloaded the ISO and set it up in VirtualBox. The only problem is, it won't install. It boots the installer, but then it won't get any further than that. It either a) goes to the Apple logo with a cancel sign over it, or in verbose mode, it will stay on "still waiting for root device". Any ideas on how to fix this?
  12. I'm really a noob to this, so forgive me if I ask stupid questions. I really think I just need guidance that I'm heading in the right direction. I used Fuision71au's guide along with some others on the internet to get a Virtualbox VM up and running and imessage working using clover. I'd like to run this on more of my pc's including some AMD FX based ones. My thought was that I could boot the VM on intel, make the changes necessary for AMD and then copy it over to the AMD machine. My understanding is that I need to swap the kernel out for the AMD kernel. I have the kernel and I know it goes into /System/Library/Kernels. 1. I can't just copy the kernel in, because it tells me that the operation is not permitted. I've tried using csrutil disable booted into recovery but it doesn't stick. I'm not sure why. It reverts to enabled after reboot. Is there another way to get the Kernel copied over to /System/Library/Kernels ? 2. Assuming I can get the kernel copied over I believe I need to make some changes to config.plist. I've found this post but honestly, I'm not sure what these do. I'd like to understand what needs to be in config.plist in order to get the AMD kernel to work properly. Is there a good guide to what the AMD kernel options and requirements are? Am I on the right track? Is there any knowledge or guideance or silver bullet you could tell me to get this working? Any assistance is appreciated.
  13. Hi folks! I run El Capitan on VB by guide on this forum. Everything works great, but I'd like to do 2 more modifications and I'll be very thankful if you helped me... 1. Adding serials to SMBIOS The main reason I run virtualisation of OSX is that I want to code apps with Xcode - Xcode wants you tu sign in with your Apple ID to sign apps. I've read that in virtualisation, there are no serials/information in SMBIOS, so "Apple" device can't be verified, which outcome is you to unable to login. I found something about Clover and Clover Configurator. I even tried that, but there were just many errors and problem wasn't solved. Can someone give me step-by-step instructions how to do this? 2. Custom screen resolution I think this'll be simpler than 1. but I couldn't find any exact guide. I managed to change resolution by VBoxManage setextradata "El Capitan" VBoxInternal2/EfiGopMode N, but I'd like to have 16:9 res (1920x1080). Is there any way to do it?
  14. Hello everyone and sorry for my bad english. I have this problem whole day and I don't know what's the reason. This isn't my first time , I've installed OS X 10.6 on VirtualBox and same PC about five times, but today, every time after booting OS X , Guru Meditation screen appears and vm stops execution. Here are logs: VBox.log.1 https://mega.co.nz/#!7YJiwI7K!xkblgM0ISlKRCXSLZ4-jb-VCLfyA2mtr250uxWRHk4o VBox.log.2 https://mega.co.nz/#!3NICnQqT!Y794guxotXScb9yMxQMRwqBM3WZgrI3fsYqfJrKSTCY VBox.log.1 https://mega.co.nz/#!vFIwQRZR!XFwuX7vk0iztjYp4t9hLd_vB37seGtmd6q1d7IpSiUk Configuration: AMD Athlon II X4 631 Quad-Core Processor 2.60GHz 4GB RAM AMD Radeon HD 6570 Realtek PCIe GBE Family Controller
  15. I havent seen many threads dedicated to Oracle's VirtualBox program. I talked to a mod about creating this thread for my Work In Progress (WIP) in trying to get Snow Leopard running in a Virtual Machine environment. I have personal requirements that prevent me from using bootcamp or any other dual boot configuration, so the only way for me to get OS X running on my machine is to put it in a virtual machine. Oracle's product has gotten some pretty good reviews, and the best part about it is it's FREE! So this thread will be about my progress getting SL to run in OracleVB. For a look at the system that I'm putting it on, check this thread out. I downloaded VB, and this is tricky because it is CONSTANTLY being updated. My recommendation (and others that I have seen here and other forums) is to stick with whichever release you downloaded. Do NOT try to update after you have the VM running. From what I have read and what others have told me, its enough of a pain in the ass getting it to work in a VM, much less getting it to work in a VM that is constantly changing. When setting up VB, there are a few things you need to do: You select OS X server as an operating system type when creating a new virtual machine (I chose 64 bit because my processor is 64 bit) Choose a base memory of at least a Gigabyte. Some threads say you can get away with less - but if you are running VB on a machine with limited RAM resources, you may need to rethink that path that you are taking. Create the new virtual hard disk, and if you are not planning on importing an image from another VM vendor, then you can use the VDI option. Dynamically allocated is fine (or so I've been told) and the recommended size is 20GB. Again with regards to resources - if you are worried about space requirements, this project may not be for you. Once the VM is created, a few tweaks need to be done to that machine: In the system settings, de-select the Enable EFI option If you are going to use an .iso for your bootloader, you need to select the path to that for your image. I have redacted my .iso from the image because I am testing various Chameleon boot loaders at the moment, and I in no way want to endorse one over another. The rest of the settings are fine for now - you can always tweak them at a later time, but this gets you to the starting point. And this is where I am stuck - hence the reason why I am trying different boot loaders. I am currently testing one specifically for Snow Leopard that is quite handy, in that it doesn't require me to change out the disc midway thru the boot-up. The error that I have run into - ebios read error: media error block: #x### - has been explained on various forums as a media fail error and a disc read error. Both are brand new in my case, and I have enlisted the help of a fellow InsanelyMac user that has far more experience with VB than I have to assist me. He suggested its an issue with the .iso and gave me some suggestions to try. I'll be doing this shortly, and I will post my next update to this *WIP* page then. Thanks for reading - hope this helps others in some way. If you find an error on this page, or a better way to do something - please chime in and I'll adjust my posts accordingly. Please also be aware that since this is a Work In Progress page, you may have to keep reading down the page to find a fix to something that I did wrong previously. Once I get the whole thing ironed out, I'll make sure all the info is correct - maybe in a summary page or as a separate [how to] thread. For now - enjoy following along as I trip and stumble my way thru this experiment!
  16. As it says how do I Install? I have 6GB of Ram, Windows 8.1 Pro, 2.40 GHZ CPU speed. Thank you for your help.
  17. Hello there, I currently have Mac OS X (10.7 Mountain Lion) running under VMWare Workstation 8 on Windows 7. I have 16GB of RAM and I dedicated 4 to MacOS X At first I wasn't very happy with the video performance. But after getting some SVGA II drivers here at Insanely Mac, I reckon the video performance is alright considering is a Virtual Machine. What I am looking for is a VM that would give me a fair 2D and at least some general audio playback capability (something tells me running Logic Pro under a VM would never be a good idea). I can't stop but wonder whether VirtualBox would be better than VMWare, mainly because with virtual box there aren't any hacks I must do in the virtualization software to run Mac OS X. I mean, with VMware I had to "unlock" Mac OS X as a guest OS option. Plus, perhaps I am wrong but I believe that it would also be easier to get audio and video? working at a better performance, since I reckon that Oracle thelselves would be working to provide decent drivers for Mac OS X under Virtual Box. Before I venture into trying to run Mac OS X under VirtualBox just for the sake of comparison (and risking wasting some precious time when I could be doing something more productive, like playing The Witcher 2 or diablo 3 ) I would rather "hear" what the community here has to say. What do you guys reckon? Also I never ran ######. on my Mac OS X VM as I thought this is only really necessary in "physical" (as in non-VMs) Mac OS X installs. But I have a feeling that I might be terribly wrong Any suggestions / recommendations are greatly appreciated. I am a total "noob" in the hackintosh scene. So my appologies in advance Cheers! P.
  18. My computer config: CPU: Intel Core i7 4770 Haswell Motherboard: ASUS Z87-PLUS RAM: 16GB SSD: 256GB HDD: 3TB OS: Windows 7 Ultimate VirtualBox version: 4.3.6 r91406 Error Message: hfs: summary table not allowed on FS with block size of 2048 hfs: mounted OS X Base System on device root_device hfs: could not initialize summary table for OS X Base System Step: 1. Create virtual machine (2048MB RAM, new 20GB dynamiclly allocated VDI) 2. Untick Enable EFI 3. Choose HackBoot_Mav.iso for the DVD drive 4. Start the VM 5. Change OSXMavericks.iso for the DVD drive 6. Press F5 and press enter 7. Then the error message shown in the screenshot I have tried some method and changing the setting but it have the same error message What should I do? Thank you.
  19. OK well I'v sucseeded, i've installed leopard in virtualbox on amd the distro to use is kalyway.
  20. Hey guys so this is my first post, I apologize if I leave something out or this has been answered, but I cant seem to find it. So I have been trying to get os x 10.9.4 or later installed on my PC. Specs Windows 7 SP1 X64 AMD Phenom II X6 1055T 2.8 GHz Gigabyte GA-880GMA-UD2H DDR3 4GB Ram ATI Radeon HD 4250 AMD High Definition Audio Device I installed VMware Workstation 10 and used the Unlocker 1.3. Added the VM for OS X 10.9, Removed the "firmware = efi" when I attempt to boot using the .vmx IDE torrent "os x mavericks 10 9 retail vmware image" I get to Loading Darwin/X86 screen and it just keeps spooling. I don't know how to get past that screen and get to the installation. I installed Virtualbox 4.3.12 and used the Niresh ISO. I finally got OS X installed using the amd64 flag and added the graphics for 1080p. It runs pretty slow in Virtualbox but at least it boots. When I try to upgrade to 10.9.5 uding the app store, the purpose of having OS X is to use Xcode which needs 10.9.4+, it boots to the Guru Meditation error. I am really lost here and have been reading forums and install guides for the past week. Any help would be greatly appreciated! Thanks for everything so far guys. P.S what is the fasting more stable software to use VMware or Virtualbox? Can I install OS X 10.9.5 on either one using AMD?
  21. Hi, I'm successfully running (Niresh) Mavericks 10.9.4 in a VirtualBox VM on a Windows 8.1 host. Most things work there, so I decided to download and try to install the latest Yosemite Public Beta 2 (20 August,2014). Running the Yosemite Installer App, results in what seem successful update, but when the installer finishes and reboots, I get a crash. Shutting down the VM in the regular way and rebooting you'd think it would try to reboot in the same way, but no, instead it boot right back up into Mavericks. WTF!? I'm new to everything that is Apple so I'm really at loss here. So I tried a second method. I took the Yosemite PB2 App and made both an ISO and an DMG using detailed instructions from this site and others. I.e. Using sparse methods etc. Now I mounted either of these images as an external CD/DVD from virtual box and they appear and run in Mavericks. However, this time, when I try to run the installer I get this picture. Any ideas what's going on, and why I can run this from withing Mavericks as an installer App, but not as a ISO/DMG image? Is there a way to circumvent this?
  22. Hello, I installed Niresh's OSX Mavericks on an ASUS Laptop in the latest VirtualBox, following the detailed instructions at MacBreaker. --------------------------------------------------------------------- Hardware: ASUS N550JK Processor: Intel Core i7-4710HQ Video-1: Intel HD Graphics 4600 Video-2: NVIDIA GeForce GTX 850M Audio: Realtek High Definition Audio Memory: 16 GB DDR3 SDRAM Host OS: Windows 8.1 (64bit) Guest OS: OS X Mavericks 10.9.0 ? (Niresh Distro) VirtualBox: 4.3.14r95030 --------------------------------------------------------------------- Everything* worked pretty much flawless, by carefully setting up the VM. The only thing that doesn't work is Audio. I get weird clicking and other noises when changing and typing in terminal. I have tried changing stuff in the Audio settings, but the problem prevails and the noises change only slightly. Also at one point when trying mess with VoodooHDA settings, there must have been some kind of kernel crash as the machine suddenly refused to respond and CPU at 100%. So my first guess is that I don't have the right kernel drivers for the Audio provided by the VirtualBox machine. The second guess is that I'm just clueless as to what the correct Audio settings should be for both OSX and VB to communicate. --------------------------------------------------------------------- The VirtualBox Audio settings are: --------------------------------------------------------------------- Host Driver: Null Audio Driver * Windows DirectSound Controller: * Intel HD Audio ICH AC97 SoundBlaster16 --------------------------------------------------------------------- And on the OSX "Sound" settings side they are: --------------------------------------------------------------------- Sound Effects: Speaker (Black Unknown) * Headphones (Green Front) SPDIF-out (Black Rear) Output: Speaker (Black Unknown) Apple speaker port * Headphones (Green Front) Headphone port SPDIF-out (Black Rear) Optical digital-out port Input: Microphone (Pink Front) Microphone port SPDIF-in (Black Rear) Optical digital-in port CD (ATAPI) --------------------------------------------------------------------- And on the OSX "VoodooHDA" settings side they are: --------------------------------------------------------------------- * 1: Speaker (Green Rear) 2: Headphones (Green Front) 3: SPDIF-out (Black Rear) 4: Line-out (blue Rear) 5: Microphone (Pink Front) 6: SPDIF-in (Black Rear) 7: CD (ATAPI) * /AppleACPIPlatformExpert/PCI0@1e0000/AppleACPIPCI/HDEF@5 [ ] Use SSE2 [ ] Enhance stereo --------------------------------------------------------------------- I have no idea what would be the proper settings for this controller. Any suggestions? Please note that I'm new to OSX and have little experience and understanding of how to find/use/install Kext files and editing plists. So any help would be much appreciated. * Well, "Everything" apart file/folder and clipboard sharing, since there still are no official VB Host Additions for OSX.
  23. Hi everyone! this is my first post on the insanelymac forum! I'm trying to get mavericks running in virtualbox on a lubuntu host. My machine is an intel core i3 laptop with 4gb ram (3.6 usable) and so it struggles a bit. The problem is that even with 2984mb of ram given to the VM (bearing in mind lubuntu only needs a few hundred MB ram to run) it has periods of about 5 minutes where OS X will be unusably slow and even the mouse will only move in small jumps every 2 seconds. Then it will return to normal for 5 minutes and then it will go back to dead slow. This even happens when it's just on the desktop, doing little else. I'm considering adding more ram to make it 8gb to try and fix this problem, however, my other option is to take the HDD (80gb 5400rpm sata) from my old laptop and attach it via a usb 3 port to my i3 laptop. Then install a proper hackintosh on there (keeping my 4gb ram) instead of running a virtual machine with 8gb. (Btw. don't want to install OS X on my i3 laptop's hard drive because it's not actually mine and I don't want to mess it up). So which option would you recommend? I could do both but I'd rather just do one. Thank you!
  24. Hey guys, As with most things for us as AMD guys , it is very hard to get a virtualbox working with osx. However I did manage to get a working virtualbox installation some time ago, with this bootcd: http://www.filedropper.com/empireefi <-- EmpireEFI FOR AMD So what you are going to do : Download this EmpireEFI , Virtualbox and iATKOS S3. So you will boot the bootcd, swap the iso with iatkos iso and press f5. now select the iAtkos disc , type -v and boot it! no extra commands needed after installation, you will always have to boot the HDD through EmpireEFI. Hope this helps! Bitcore
  25. Hi. Some time ago I decided to explore Mac OS X so I decided to install Snow Leopard (10.6) on my computer. Since I wasn't serious about using it as an OS, I installed it as a virtual machine in VirtualBox under Linux (ubuntu to be precise) using the EmpireEFI4AMD BootCD and a retail DVD. It worked well so I kept the virtual machine. Later, I decided to upgrade to Mountain Lion (10.8) so I used ##### (with a custom AMD kernel) on a small VirtualBox partition I created for that and the upgrade was successful. Presently, the virtual machine works just fine (see below image), but I'd like to have the OS on my actual computer so that it runs as fast as it can. The way my system is configured is that I have a Linux partition, an HFS+ partition for OS X and another small HFS+ partition which contains the ##### installer. The grub bootloader boots Linux and the VirtualBox virtual machine is configured to directly access the two HFS+ partitions. I have a Chameleon Boot CD and when I boot the computer using it, the two HFS+ partitions are available for booting (see below image). I wanted to see if it was possible to at least get the ##### installer up and running outside of the virtual machine (it runs fine inside it) so I tried booting the installer partition with the Chameleon Boot CD using the "-v npci=0x2000" flags (without the npci flag the boot process gets stuck at "[ PCI configuration begin ]"). The below picture shows as far as I got (It gets stuck at "Still waiting for root device"). At the present, my system has one SATA drive and the latest BIOS for this motherboard does not have an enable/disable AHCI option so I placed the kexts from the following thread in /System/Library/Extensions (I also tried having them in /Extra/Extensions) but I'm still not successful: http://www.insanelymac.com/forum/topic/290644-installing-os-x-on-non-ahci-drive-laptop/ I'm wondering if there's something that I can do to further the process. Also, might it also be possible to use the OS X partition installed under VirtualBox outside of the virtual machine? Any help would be appreciated. By the way, I'm willing to use any other install method (other than the ##### method) if it also works. Thanks so much.