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


Forums

  • 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
    • Installation
    • Post-Installation
    • DSDT and SSDT
    • Hardware Components and Drivers
    • 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

Categories

  • 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

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 14 results

  1. OK well I'v sucseeded, i've installed leopard in virtualbox on amd the distro to use is kalyway.
  2. Bautastein

    Making Windows partition bootable

    Hi The problem is the following: I have a mid 2012 27" iMac with no SuperDrive, and would like to install Windows using dual boot. I have an ISO image of Win7. I see there's an option in Boot Camp Assistant to install it via a USB Flash Drive, but I don't have one. Since I am sick I would have to order it online, and it would take maybe a week, and I'm a little impatient. I see there is an often recommended trick of installing Windows via VMWare to the physical disk, then switch the virtual machine off before it restarts, then restart the mac and boot into the new windows Volume. I don't have VMWare Fusion, but I tried it with VirtualBox instead. I then tried to set the startup volume to the new Windows partition, in System Preferences, and restarted, and got the following message: No Bootable Device --- press any key to continue... The message is taken from memory. So, I reckon there might be three ways from here: 1) Install rEFIt. I see almost all tutorials include this. I'm very squeamish about installing software that has low-level access and makes low-level changes to the system that might have consequences like the machine not booting at all. I'm not sure how much it changes the firmware etc., the stuff that I'm squeamish about. I also couldn't quite determine from the rEFIt/rEFInd websites whether it would solve my problem, and whether it would be necessary. 2) Try installing windows again via VirtualBox, but this time give VirtualBox access to the entire disk. Gulp! I'm squeamish about that too. Until now, I have only given it access to the partition where I want Windows installed, I suspect the Windows installer actually needs to put some boot code into the MBR records too. I suspect I would have to give it access to the entire physical disk for it to work. But, as I understand it, there is a trick that Mac OS X employs to make two partition map types work together. Perhaps there might be incompatibilities that won't be handled by installing Windows via VirtualBox, so that the entire disk could be ruined (or at least the partition tables). Therefore, I thought I'd ask here first. Here is the command I used to create the raw vmdk file for VirtualBox: sudo vboxmanage internalcommands createrawvmdk -filename ./raw_hd.vmdk -rawdisk /dev/disk0 -partitions 4 By removing the last bit "-partitions 4", I'd give it access to the entire disk. 3) Get VMWare Fusion, and install Windows via it instead, like the tutorials say? Perhaps VirtualBox just ain't up to the task? Or..... maybe I should just accept that squeamishness and hackishness don't go together, and order a USB flash drive online.... Partition Inspector from the rEFIt package (which I didn't install), says: *** Report for internal hard disk *** Current GPT partition table: # Start LBA End LBA Type 1 40 409639 EFI System (FAT) 2 409640 1815536839 Mac OS X HFS+ 3 1815536840 1816806375 Mac OS X Boot 4 1816807424 1953523711 Basic Data Current MBR partition table: # A Start LBA End LBA Type 1 1 409639 ee EFI Protective 2 409640 1815536839 af Mac OS X HFS+ 3 1815536840 1816806375 ab Mac OS X Boot 4 1816807424 1953523711 87 NTFS volume set MBR contents: Boot Code: None Partition at LBA 40: Boot Code: None (Non-system disk message) File System: FAT32 Listed in GPT as partition 1, type EFI System (FAT) Partition at LBA 409640: Boot Code: None File System: HFS Extended (HFS+) Listed in GPT as partition 2, type Mac OS X HFS+ Listed in MBR as partition 2, type af Mac OS X HFS+ Partition at LBA 1815536840: Boot Code: None File System: HFS Extended (HFS+) Listed in GPT as partition 3, type Mac OS X Boot Listed in MBR as partition 3, type ab Mac OS X Boot Partition at LBA 1816807424: Boot Code: Windows BOOTMGR (Vista) File System: NTFS Listed in GPT as partition 4, type Basic Data Listed in MBR as partition 4, type 87 NTFS volume set
  3. 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
  4. Hi. First time posting here (yay welcome me) Okay, So I have decided to emulate iATKOS in virtualbox (by sun) but something is not working for me. Attached will be a photo of whats going on. My PC Specs: Win7 Home Premium 32Bit 1GB Ram 40GB HDD VM Specs: 20GB HDD Around 400-506MB Ram (Varying often) 128MB Graphics with 3D acceleration FreeBSD System. Any help appreciated By the way its iATKOS v7
  5. 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.
  6. 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?
  7. 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!
  8. 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
  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. 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.
  11. 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.
  12. 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.
  13. 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
  14. 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.
×