# Check macOS version (should be 12+)sw_vers# Check architecture (should be arm64)uname -m
# Check if CPU supports virtualization (should show vmx or svm)grep -E 'vmx|svm' /proc/cpuinfo# Check if KVM is available (should exist and be accessible)ls -l /dev/kvm# If /dev/kvm doesn't exist, load KVM modulesudo modprobe kvmsudo modprobe kvm_intel # For Intel CPUssudo modprobe kvm_amd # For AMD CPUs# Add user to kvm group (may require logout/login)sudo usermod -aG kvm $USER
# Verify you're running WSL2 (should show "2")wsl.exe -l -v# Check if KVM is availablels -l /dev/kvm# Add user to kvm groupsudo usermod -aG kvm $USER# Apply the new group membership (pick one):newgrp kvm# OR restart WSL from Windows PowerShell:# wsl.exe --shutdown# Verify group membershipid -nG | tr ' ' '\n' | grep -x kvm# Verify KVM accesspython3 -c "open('/dev/kvm','rb').close(); print('kvm ok')"
If you see “Timeout waiting for guest ready (30s)” errors, it’s likely a KVM permission issue. Ensure your user is in the kvm group and restart WSL with wsl.exe --shutdown.