

- #RUNNING WINDOWS ON MAC FOR FREE DRIVER#
- #RUNNING WINDOWS ON MAC FOR FREE WINDOWS 10#
- #RUNNING WINDOWS ON MAC FOR FREE DOWNLOAD#
Select View>Devices by Connection in the top menu bar. Reboot, then open Device Manager in Windows. To enable Internet access, once you have opened your desktop, open up a Command Prompt terminal as Administrator: You’ll notice that Windows doesn’t have Internet access at first. Save the settings, and select Reset in the main BIOS menu to test out your new resolution. This may change in the future, but we have to use ramfb for now. It’s limited to a relatively small resolution, due to standard VGA for ARM64 not being supported, and having to use ramfb instead. Set your display resolution up to 1440x900 in Device Manager > OVMF Platform Configuration (or any other resolution you want to use). This will make it boot into its BIOS so we can configure it. When QEMU first starts up, select the window and press ESC before it starts booting. device qemu-xhci \ -device usb-kbd \ -device usb-tablet \ -drive file =disk.qcow2,if =none,id =windows \ -device nvme,drive =windows,serial = "dummyserial" \ -nic user,model =virtio \ -drive file = "virtio.iso",media =cdrom,if =none,id =drivers \ -device usb-storage,drive =drivers \ -monitor stdio \ -device ramfb \ -drive file =pflash0.img,format =raw,if =pflash,readonly =on \ -drive file =pflash1.img,format =raw,if =pflash \ Qemu-system-aarch64 \ -accel hvf \ -cpu host \ -smp 4 -m 2048 \ -M virt,highmem =off Use your favorite text editor to create start.sh:
#RUNNING WINDOWS ON MAC FOR FREE DRIVER#
Qemu-img snapshot disk.qcow2 -a SNAPSHOT_NAME to revert to a snapshot.ĭownload the LATEST VirtIO driver ISO for Windows.įinally. Qemu-img snapshot disk.qcow2 -l to list snapshots, and If something goes wrong and you need to revert to a snapshot, just do Remember to take another differently-named snapshot after installation is complete (I like to name mine clean_install).

Qemu-img snapshot disk.qcow2 -c brand_new That way, we won’t have to redownload the VHDX file. We are going to take a snapshot of our QCOW2 file, just in case anything goes wrong during installation. Once it’s done, delete the original VHDX file, as we no longer need it. Now you just wait this might take a while. Remember to change Windows.vhdx to the path to your own vhdx file. Qemu-img convert -O qcow2 Windows.vhdx disk.qcow2 We want to convert it to a QCOW2 file, so we can take snapshots of it and compress it. Now that you’ve built QEMU, the Windows VHDX is probably done downloading. You really should just skip this part.ĭd if =/dev/zero of =pflash0.img bs =1m count =64ĭd if =/dev/zero of =pflash1.img bs =1m count =64ĭd if =QEMU_EFI.fd of =pflash0.img conv =notruncĭd if =QEMU_VARS.fd of =pflash1.img conv =notrunc View optional build instructions You can still build your own QEMU if you want, but you don't really need to anymore.
#RUNNING WINDOWS ON MAC FOR FREE DOWNLOAD#
Go visit the Windows for ARM download page and sign in with a Microsoft account. It’s been merged into the main branch, woohoo! Just make sure your QEMU is up-to-date (6.2 or higher.) Updated 1/6/22: Building your own QEMU is no longer needed. While this isn’t quite as performant as paid solutions (like Parallels), it works ‘fast enough’ and is completely free. The problem is that QEMU isn’t optimized for M1 Macs, and virtualization is very slow… unless it uses MacOS’ Hypervisor.Framework. So, in order to have a working Windows environment, you have to do it all in a virtual machine.
#RUNNING WINDOWS ON MAC FOR FREE WINDOWS 10#
Running Windows 10 on M1 Mac with QEMU & Hypervisor.Framework
