Diagnostics & Troubleshooting

When something goes wrong, the Diagnostics view is the first place to look.

Open Diagnostics

From the main window, open Diagnostics (Help menu, or the diagnostics button in the toolbar when available).

Kyvenza collects:

• System info — chip, macOS version, free disk space at the storage path.
• Kyvenza version and build.
• Recent lifecycle events for each VM.
• The last run of the onboarding compatibility checks.

Exporting a bundle

Export produces a diagnostics bundle — a zip file with the above information plus relevant logs, safe to attach to a support ticket. It is available whenever Kyvenza is licensed or in its trial period.

Common issues

"VM won't start"

1. Confirm the VM is actually stopped (not just inactive).
2. Check free disk space at your storage path — starting a VM reserves scratch space.
3. Open Diagnostics and look for recent lifecycle errors on that VM.
4. If the error mentions Apple's Virtualization Framework, reboot the Mac and try again.

"macOS installer fails to boot"

• Confirm the IPSW is for Apple Silicon (arm64e). IPSWs for Intel Macs will not boot.
• Make sure free space at the storage path covers the restore image plus the installed disk.

"Permission denied" when creating a VM

Kyvenza needs read/write access to your chosen storage path. Open Settings → General, confirm the path, and retry. On first use with a new folder, macOS may also prompt for Full Disk Access.

Cleaning up an old Lume install

Kyvenza does not use the Lume CLI. Releases before 1.2 bundled it, and some people also installed it themselves back then. If you ran Lume's upstream installer at some point, it left an auto-updater and a LaunchAgent behind that Kyvenza never touches. To remove them:

rm -f ~/.local/bin/lume-update
crontab -l 2>/dev/null | grep -v 'lume-update' | crontab - 2>/dev/null || true
rm -f ~/Library/LaunchAgents/com.trycua.lume_updater.plist

This does not affect Kyvenza's bundled copy.

Still stuck?

Email support@kyvenza.com with:

• The Kyvenza version and build (Settings → About).
• A description of what you expected vs what happened.
• A Diagnostics export if you are on Pro, or screenshots otherwise.