Watch Windows complete the installation as if your Mac were any other PC. Reboot your Mac while holding the Option key.ģ. **If you're not quick enough, and the installation process starts in the VM, you're gonna be starting over, so pay attention**.ġ. Click "Restart" and shut off the VM right before it boots back up. When it's finished copying the files, it will reboot. Make sure to press a key to boot the installer from the DVD image.Īnd then start the Windows installation. This happens every time you reboot the Mac, and every time you shut down the VM.Ĭlick "Start" to fire up the VM. This needs to be done every time your Mac mounts the physical drive. When you add the VMDK, VBox mounts the physical drive, so we need to set the permissions again before we launch the VM. You'll notice that the size of the virtual hard disk is the same as the size of your physical disk. Set the permissions on the physical drive and the VMDK before attaching it to the virtual machine with Change the "Type" to "ICH6."Īdd an optical drive, and attach your Windows ISO to it. Open up the settings for your new VM and select "storage." Remove the default SATA storage controller, and add an IDE storage controller. After the drive is formatted and the install files are copied over, the rest of the installation is completed using the native hardware (and thus, the native onboard SATA controller), so VBox's setup becomes irrelevant. Initially, we need to attach the physical drive using the IDE controller. **Select "Do not add a virtual disk."** This is important because VirtualBox by default attaches virtual disks using a SATA controller. Open VirtualBox and create a new virtual machine. Now we are done setting up the VMDK for physical drive access. We also need to define the permissions for the VMDK file so that the VM will have access to the physical drive: We need to unmount it and repeat the permissions modification: VirtualBox will remount the disk after it has created the VMDK. VirtualBox will create a file called `Windows.vmdk` in your working directory. Sudo VBoxManage internalcommands createrawvmdk -filename "Windows.vmdk" -rawdisk /dev/disk0 This VMDK is simply a pointer to our physical drive. VMDK file that will be attached to the VM. VirtualBox comes with a nice tool that we can use called `createrawvmdk`. Next, we have to set up the correct permissions for the physical drive so that userland VirtualBox can access it. The one I am interested in using is `/dev/disk0`.
On my MacBook Pro, there are two physical SSDs. # VirtualBox needs full access to the physical drive that you plan to use.įire up Terminal and look for your physical drive's mount point using `diskutil list` Set up your Mac's secondary physical drive for access _.because we're not stuck in the 90s anymore._ See my notes down at the bottom about the "Why some Macs cannot use Boot Camp Assistant to make USB boot drive."
We can use VirtualBox to start the installation process for Windows on a physical drive, then complete the installation by booting the drive using the actual hardware (instead of the VM). # An alternative method for native installation * They can integrate with the host OS for the purposes of transferring files, running guest OS-specific applications, etc. * You can use snapshots to revert immediately back to working installations
* They can run side-by-side with macOS without partitioning, rebooting, etc. VMs are super convenient for many reasons: VMs are much more convienent for everything else. Or to be able to use 100% of the hardware resources for other applications, if you're into productivity and those things. Use VirtualBox/Parallels Desktop/VMWare Fusion and set up a virtual machine. Use source of physical media, such as a Windows install CD/DVD or USB flash drive.Ģ.
There are two easy ways to get Windows on a Mac:ġ. Windows 7 is the only one that doesn't suck XD I've tested this on Windows 7, 8, and 8.1. This guide uses Windows 10, but this applies to any version of Windows. # Installing Windows on a physical drive using VirtualBox
0 kommentar(er)
