Originally created by @pedroreglero on GitHub (Jun 8, 2023).
OS related issued, please help us identify the issue by posting the output of this
Linux 8fcdbf348545 5.15.90.1-microsoft-standard-WSL2 #1 SMP Fri Jan 27 02:56:13 UTC 2023 x86_64 GNU/Linux
:0
tee: /sys/module/kvm/parameters/ignore_msrs: Read-only file system
1
NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
Filesystem Size Used Avail Use% Mounted on
overlay 1007G 29G 927G 4% /
QEMU emulator version 7.1.0
Copyright (c) 2003-2022 Fabrice Bellard and the QEMU Project developers
libvirtd (libvirt) 8.9.0
total used free shared buff/cache available
Mem: 11Gi 5.2Gi 152Mi 17Mi 6.3Gi 6.2Gi
Swap: 3.0Gi 494Mi 2.5Gi
16
egrep: warning: egrep is obsolescent; using grep -E
16
crw-rw-rw- 1 arch arch 10, 232 Jun 8 12:16 /dev/kvm
total 8.0K
drwxrwxrwx 2 root root 60 Jun 8 08:34 .
drwxrwxrwt 1 root root 4.0K Jun 8 12:17 ..
srwxrwxrwx 1 arch arch 0 Jun 8 08:34 X0
arch 1066 0.0 0.0 3976 2112 pts/1 S+ 12:56 0:00 grep dockerd
sh: docker: command not found
kvm:x:992:libvirt-qemu,qemu
libvirt:x:973:
libvirt-qemu:x:970:
libvirtdbus:x:969:
When running the macOS Ventura installation, at the end I get this error:
Longer Log:
Running in Windows 11 Clean Docker installation.
Originally created by @pedroreglero on GitHub (Jun 8, 2023).
# OS related issued, please help us identify the issue by posting the output of this
Linux 8fcdbf348545 5.15.90.1-microsoft-standard-WSL2 #1 SMP Fri Jan 27 02:56:13 UTC 2023 x86_64 GNU/Linux
:0
tee: /sys/module/kvm/parameters/ignore_msrs: Read-only file system
1
NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
Filesystem Size Used Avail Use% Mounted on
overlay 1007G 29G 927G 4% /
QEMU emulator version 7.1.0
Copyright (c) 2003-2022 Fabrice Bellard and the QEMU Project developers
libvirtd (libvirt) 8.9.0
total used free shared buff/cache available
Mem: 11Gi 5.2Gi 152Mi 17Mi 6.3Gi 6.2Gi
Swap: 3.0Gi 494Mi 2.5Gi
16
egrep: warning: egrep is obsolescent; using grep -E
16
crw-rw-rw- 1 arch arch 10, 232 Jun 8 12:16 /dev/kvm
total 8.0K
drwxrwxrwx 2 root root 60 Jun 8 08:34 .
drwxrwxrwt 1 root root 4.0K Jun 8 12:17 ..
srwxrwxrwx 1 arch arch 0 Jun 8 08:34 X0
arch 1066 0.0 0.0 3976 2112 pts/1 S+ 12:56 0:00 grep dockerd
sh: docker: command not found
kvm:x:992:libvirt-qemu,qemu
libvirt:x:973:
libvirt-qemu:x:970:
libvirtdbus:x:969:
When running the macOS Ventura installation, at the end I get this error:

Longer Log:

Running in Windows 11 Clean Docker installation.
@LiushuiXiaoxia commented on GitHub (Jun 9, 2023):
me too
@LiushuiXiaoxia commented on GitHub (Jun 9, 2023):
me too


@meloandrefilipe commented on GitHub (Jun 9, 2023):
I'm getting the same issue here, already tried on Windows 11 with wsl, last version of Arch Linux and now Ubuntu 23.04. All with the same issue.
@meloandrefilipe commented on GitHub (Jun 9, 2023):
I'm getting the same issue here, already tried on Windows 11 with wsl, last version of Arch Linux and now Ubuntu 23.04. All with the same issue.

