One of the features required didn't come into Windows 10 until build 19619 and the nested virtualisation support for AMD didn't come in until build 19636 either, so that's a must if you are on AMD too. The insiders Fast ring which is mentioned in the pre-requisites is now the Dev channel. You'll also need to be running a windows insider build of Windows 10. If you're already running a hypervisor, it's likely this is good to go. If your CPU does support virtualization it might not be enabled in your BIOS, it's worth a check before you start. Unless you're running an Intel CPU from the early 2000s or even earlier you should be OK. One thing that's not obvious is your CPU needs to support virtualisation. I am still stunned how good the performance is having run through this! I've tried a couple of other Linux distro's too, seriously slick.īefore starting check out the requirements from the top of the "Accelerated KVM guests on WSL2" post. Then I realised, I finally had an excuse to give this a go! I've been itching to since I read - Accelerated KVM guests on WSL 2, an awesome write-up on how to run accelerated KVM guests on WSL2 from is a walkthrough of how I used the excellent work of and and got my 3 year old XPS Intel i7 to run MacOS on Windows 10! Without their writeups and scripting this post probably wouldn't exist. Unsupported configurations run the risk of not having hardware features that both macOS and Fusion expect.I needed to record a demo on a Mac, I don't own a Mac and was contemplating borrowing one from a friend. macOS Monterey is not supported by Apple on any 2012 Mac models, and Fusion is not tested or supported on Macs running on hardware/macOS combinations not supported by Apple.
If that's the case, you are running an unsupported configuration according to both Apple and VMware. According to, this CPU is used in 2012 MacBook Pros and the 2012 Mac mini.
Fusion 12.1.x is not supported on macOS 12.x Monterey per Īlso, what model Mac are you running this on? Based on the output you've provided, it shows the CPU in your Mac is an Intel i5-3210M. Ls -ald /private/var/tmp # to verify the changed permissionsĪs a first action, I would upgrade to Fusion 12.2.3. If you really want to change the permissions to what they should be (this is not necessary, though), use the following command from a Terminal session: sudo chmod 1777 /private/var/tmp The 't" or "sticky bit" permission on a directory is more of a security feature - it limits the deletion of a file in the directory to the userid that created the file, the owner of the directory, or the superuser.
You already have read/write for everyone for the directory. It doesn't immediately look like permissions on the /private/var/tmp directory are your problem.
0 kommentar(er)
