OSX-KVM - Revision history

Trespaul: Updated instructions for running; add alternative to fork with flake, since it is behind upstream.

2025-11-21T14:49:57Z

Updated instructions for running; add alternative to fork with flake, since it is behind upstream.

← Older revision		Revision as of 14:49, 21 November 2025
Line 1:		Line 1:
	[https://github.com/kholia/OSX-KVM OSX-KVM] ~~allows to run~~ macOS on Linux machines.		The [https://github.com/kholia/OSX-KVM OSX-KVM] project provides a quick method of running macOS on Linux machines.

	== Installation ==		== Installation ==
Line 21:		Line 21:

	== Usage ==		== Usage ==
			Jonas Heinrich (GitHub user @onny) created a fork of the OSX-KVM repository with a flake. You can clone the fork and simply <code>nix run</code>, or, since the fork is several commits behind the original repo, you can complete the steps manually (see below), or copy the flake.nix to a clone of the original repo.

	~~{{Note\|This instruction uses~~ a ~~custom fork of~~ OSX-KVM ~~with Nix Flake support~~. ~~Hopefully these changes will soon be merged to the upstream repository.}}~~		For the forked repo, git clone and run <code>nix run</code> to prepare and run a macOS system:<syntaxhighlight lang="bash">git clone -b flake https://github.com/onny/OSX-KVM.git
			cd OSX-KVM
			nix run</syntaxhighlight>

	~~Git~~ clone the ~~project repository~~ and run <code>~~nix~~ run</code> to ~~prepare and run your MacOS system~~		Alternatively, clone the original repo, https://github.com/kholia/OSX-KVM. Then, copy over @onny's flake and <code>nix run</code>, or run the following manually. You will need the <code>python3</code> and <code>qemu</code> packages.<syntaxhighlight lang="bash">
			# to fetch BaseSystem.dmg
			python ./fetch-macOS-v2.py

	<~~syntaxHighlight lang=bash~~>		# to convert BaseSystem.dmg to BaseSystem.img
	~~git clone~~ -~~b flake~~ https://github.com/~~onny~~/OSX-KVM.~~git~~		qemu-img convert BaseSystem.dmg -O raw BaseSystem.img
	cd OSX-KVM
	~~nix run~~		# to create virtual hard drive image file mac_hdd_ng.img
	</~~syntaxHighlight~~>		qemu-img create -f qcow2 mac_hdd_ng.img 128G

			# run launch script
			# this runs qemu-system-x86_64 with the necessary arguments
			source ./OpenCore-Boot.sh
			</syntaxhighlight>In all cases, you can adjust the CPU count, memory, or other options in <code>./OpenCore-Boot.sh</code>. Currently (commit [https://github.com/kholia/OSX-KVM/tree/da4b23b5e92c5b939568700034367e8b7649fe90 da4b23b]), the script [https://github.com/kholia/OSX-KVM/blob/da4b23b5e92c5b939568700034367e8b7649fe90/OpenCore-Boot.sh#L16 recommends changing the CPU to <code>Haswell-noTSX</code> for macOS Sonoma].

	~~You may also want to adjust~~ the ~~cpu count~~/~~memory~~ in ~~<code>./OpenCore-Boot.sh</code> if your systems resources allow it~~.		On the first run, QEMU will boot into the macOS recovery image. From the boot menu, select the macOS Disk Utility and erase / format the virtual hard drive that will be used for installation (find the one with the same size as created in the script, 128GB by default).

	~~On the first run, from the boot menu, select disk utilities and erase / format the Qemu disk that will be used for installation.~~ Then choose the installer from the boot menu~~. Select~~ the previously created disk image as ~~install~~ target.		Then choose the (re-)installer from the boot menu and select the previously created disk image as the installation target. This will then download the full image of the selected macOS version.

	On the next boot you will a new boot entry containing the actual installation.		On the next boot, you will see a new boot entry containing the actual installation.

	== See also ==		== See also ==

Klinger: Category:Virtualization

2024-04-19T17:31:40Z

Category:Virtualization

← Older revision		Revision as of 17:31, 19 April 2024
Line 41:		Line 41:

	* [https://github.com/ngi-nix/OSX-KVM ngi-nix/OSX-KVM]: This implementation is based on [https://github.com/foxlet/macOS-Simple-KVM macOS-Simple-KVM], and may not be as complete or polished as [https://github.com/kholia/OSX-KVM kholia/OSX-KVM]. Usage instructions are available in the repository README.		* [https://github.com/ngi-nix/OSX-KVM ngi-nix/OSX-KVM]: This implementation is based on [https://github.com/foxlet/macOS-Simple-KVM macOS-Simple-KVM], and may not be as complete or polished as [https://github.com/kholia/OSX-KVM kholia/OSX-KVM]. Usage instructions are available in the repository README.

			[[Category:Virtualization]]

imported>Onny at 19:02, 6 January 2023

2023-01-06T19:02:07Z

← Older revision		Revision as of 19:02, 6 January 2023
Line 19:		Line 19:

	Replace <code>youruser</code> with the user name of your running system. After applying the configuration, reboot your system so the changes to the kernel modules can take effect.		Replace <code>youruser</code> with the user name of your running system. After applying the configuration, reboot your system so the changes to the kernel modules can take effect.

	~~Last but not least, configure a tap interface that will be used in macOS for networking:~~

	~~<syntaxHighlight lang=console>~~
	~~$ sudo ip tuntap add dev tap0 mode tap~~
	~~$ sudo ip link set tap0 up promisc on~~
	~~$ sudo ip link set dev virbr0 up~~
	~~$ sudo ip link set dev tap0 master virbr0~~
	~~</syntaxHighlight>~~

	== Usage ==		== Usage ==

imported>Onny at 18:54, 6 January 2023

2023-01-06T18:54:29Z

← Older revision		Revision as of 18:54, 6 January 2023
Line 36:		Line 36:

	<syntaxHighlight lang=bash>		<syntaxHighlight lang=bash>
	git clone https://github.com/onny/OSX-KVM.git		git clone -b flake https://github.com/onny/OSX-KVM.git
	cd OSX-KVM		cd OSX-KVM
	~~git checkout flake~~
	nix run		nix run
	</syntaxHighlight>		</syntaxHighlight>

imported>Onny: Page cleanup and easier setup approach

2023-01-06T18:52:38Z

Page cleanup and easier setup approach

← Older revision		Revision as of 18:52, 6 January 2023
Line 1:		Line 1:
	~~== [https://github.com/kholia/OSX-KVM kholia/OSX-KVM] ==~~

	[https://github.com/kholia/OSX-KVM OSX-KVM] allows to run macOS on Linux machines.		[https://github.com/kholia/OSX-KVM OSX-KVM] allows to run macOS on Linux machines.

	~~Use the following <code>shell.nix</code> to get all the tools required to boot OSX-KVM:~~		== Installation ==

	~~<syntaxHighlight lang~~=~~nix>~~
	~~with import <nixpkgs> {};~~
	~~mkShell {~~
	~~buildInputs~~ = [
	~~qemu~~
	~~python3~~
	~~iproute2~~
	~~# If you want to regenerate the OpenCore image you'll need the below:~~
	~~# libguestfs-with-appliance~~
	];
	}
	~~</syntaxHighlight>~~

	~~On NixOS also add the~~ following lines ~~to your <code>configuration.nix</code>:~~		Enable virtualisation support in your system configuration by adding following lines

	<syntaxHighlight lang=nix>		<syntaxHighlight lang=nix>
	{		{
	~~# this is needed to get a bridge with DHCP enabled~~
	virtualisation.libvirtd.enable = true;		virtualisation.libvirtd.enable = true;
	~~# Replace <youruser> with your actual username.~~		users.extraUsers.youruser.extraGroups = [ "libvirtd" ];
	users.extraUsers.<youruser>.extraGroups = [ "libvirtd" ];

	~~# reboot your computer after adding those lines~~
	boot.extraModprobeConfig = ''		boot.extraModprobeConfig = ''
	options kvm_intel nested=1		options kvm_intel nested=1
Line 36:		Line 18:
	</syntaxHighlight>		</syntaxHighlight>

	~~After cloning the repository use <code>./fetch-macOS.py</code> or~~ <code>~~./fetch-macOS-v2.py~~</code> ~~as described in~~ the ~~README~~		Replace <code>youruser</code> with the user name of your running system. After applying the configuration, reboot your system so the changes to the kernel modules can take effect.
	~~to download macOS~~
	~~Then do:~~

	~~<syntaxHighlight lang=console>~~
	~~$ qemu-img convert BaseSystem~~.~~dmg -O raw BaseSystem.img~~
	~~</syntaxHighlight>~~

	~~to create the base image containing~~ the ~~macOS installer~~, ~~followed by creating~~
	your ~~actual disk image where later~~ the ~~macOS will be installed~~ to:

	~~<syntaxHighlight lang=console>~~
	~~$ qemu-img create -f qcow2 mac_hdd_ng~~.~~img 128G~~
	~~</syntaxHighlight>~~

	Last but not least, configure a tap interface that will be used in macOS for networking:		Last but not least, configure a tap interface that will be used in macOS for networking:
Line 60:		Line 29:
	</syntaxHighlight>		</syntaxHighlight>

	~~Then boot~~ the system ~~with:~~		== Usage ==

			{{Note\|This instruction uses a custom fork of OSX-KVM with Nix Flake support. Hopefully these changes will soon be merged to the upstream repository.}}

			Git clone the project repository and run <code>nix run</code> to prepare and run your MacOS system

	<syntaxHighlight lang=~~console~~>		<syntaxHighlight lang=bash>
	$ ./~~OpenCore~~-~~Boot~~.sh		git clone https://github.com/onny/OSX-KVM.git
			cd OSX-KVM
			git checkout flake
			nix run
	</syntaxHighlight>		</syntaxHighlight>

Line 72:		Line 48:
	On the next boot you will a new boot entry containing the actual installation.		On the next boot you will a new boot entry containing the actual installation.

	== ~~[https://github.com/ngi-nix/OSX-KVM ngi-nix/OSX-KVM]~~ ==		== See also ==

	~~This implementation is based on [https://github.com/foxlet/macOS-Simple-KVM macOS-Simple-KVM], and may not be as complete or polished as [https://github.com/kholia/OSX-KVM kholia/OSX-KVM]~~

	Usage instructions are available in the repository README.		* [https://github.com/ngi-nix/OSX-KVM ngi-nix/OSX-KVM]: This implementation is based on [https://github.com/foxlet/macOS-Simple-KVM macOS-Simple-KVM], and may not be as complete or polished as [https://github.com/kholia/OSX-KVM kholia/OSX-KVM]. Usage instructions are available in the repository README.

imported>Fufexan: Add ngi-nix/OSX-KVM

2022-08-31T12:15:53Z

Add ngi-nix/OSX-KVM

← Older revision		Revision as of 12:15, 31 August 2022
Line 1:		Line 1:
			== [https://github.com/kholia/OSX-KVM kholia/OSX-KVM] ==

	[https://github.com/kholia/OSX-KVM OSX-KVM] allows to run macOS on Linux machines.		[https://github.com/kholia/OSX-KVM OSX-KVM] allows to run macOS on Linux machines.

Line 69:		Line 71:

	On the next boot you will a new boot entry containing the actual installation.		On the next boot you will a new boot entry containing the actual installation.

			== [https://github.com/ngi-nix/OSX-KVM ngi-nix/OSX-KVM] ==

			This implementation is based on [https://github.com/foxlet/macOS-Simple-KVM macOS-Simple-KVM], and may not be as complete or polished as [https://github.com/kholia/OSX-KVM kholia/OSX-KVM]

			Usage instructions are available in the repository README.

imported>Zeorin: Add dependency for OpenCore image regeneration script

2022-08-31T10:15:51Z

Add dependency for OpenCore image regeneration script

← Older revision		Revision as of 10:15, 31 August 2022
Line 10:		Line 10:
	python3		python3
	iproute2		iproute2
			# If you want to regenerate the OpenCore image you'll need the below:
			# libguestfs-with-appliance
	];		];
	}		}

imported>Wineee at 14:05, 3 February 2021

2021-02-03T14:05:32Z

← Older revision		Revision as of 14:05, 3 February 2021
Line 32:		Line 32:
	</syntaxHighlight>		</syntaxHighlight>

	After cloning the repository use <code>./fetch-macOS.py</code> as described in the README		After cloning the repository use <code>./fetch-macOS.py</code> or <code>./fetch-macOS-v2.py</code> as described in the README
	to download macOS		to download macOS
	Then do:		Then do:

imported>Flokli: fix typo

2020-10-09T14:05:33Z

fix typo

← Older revision		Revision as of 14:05, 9 October 2020
Line 32:		Line 32:
	</syntaxHighlight>		</syntaxHighlight>

	After ~~using~~ cloning the repository use <code>./fetch-macOS.py</code> as described in the README		After cloning the repository use <code>./fetch-macOS.py</code> as described in the README
	to download macOS		to download macOS
	~~Than~~ do:		Then do:

	<syntaxHighlight lang=console>		<syntaxHighlight lang=console>
Line 47:		Line 47:
	</syntaxHighlight>		</syntaxHighlight>

	Last but not least configure a tap interface that will be used in macOS for networking:		Last but not least, configure a tap interface that will be used in macOS for networking:

	<syntaxHighlight lang=console>		<syntaxHighlight lang=console>
Line 62:		Line 62:
	</syntaxHighlight>		</syntaxHighlight>

	You may also want to adjust the ~~increase~~ cpu count/memory in <code>./OpenCore-Boot.sh</code> if your systems resources ~~allows~~ it.		You may also want to adjust the cpu count/memory in <code>./OpenCore-Boot.sh</code> if your systems resources allow it.

	On the first run, from the boot menu, select disk utilities and erase / format the Qemu disk that will be used for installation. Then choose the installer from the boot menu. Select the previously created disk image as install target.		On the first run, from the boot menu, select disk utilities and erase / format the Qemu disk that will be used for installation. Then choose the installer from the boot menu. Select the previously created disk image as install target.

	On the next boot you will a new boot entry containing the actual installation.		On the next boot you will a new boot entry containing the actual installation.

imported>BenSchZA: Add details about erase/formatting of Qemu disk

2020-08-06T08:19:31Z

Add details about erase/formatting of Qemu disk

← Older revision		Revision as of 08:19, 6 August 2020
Line 56:		Line 56:
	</syntaxHighlight>		</syntaxHighlight>

	~~Than~~ boot the system with:		Then boot the system with:

	<syntaxHighlight lang=console>		<syntaxHighlight lang=console>
Line 62:		Line 62:
	</syntaxHighlight>		</syntaxHighlight>

	You may also want to adjust the increase cpu count/memory in <code>./OpenCore-Boot.sh</code> if your systems resources allows it. On the first run choose the installer from the boot menu. Select the previously created disk image as install target.		You may also want to adjust the increase cpu count/memory in <code>./OpenCore-Boot.sh</code> if your systems resources allows it.

			On the first run, from the boot menu, select disk utilities and erase / format the Qemu disk that will be used for installation. Then choose the installer from the boot menu. Select the previously created disk image as install target.

	On the next boot you will a new boot entry containing the actual installation.		On the next boot you will a new boot entry containing the actual installation.