@LiushuiXiaoxia one needs to already be on MacOS to use hdiutil and thus the create_dmg_ventura.sh script
@singpolyma commented on GitHub (Jun 14, 2023):
@LiushuiXiaoxia one needs to already be on MacOS to use hdiutil and thus the `create_dmg_ventura.sh` script
@LiushuiXiaoxia commented on GitHub (Jun 14, 2023):
@LiushuiXiaoxia one needs to already be on MacOS to use hdiutil and thus the create_dmg_ventura.sh script
that is the problem.
you can install the old version first, such as macos Monterey
@LiushuiXiaoxia commented on GitHub (Jun 14, 2023):
> @LiushuiXiaoxia one needs to already be on MacOS to use hdiutil and thus the `create_dmg_ventura.sh` script
that is the problem.
you can install the old version first, such as macos Monterey
then, download OSX-KVM to create ventura.dmg (on montery )
copy ventura.dmg to linux os,
finally to install ventura on linux os (use osx-kvm, not docker-osx)
@LiushuiXiaoxia commented on GitHub (Jun 14, 2023):
> I tried that, it installs but doesn't boot #668
I mean, you install macos Monterey at first.
then, download [OSX-KVM](https://github.com/kholia/OSX-KVM) to create ventura.dmg (on montery )
copy ventura.dmg to linux os,
finally to install ventura on linux os (use osx-kvm, not docker-osx)
then, download OSX-KVM to create ventura.dmg (on montery )
copy ventura.dmg to linux os,
finally to install ventura on linux os (use osx-kvm, not docker-osx)
I already tried that and it gets past that point but still doesn't boot.
@pedroreglero commented on GitHub (Jun 14, 2023):
> > I tried that, it installs but doesn't boot #668
>
>
>
> I mean, you install macos Monterey at first.
>
>
>
> then, download [OSX-KVM](https://github.com/kholia/OSX-KVM) to create ventura.dmg (on montery )
>
>
>
> copy ventura.dmg to linux os,
>
>
>
> finally to install ventura on linux os (use osx-kvm, not docker-osx)
>
>
I already tried that and it gets past that point but still doesn't boot.
I mean, you install macos Monterey at first.
then, download OSX-KVM to create ventura.dmg (on montery )
copy ventura.dmg to linux os,
finally to install ventura on linux os (use osx-kvm, not docker-osx)
I already tried that and it gets past that point but still doesn't boot.
I tried and it was okay,
First you need to get mac_hdd_ng.img by osx-kvm
The second is to launch docker by Docker-OSX,such as
Maybe this step is a failure because the osx-kvm in sickcodes/docker-osx:naked is old
@LiushuiXiaoxia commented on GitHub (Jun 14, 2023):
> > > I tried that, it installs but doesn't boot #668
> >
> >
> > I mean, you install macos Monterey at first.
> > then, download [OSX-KVM](https://github.com/kholia/OSX-KVM) to create ventura.dmg (on montery )
> > copy ventura.dmg to linux os,
> > finally to install ventura on linux os (use osx-kvm, not docker-osx)
>
> I already tried that and it gets past that point but still doesn't boot.
I tried and it was okay,
First you need to get ` mac_hdd_ng.img ` by `osx-kvm`
The second is to ` launch docker` by ` Docker-OSX`,such as
```
docker run -it \
--device /dev/kvm \
-p 50922:10022 \
-v "${PWD}/mac_hdd_ng.img:/image" \
-v /tmp/.X11-unix:/tmp/.X11-unix \
-e "DISPLAY=${DISPLAY:-:0.0}" \
-e GENERATE_UNIQUE=true \
-e MASTER_PLIST_URL=https://raw.githubusercontent.com/sickcodes/Docker-OSX/master/custom/config-nopicker-custom.plist \
sickcodes/docker-osx:naked
```
Maybe this step is a failure because the ` osx-kvm` in `sickcodes/docker-osx:naked` is old
@pedroreglero commented on GitHub (Jun 18, 2023):
Updating to Ventura from Moajve I can't boot

@LiushuiXiaoxia commented on GitHub (Jun 19, 2023):
I use this project as the ios ci system, so I don't need a gui.
Updating to Ventura from Moajve I can't boot
just reboot ?
@LiushuiXiaoxia commented on GitHub (Jun 19, 2023):
I use this project as the ios ci system, so I don't need a gui.
> Updating to Ventura from Moajve I can't boot 
just reboot ?
I use this project as the ios ci system, so I don't need a gui.
Updating to Ventura from Moajve I can't boot
just reboot ?
The same happens every time I boot, it gets stuck there.
@pedroreglero commented on GitHub (Jun 19, 2023):
> I use this project as the ios ci system, so I don't need a gui.
>
>
>
>
>
> > Updating to Ventura from Moajve I can't boot 
>
>
>
> just reboot ?
The same happens every time I boot, it gets stuck there.
@LiushuiXiaoxia commented on GitHub (Jun 19, 2023):
you can not upgrade from Moajve (hackintosh) to Ventura,
Iook this
https://github.com/sickcodes/Docker-OSX/issues/667#issuecomment-1590510541
ni need create `ventura .img` in Moajve (macos).
and then use `osx-kvm` do upgrading (linux).
https://www.youtube.com/watch?v=_5XVYF4CwR4&ab_channel=HikmatEUstad
I downloaded the Ventura installer inside Mojave, used the create_dmg_ventura.sh script and got the Ventura.dmg file back to linux. But when I run "dmg2img -i BaseSystem.dmg BaseSystem.img" I get "ERROR: dmg image is corrupted"
@pedroreglero commented on GitHub (Jun 20, 2023):
> you can not upgrade from Moajve (hackintosh) to Ventura,
>
> Iook this
>
> [#667 (comment)](https://github.com/sickcodes/Docker-OSX/issues/667#issuecomment-1590510541)
>
> ni need create `ventura .img` in Moajve (macos). and then use `osx-kvm` do upgrading (linux).
>
> https://www.youtube.com/watch?v=_5XVYF4CwR4&ab_channel=HikmatEUstad
I downloaded the Ventura installer inside Mojave, used the create_dmg_ventura.sh script and got the Ventura.dmg file back to linux. But when I run "dmg2img -i BaseSystem.dmg BaseSystem.img" I get "ERROR: dmg image is corrupted"
I downloaded the Ventura installer inside Mojave, used the create_dmg_ventura.sh script and got the Ventura.dmg file back to linux. But when I run "dmg2img -i BaseSystem.dmg BaseSystem.img" I get "ERROR: dmg image is corrupted"
@LiushuiXiaoxia commented on GitHub (Jun 21, 2023):
> > you can not upgrade from Moajve (hackintosh) to Ventura,
> > Iook this
> > [#667 (comment)](https://github.com/sickcodes/Docker-OSX/issues/667#issuecomment-1590510541)
> > ni need create `ventura .img` in Moajve (macos). and then use `osx-kvm` do upgrading (linux).
> > https://www.youtube.com/watch?v=_5XVYF4CwR4&ab_channel=HikmatEUstad
>
> I downloaded the Ventura installer inside Mojave, used the create_dmg_ventura.sh script and got the Ventura.dmg file back to linux. But when I run "dmg2img -i BaseSystem.dmg BaseSystem.img" I get "ERROR: dmg image is corrupted"
you did not need to convert dmg to img
```shell
#-drive id=InstallMedia,if=none,file="$REPO_PATH/BaseSystem.img",format=raw
-drive id=InstallMedia,if=virtio,file="$REPO_PATH/Ventura.dmg",format=raw
```
I downloaded the Ventura installer inside Mojave, used the create_dmg_ventura.sh script and got the Ventura.dmg file back to linux. But when I run "dmg2img -i BaseSystem.dmg BaseSystem.img" I get "ERROR: dmg image is corrupted"
Had to change: "-drive id=InstallMedia,if=virtio,file="$REPO_PATH/Ventura.dmg",format=raw" to "-drive id=InstallMedia,if=none,file="$REPO_PATH/Ventura.dmg",format=raw" but after that, worked like a charm 😁.
Thanks a lot for your help!!!!
@pedroreglero commented on GitHub (Jun 23, 2023):
> > > you can not upgrade from Moajve (hackintosh) to Ventura,
> > > Iook this
> > > [#667 (comment)](https://github.com/sickcodes/Docker-OSX/issues/667#issuecomment-1590510541)
> > > ni need create `ventura .img` in Moajve (macos). and then use `osx-kvm` do upgrading (linux).
> > > https://www.youtube.com/watch?v=_5XVYF4CwR4&ab_channel=HikmatEUstad
> >
> >
> > I downloaded the Ventura installer inside Mojave, used the create_dmg_ventura.sh script and got the Ventura.dmg file back to linux. But when I run "dmg2img -i BaseSystem.dmg BaseSystem.img" I get "ERROR: dmg image is corrupted"
>
> you did not need to convert dmg to img
>
> ```shell
> #-drive id=InstallMedia,if=none,file="$REPO_PATH/BaseSystem.img",format=raw
> -drive id=InstallMedia,if=virtio,file="$REPO_PATH/Ventura.dmg",format=raw
> ```
Had to change: "-drive id=InstallMedia,if=virtio,file="$REPO_PATH/Ventura.dmg",format=raw" to "-drive id=InstallMedia,if=none,file="$REPO_PATH/Ventura.dmg",format=raw" but after that, worked like a charm 😁.
Thanks a lot for your help!!!!
I am trying to follow the steps, I was able to create image in OSX-KVM and I am lost the these steps, first step I could fire up naked container, but How to perform the second step, Could you please elaborate the step 2, add launcher.sh locally? Appreciate it. Thanks
@mingjing33us commented on GitHub (Aug 21, 2023):
> `osx-kvm` in `sickcodes/docker-osx:naked` is earlier version
>
> 1. copy origin `Launch.sh` from `naked`
>
> ```
> docker cp {containerId}:/home/arch/OSX-KVM/Launch.sh ./LaunchReal.sh
> ```
>
> 2. Add `Launch.sh` in local
>
> ```
> #!/bin/bash
> cd /home/arch
>
> # 方法1
> git clone --depth 1 --recursive https://github.com/kholia/OSX-KVM.git OSX-KVM2
> cd OSX-KVM2
>
> # 方法2
> # cp -r OSX-KVM OSX-KVM2
> # cd OSX-KVM2
> # git add .
> # git reset --hard HEAD
> # git fetch --depth 1
> # git reset --hard origin/HEAD
>
> echo "use new opencore"
> cp ../LaunchReal.sh ./LaunchReal.sh
> sh LaunchReal.sh
> ```
>
> 3. restart docker such as (replace origin Launch.sh)
>
> ```
> docker run -it \
> --device /dev/kvm \
> -p 50922:10022 \
> -v "${PWD}/mac_hdd_ng.img:/image" \
> -v /tmp/.X11-unix:/tmp/.X11-unix \
> -e "DISPLAY=${DISPLAY:-:0.0}" \
> -e GENERATE_UNIQUE=true \
> -e MASTER_PLIST_URL=https://raw.githubusercontent.com/sickcodes/Docker-OSX/master/custom/config-nopicker-custom.plist \
> -v "${PWD}/Launch.sh:/home/arch/OSX-KVM/Launch.sh" \
> -v "${PWD}/LaunchReal.sh:/home/arch/LaunchReal.sh" \
> sickcodes/docker-osx:naked
> ```
Hello
I am trying to follow the steps, I was able to create image in OSX-KVM and I am lost the these steps, first step I could fire up naked container, but How to perform the second step, Could you please elaborate the step 2, add launcher.sh locally? Appreciate it. Thanks
I am trying to follow the steps, I was able to create image in OSX-KVM and I am lost the these steps, first step I could fire up naked container, but How to perform the second step, Could you please elaborate the step 2, add launcher.sh locally? Appreciate it. Thanks
just create file Launch.sh
@LiushuiXiaoxia commented on GitHub (Aug 22, 2023):
> > `osx-kvm` in `sickcodes/docker-osx:naked` is earlier version
> >
> > 1. copy origin `Launch.sh` from `naked`
> >
> > ```
> > docker cp {containerId}:/home/arch/OSX-KVM/Launch.sh ./LaunchReal.sh
> > ```
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > 2. Add `Launch.sh` in local
> >
> > ```
> > #!/bin/bash
> > cd /home/arch
> >
> > # 方法1
> > git clone --depth 1 --recursive https://github.com/kholia/OSX-KVM.git OSX-KVM2
> > cd OSX-KVM2
> >
> > # 方法2
> > # cp -r OSX-KVM OSX-KVM2
> > # cd OSX-KVM2
> > # git add .
> > # git reset --hard HEAD
> > # git fetch --depth 1
> > # git reset --hard origin/HEAD
> >
> > echo "use new opencore"
> > cp ../LaunchReal.sh ./LaunchReal.sh
> > sh LaunchReal.sh
> > ```
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > 3. restart docker such as (replace origin Launch.sh)
> >
> > ```
> > docker run -it \
> > --device /dev/kvm \
> > -p 50922:10022 \
> > -v "${PWD}/mac_hdd_ng.img:/image" \
> > -v /tmp/.X11-unix:/tmp/.X11-unix \
> > -e "DISPLAY=${DISPLAY:-:0.0}" \
> > -e GENERATE_UNIQUE=true \
> > -e MASTER_PLIST_URL=https://raw.githubusercontent.com/sickcodes/Docker-OSX/master/custom/config-nopicker-custom.plist \
> > -v "${PWD}/Launch.sh:/home/arch/OSX-KVM/Launch.sh" \
> > -v "${PWD}/LaunchReal.sh:/home/arch/LaunchReal.sh" \
> > sickcodes/docker-osx:naked
> > ```
>
> Hello
>
> I am trying to follow the steps, I was able to create image in OSX-KVM and I am lost the these steps, first step I could fire up naked container, but How to perform the second step, Could you please elaborate the step 2, add launcher.sh locally? Appreciate it. Thanks
just create file `Launch.sh`
Hello
I am trying to follow the steps, I was able to create image in OSX-KVM and I am lost the these steps, first step I could fire up naked container, but How to perform the second step, Could you please elaborate the step 2, add launcher.sh locally? Appreciate it. Thanks
just create file Launch.sh
Thanks for your reply...
I am just stuck at create file Launch.sh
For step2 , it only create LaunchReal.sh, maybe I missed step to create the file?
That leads to the step 3
-v "${PWD}/Launch.sh:/home/arch/OSX-KVM/Launch.sh"
Current Folder, there is no Launch.sh
-v "${PWD}/LaunchReal.sh:/home/arch/LaunchReal.sh" \
Also Step 3 , restart Docker, following command will create a new container
docker run -it \
Any suggestions? Appreciate your help and time. Thanks!
@mingjing33us commented on GitHub (Aug 23, 2023):
> > > `osx-kvm` in `sickcodes/docker-osx:naked` is earlier version
> > >
> > > 1. copy origin `Launch.sh` from `naked`
> > >
> > > ```
> > > docker cp {containerId}:/home/arch/OSX-KVM/Launch.sh ./LaunchReal.sh
> > > ```
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > 2. Add `Launch.sh` in local
> > >
> > > ```
> > > #!/bin/bash
> > > cd /home/arch
> > >
> > > # 方法1
> > > git clone --depth 1 --recursive https://github.com/kholia/OSX-KVM.git OSX-KVM2
> > > cd OSX-KVM2
> > >
> > > # 方法2
> > > # cp -r OSX-KVM OSX-KVM2
> > > # cd OSX-KVM2
> > > # git add .
> > > # git reset --hard HEAD
> > > # git fetch --depth 1
> > > # git reset --hard origin/HEAD
> > >
> > > echo "use new opencore"
> > > cp ../LaunchReal.sh ./LaunchReal.sh
> > > sh LaunchReal.sh
> > > ```
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > 3. restart docker such as (replace origin Launch.sh)
> > >
> > > ```
> > > docker run -it \
> > > --device /dev/kvm \
> > > -p 50922:10022 \
> > > -v "${PWD}/mac_hdd_ng.img:/image" \
> > > -v /tmp/.X11-unix:/tmp/.X11-unix \
> > > -e "DISPLAY=${DISPLAY:-:0.0}" \
> > > -e GENERATE_UNIQUE=true \
> > > -e MASTER_PLIST_URL=https://raw.githubusercontent.com/sickcodes/Docker-OSX/master/custom/config-nopicker-custom.plist \
> > > -v "${PWD}/Launch.sh:/home/arch/OSX-KVM/Launch.sh" \
> > > -v "${PWD}/LaunchReal.sh:/home/arch/LaunchReal.sh" \
> > > sickcodes/docker-osx:naked
> > > ```
> >
> >
> > Hello
> > I am trying to follow the steps, I was able to create image in OSX-KVM and I am lost the these steps, first step I could fire up naked container, but How to perform the second step, Could you please elaborate the step 2, add launcher.sh locally? Appreciate it. Thanks
>
> just create file `Launch.sh`
Thanks for your reply...
I am just stuck at create file Launch.sh
For step2 , it only create LaunchReal.sh, maybe I missed step to create the file?
That leads to the step 3
-v "${PWD}/Launch.sh:/home/arch/OSX-KVM/Launch.sh" \
Current Folder, there is no Launch.sh
-v "${PWD}/LaunchReal.sh:/home/arch/LaunchReal.sh" \
Also Step 3 , restart Docker, following command will create a new container
docker run -it \
Any suggestions? Appreciate your help and time. Thanks!
Thanks for the detailed information, I was able to follow your instruction to boot up the system. Thanks again!
@mingjing33us commented on GitHub (Aug 29, 2023):
> ./OpenCore-Boot.sh
Thanks for the detailed information, I was able to follow your instruction to boot up the system. Thanks again!
I used the OSX-KVM repository following the documentation to install Ventura. I had to use the following tweaks in the provided OpenCore-Boot.sh to get things running:
a. set ALLOCATED_RAM=8192
b. set CPU_CORES=1, CPU_SOCKETS=1 and CPU_THREADS=1 (yep it's going to be slow)
c. and set the CPU to Haswell-noTSX (Penryn is the default)
For some reason in that setup I never could increase the number of cores withouth the VM crashing (or hanging). So I tried it with sickcodes naked image where it works without problems:
Copy resulting mac_hdd_ng.img use nakedinstructions to mount it as per documentation.
a. additionally set environment variable CPU=Haswell-noTSX
Works on fine on my machine(tm)!
EDIT: A few runs later I found out that when my machine booted and had an unstable tsc, multi-core support wouldn't work. Check sudo dmesg -T | grep -i -e tsc -e clocksource which should give clocksource: Switched to clocksource tsc. Otherwise a cold boot might help.
@stonemaster commented on GitHub (Oct 18, 2023):
Some notes on how I got Ventura running locally:
1. I used the [OSX-KVM repository](https://github.com/kholia/OSX-KVM) following the documentation to install Ventura. I had to use the following tweaks in the provided `OpenCore-Boot.sh` to get things running:
a. set `ALLOCATED_RAM=8192`
b. set `CPU_CORES=1`, `CPU_SOCKETS=1` and `CPU_THREADS=1` (yep it's going to be slow)
c. and set the CPU to `Haswell-noTSX` (`Penryn` is the default)
For some reason in that setup I never could increase the number of cores withouth the VM crashing (or hanging). So I tried it with sickcodes `naked` image where it works without problems:
2. Copy resulting `mac_hdd_ng.img` use `naked`instructions to mount it as per documentation.
a. additionally set environment variable `CPU=Haswell-noTSX`
Works on fine on my machine(tm)!
EDIT: A few runs later I found out that when my machine booted and had an unstable tsc, **multi-core** support wouldn't work. Check `sudo dmesg -T | grep -i -e tsc -e clocksource` which should give ` clocksource: Switched to clocksource tsc`. Otherwise a cold boot might help.
1. I used the [OSX-KVM repository](https://github.com/kholia/OSX-KVM) following the documentation to install Ventura. I had to use the following tweaks in the provided `OpenCore-Boot.sh` to get things running:
a. set `ALLOCATED_RAM=8192`
b. set `CPU_CORES=1`, `CPU_SOCKETS=1` and `CPU_THREADS=1` (yep it's going to be slow)
c. and set the CPU to `Haswell-noTSX` (`Penryn` is the default)
For some reason in that setup I never could increase the number of cores withouth the VM crashing (or hanging). So I tried it with sickcodes naked image where it works without problems:
2. Copy resulting `mac_hdd_ng.img` use `naked`instructions to mount it as per documentation.
a. additionally set environment variable `CPU=Haswell-noTSX`
Works on fine on my machine(tm)!
EDIT: A few runs later I found out that when my machine booted and had an unstable tsc, multi-core support wouldn't work. Check sudo dmesg -T | grep -i -e tsc -e clocksource which should give clocksource: Switched to clocksource tsc. Otherwise a cold boot might help.
Just set CPU to Haswell-noTSX (Penryn is the default), I can boot into Sonoma! Thanks for your advice.
@MockyBang commented on GitHub (Nov 26, 2023):
> Some notes on how I got Ventura running locally:
>
> 1. I used the [OSX-KVM repository](https://github.com/kholia/OSX-KVM) following the documentation to install Ventura. I had to use the following tweaks in the provided `OpenCore-Boot.sh` to get things running:
> a. set `ALLOCATED_RAM=8192`
> b. set `CPU_CORES=1`, `CPU_SOCKETS=1` and `CPU_THREADS=1` (yep it's going to be slow)
> c. and set the CPU to `Haswell-noTSX` (`Penryn` is the default)
>
>
> For some reason in that setup I never could increase the number of cores withouth the VM crashing (or hanging). So I tried it with sickcodes `naked` image where it works without problems:
>
> 2. Copy resulting `mac_hdd_ng.img` use `naked`instructions to mount it as per documentation.
> a. additionally set environment variable `CPU=Haswell-noTSX`
>
>
> Works on fine on my machine(tm)!
>
> EDIT: A few runs later I found out that when my machine booted and had an unstable tsc, **multi-core** support wouldn't work. Check `sudo dmesg -T | grep -i -e tsc -e clocksource` which should give ` clocksource: Switched to clocksource tsc`. Otherwise a cold boot might help.
Just set CPU to `Haswell-noTSX` (`Penryn` is the default), I can boot into Sonoma! Thanks for your advice.
I used the OSX-KVM repository following the documentation to install Ventura. I had to use the following tweaks in the provided OpenCore-Boot.sh to get things running:
a. set ALLOCATED_RAM=8192
b. set CPU_CORES=1, CPU_SOCKETS=1 and CPU_THREADS=1 (yep it's going to be slow)
c. and set the CPU to Haswell-noTSX (Penryn is the default)
For some reason in that setup I never could increase the number of cores withouth the VM crashing (or hanging). So I tried it with sickcodes naked image where it works without problems:
Copy resulting mac_hdd_ng.img use nakedinstructions to mount it as per documentation.
a. additionally set environment variable CPU=Haswell-noTSX
Works on fine on my machine(tm)!
EDIT: A few runs later I found out that when my machine booted and had an unstable tsc, multi-core support wouldn't work. Check sudo dmesg -T | grep -i -e tsc -e clocksource which should give clocksource: Switched to clocksource tsc. Otherwise a cold boot might help.
Thanks, I couldn't boot the VM untill I set the CPU to 1 core/socket/thread. Hope someone will find a workaround :/
@awsms commented on GitHub (Jan 10, 2024):
> Some notes on how I got Ventura running locally:
>
> 1. I used the [OSX-KVM repository](https://github.com/kholia/OSX-KVM) following the documentation to install Ventura. I had to use the following tweaks in the provided `OpenCore-Boot.sh` to get things running:
> a. set `ALLOCATED_RAM=8192`
> b. set `CPU_CORES=1`, `CPU_SOCKETS=1` and `CPU_THREADS=1` (yep it's going to be slow)
> c. and set the CPU to `Haswell-noTSX` (`Penryn` is the default)
>
> For some reason in that setup I never could increase the number of cores withouth the VM crashing (or hanging). So I tried it with sickcodes `naked` image where it works without problems:
>
> 2. Copy resulting `mac_hdd_ng.img` use `naked`instructions to mount it as per documentation.
> a. additionally set environment variable `CPU=Haswell-noTSX`
>
> Works on fine on my machine(tm)!
>
> EDIT: A few runs later I found out that when my machine booted and had an unstable tsc, **multi-core** support wouldn't work. Check `sudo dmesg -T | grep -i -e tsc -e clocksource` which should give ` clocksource: Switched to clocksource tsc`. Otherwise a cold boot might help.
Thanks, I couldn't boot the VM untill I set the CPU to 1 core/socket/thread. Hope someone will find a workaround :/
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @pedroreglero on GitHub (Jun 8, 2023).
OS related issued, please help us identify the issue by posting the output of this
Linux 8fcdbf348545 5.15.90.1-microsoft-standard-WSL2 #1 SMP Fri Jan 27 02:56:13 UTC 2023 x86_64 GNU/Linux
:0
tee: /sys/module/kvm/parameters/ignore_msrs: Read-only file system
1
NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
Filesystem Size Used Avail Use% Mounted on
overlay 1007G 29G 927G 4% /
QEMU emulator version 7.1.0
Copyright (c) 2003-2022 Fabrice Bellard and the QEMU Project developers
libvirtd (libvirt) 8.9.0
total used free shared buff/cache available
Mem: 11Gi 5.2Gi 152Mi 17Mi 6.3Gi 6.2Gi
Swap: 3.0Gi 494Mi 2.5Gi
16
egrep: warning: egrep is obsolescent; using grep -E
16
crw-rw-rw- 1 arch arch 10, 232 Jun 8 12:16 /dev/kvm
total 8.0K
drwxrwxrwx 2 root root 60 Jun 8 08:34 .
drwxrwxrwt 1 root root 4.0K Jun 8 12:17 ..
srwxrwxrwx 1 arch arch 0 Jun 8 08:34 X0
arch 1066 0.0 0.0 3976 2112 pts/1 S+ 12:56 0:00 grep dockerd
sh: docker: command not found
kvm:x:992:libvirt-qemu,qemu
libvirt:x:973:
libvirt-qemu:x:970:
libvirtdbus:x:969:
When running the macOS Ventura installation, at the end I get this error:
Longer Log:
Running in Windows 11 Clean Docker installation.
@pedroreglero commented on GitHub (Jun 8, 2023):
Installation works fine for macOS Monterey
@LiushuiXiaoxia commented on GitHub (Jun 9, 2023):
me too
@singpolyma commented on GitHub (Jun 9, 2023):
yes, I get this same
@meloandrefilipe commented on GitHub (Jun 9, 2023):
I'm getting the same issue here, already tried on Windows 11 with wsl, last version of Arch Linux and now Ubuntu 23.04. All with the same issue.

@djpfs commented on GitHub (Jun 10, 2023):
same error here, i'm using ubuntu 22.04
@LiushuiXiaoxia commented on GitHub (Jun 14, 2023):
use offline install maby be success.
1: download macos 13, https://mrmacintosh.com/macos-ventura-13-full-installer-database-download-directly-from-apple/
2: clone this repo, https://github.com/kholia/OSX-KVM
3: make ventura img by
sh create_dmg_ventura.sh4: repace
BaseSystem.imgtoVentura.dmginOpenCore-Boot.sh5:
./OpenCore-Boot.shto install, may be alos fail, just retry@singpolyma commented on GitHub (Jun 14, 2023):
@LiushuiXiaoxia one needs to already be on MacOS to use hdiutil and thus the
create_dmg_ventura.shscript@LiushuiXiaoxia commented on GitHub (Jun 14, 2023):
that is the problem.
you can install the old version first, such as macos Monterey
@singpolyma commented on GitHub (Jun 14, 2023):
I tried that, it installs but doesn't boot #668
@LiushuiXiaoxia commented on GitHub (Jun 14, 2023):
I mean, you install macos Monterey at first.
then, download OSX-KVM to create ventura.dmg (on montery )
copy ventura.dmg to linux os,
finally to install ventura on linux os (use osx-kvm, not docker-osx)
@pedroreglero commented on GitHub (Jun 14, 2023):
I already tried that and it gets past that point but still doesn't boot.
@LiushuiXiaoxia commented on GitHub (Jun 14, 2023):
I tried and it was okay,
First you need to get
mac_hdd_ng.imgbyosx-kvmThe second is to
launch dockerbyDocker-OSX,such asMaybe this step is a failure because the
osx-kvminsickcodes/docker-osx:nakedis old@LiushuiXiaoxia commented on GitHub (Jun 15, 2023):
osx-kvminsickcodes/docker-osx:nakedis earlier versionLaunch.shfromnakedLaunch.shin local@pedroreglero commented on GitHub (Jun 17, 2023):
Thanks for the help, I get a black screen when booting.
Can you do a complete explanation on how to run that? I think I might be missing steps.
Greetings.
@pedroreglero commented on GitHub (Jun 18, 2023):
Updating to Ventura from Moajve I can't boot

@LiushuiXiaoxia commented on GitHub (Jun 19, 2023):
I use this project as the ios ci system, so I don't need a gui.
just reboot ?
@pedroreglero commented on GitHub (Jun 19, 2023):
The same happens every time I boot, it gets stuck there.
@LiushuiXiaoxia commented on GitHub (Jun 19, 2023):
you can not upgrade from Moajve (hackintosh) to Ventura,
Iook this
https://github.com/sickcodes/Docker-OSX/issues/667#issuecomment-1590510541
ni need create
ventura .imgin Moajve (macos).and then use
osx-kvmdo upgrading (linux).https://www.youtube.com/watch?v=_5XVYF4CwR4&ab_channel=HikmatEUstad
@pedroreglero commented on GitHub (Jun 20, 2023):
I downloaded the Ventura installer inside Mojave, used the create_dmg_ventura.sh script and got the Ventura.dmg file back to linux. But when I run "dmg2img -i BaseSystem.dmg BaseSystem.img" I get "ERROR: dmg image is corrupted"
@LiushuiXiaoxia commented on GitHub (Jun 21, 2023):
you did not need to convert dmg to img
@pedroreglero commented on GitHub (Jun 23, 2023):
Had to change: "-drive id=InstallMedia,if=virtio,file="$REPO_PATH/Ventura.dmg",format=raw" to "-drive id=InstallMedia,if=none,file="$REPO_PATH/Ventura.dmg",format=raw" but after that, worked like a charm 😁.
Thanks a lot for your help!!!!
@LiushuiXiaoxia commented on GitHub (Jun 24, 2023):
😆
@jordankoehn commented on GitHub (Jun 25, 2023):
Confirmed workaround by using offline install @LiushuiXiaoxia
@LiushuiXiaoxia commented on GitHub (Jun 26, 2023):
😄
@mingjing33us commented on GitHub (Aug 21, 2023):
Hello
I am trying to follow the steps, I was able to create image in OSX-KVM and I am lost the these steps, first step I could fire up naked container, but How to perform the second step, Could you please elaborate the step 2, add launcher.sh locally? Appreciate it. Thanks
@LiushuiXiaoxia commented on GitHub (Aug 22, 2023):
just create file
Launch.sh@mingjing33us commented on GitHub (Aug 23, 2023):
Thanks for your reply...
I am just stuck at create file Launch.sh
For step2 , it only create LaunchReal.sh, maybe I missed step to create the file?
That leads to the step 3
-v "${PWD}/Launch.sh:/home/arch/OSX-KVM/Launch.sh"
Current Folder, there is no Launch.sh
-v "${PWD}/LaunchReal.sh:/home/arch/LaunchReal.sh" \
Also Step 3 , restart Docker, following command will create a new container
docker run -it \
Any suggestions? Appreciate your help and time. Thanks!
@LiushuiXiaoxia commented on GitHub (Aug 23, 2023):
Linux 系统上创建一个空的文件夹,如
test-osx使用 终端进入
test-osx文件夹正常启动Docker实例,然后从实例中复制 Launch.sh 到本地 Linux 机器上,然后重命名为 ./LaunchReal.sh
docker cp {containerId}:/home/arch/OSX-KVM/Launch.sh ./LaunchReal.sh在
test-osx文件中,使用终端新建一个 Launch.sh 的文件,并把以下内容复制到文件中@mingjing33us commented on GitHub (Aug 29, 2023):
Thanks for the detailed information, I was able to follow your instruction to boot up the system. Thanks again!
@stonemaster commented on GitHub (Oct 18, 2023):
Some notes on how I got Ventura running locally:
OpenCore-Boot.shto get things running:a. set
ALLOCATED_RAM=8192b. set
CPU_CORES=1,CPU_SOCKETS=1andCPU_THREADS=1(yep it's going to be slow)c. and set the CPU to
Haswell-noTSX(Penrynis the default)For some reason in that setup I never could increase the number of cores withouth the VM crashing (or hanging). So I tried it with sickcodes
nakedimage where it works without problems:mac_hdd_ng.imgusenakedinstructions to mount it as per documentation.a. additionally set environment variable
CPU=Haswell-noTSXWorks on fine on my machine(tm)!
EDIT: A few runs later I found out that when my machine booted and had an unstable tsc, multi-core support wouldn't work. Check
sudo dmesg -T | grep -i -e tsc -e clocksourcewhich should giveclocksource: Switched to clocksource tsc. Otherwise a cold boot might help.@MockyBang commented on GitHub (Nov 26, 2023):
Just set CPU to
Haswell-noTSX(Penrynis the default), I can boot into Sonoma! Thanks for your advice.@awsms commented on GitHub (Jan 10, 2024):
Thanks, I couldn't boot the VM untill I set the CPU to 1 core/socket/thread. Hope someone will find a workaround :/
@LesterKraft commented on GitHub (May 12, 2024):
The following settings helped me(ryzen 5 3550h ram:2x8g):