// Support & Feedback

Need Help with
QEMU Manager?

Found a bug, have a feature request, or can't get a VM to boot? Open an issue on our public GitHub tracker. It's where we triage everything, and where you can follow progress on a fix.

Open an Issue Browse Issues
// Channels

How to Get Help

All support runs through the qemu-manager.alephvoid.com issue tracker on GitHub. You'll need a free GitHub account to file an issue.

Report a Bug

Something not working as expected? Tell us what you did, what you saw and what you expected, plus your host OS, QEMU version and the guest architecture.

File a bug report →

Request a Feature

A device you'd like in the hardware list, a networking mode, a guest that needs special handling? Describe the use case and the problem it would solve.

Suggest a feature →

Ask a Question

Not sure whether something is a bug or a setup issue? Open an issue anyway and label it as a question. The answer will help the next person too.

Ask a question →

Never post your license key in a public issue. Issues are public. For purchase, refund or license-key problems, email support@alephvoid.com instead.
// Checklist

Before You File an Issue

A few quick checks that help us help you faster.

1

Check QEMU

Open the app's QEMU page and confirm it detects your QEMU and its version. Many "won't start" reports are a missing emulator or firmware package.

2

Search Existing Issues

Someone may have already reported it. Browse the issue tracker; a thumbs-up on an existing issue helps us prioritize.

3

Include Details

Host OS and CPU, QEMU version, app version, guest architecture, the VM's QEMU command line and the QEMU log from the VM page.

4

Submit

Open the issue on GitHub. We'll triage it and reply in the thread.

// Troubleshooting

Host Setup & Common Issues

Some features need setup on the host outside the app. These are the ones that come up most.

"QEMU not found"

QEMU isn't bundled with the app. Install it with your package manager (see Requirements), then click Re-detect on the QEMU page.

If QEMU lives somewhere unusual, set its folder in Settings.

VMs are slow / no acceleration

Acceleration only applies when the guest architecture matches the host CPU. Otherwise QEMU uses TCG emulation.

  • Linux: add yourself to the kvm group and log in again.
  • Windows: enable the Windows Hypervisor Platform feature.
  • macOS: Hypervisor.framework is used automatically.

TPM 2.0 isn't offered

Install swtpm. QEMU's Windows build has no TPM emulator backend, so TPM is unavailable on Windows hosts. TPM is offered for x86, ARM64 (virt) and POWER (pseries) guests. Windows 11 also needs UEFI firmware.

Bridged, TAP & vmnet networking

  • Bridge (Linux): allow the bridge in /etc/qemu/bridge.conf (e.g. allow br0). qemu-bridge-helper must be setuid root, which most distributions already do.
  • TAP (Linux / Windows): create the TAP device first. On Windows, install the TAP-Windows driver (e.g. from OpenVPN) and use the adapter's name.
  • vmnet (macOS): requires running QEMU as root or a binary signed with the com.apple.vm.networking entitlement.

PCI passthrough (Linux)

  • Enable VT-d / AMD-Vi and boot with intel_iommu=on (or amd_iommu=on).
  • Bind the device and the rest of its IOMMU group to vfio-pci (e.g. driverctl set-override).
  • Give your user access to /dev/vfio/<group> and raise the locked-memory limit to at least the VM's memory.

The app lists each device's driver and IOMMU group and tells you what's still missing.

USB passthrough & shared folders

  • USB on Linux: QEMU needs access to the device under /dev/bus/usb (e.g. a udev rule).
  • USB on Windows: install the WinUSB driver for the device (e.g. with Zadig).
  • virtio-fs (Linux): install virtiofsd; guests need Linux 5.4 or newer.