From 70edc40aae9af2469cacea03381a4638ba3f18db Mon Sep 17 00:00:00 2001 From: Vitaly Date: Fri, 1 Nov 2024 22:50:33 +0100 Subject: [PATCH] Add NOTICE about kernel panic solution --- README.md | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/README.md b/README.md index 0e4400e..20d11ec 100644 --- a/README.md +++ b/README.md @@ -46,6 +46,28 @@ sudo spctl --master-disable - I'm not responsible for any problem and/or equipment damage or loss of files. - Always back up everything before any changes to your computer. +## Requirements + +Since Monterey, your host must have a working TSC (timestamp counter), because otherwise if you give the VM more than one core, macOS will observe the skew between cores and **kernel/memory panic** when it sees time ticking backwards. To check this, on Proxmox run: + +``` +dmesg | grep -i -e tsc -e clocksource +... +# for working host must be: +... +clocksource: Switched to clocksource tsc +... + +# for broken host could be: +tsc: Marking TSC unstable due to check_tsc_sync_source failed +clocksource: Switched to clocksource hpet +``` +Below is a possible workaround from here: https://www.nicksherlock.com/2022/10/installing-macos-13-ventura-on-proxmox/comment-page-1/#comment-55532 + +1. Try to turn off “ErP mode” or any C state power saving modes your BIOS supports and poweroff/poweron device (including physical cable). It could help host OS to init TSC correctly, but no guarantee. +2. Or try to activate TSC force in GRUB by adding boot flags `clocksource=tsc tsc=reliable` in the `GRUB_CMDLINE_LINUX_DEFAULT` and call `update-grub`. In this case host OS probably could work unstable in some cases. +3. Check the current TSC by call `cat /sys/devices/system/clocksource/clocksource0/current_clocksource` must be `tsc`. + ## Demonstration (in Portuguese/Brazil) https://youtu.be/dil6iRWiun0