Skip to main content

Troubleshooting

Solutions for common issues with HYPR.

Daemon Issues

Daemon Not Running

Symptom:
Linux:
macOS:

Another Instance Running

Symptom:
Solution:

Permission Denied

Symptom:
Solution: The daemon must run as root. Ensure proper service configuration:

VM Issues

VM Fails to Start

Symptom:
Possible causes:
  1. Missing kernel:
    If missing, delete and let HYPR re-download:
  2. KVM not available (Linux):
    If missing, enable virtualization in BIOS or install KVM:
  3. Hypervisor library not found (macOS): Check if libkrun-efi is installed:
    Install if missing:

VM Boot Timeout

Symptom:
Possible causes:
  1. Image entrypoint fails immediately:
    Check for application errors.
  2. Resource constraints: Increase memory:
  3. Slow disk I/O: Wait longer or check disk health.

Cannot Connect to VM Port

Symptom: Port mapping configured but connection refused. Checks:
  1. VM running:
  2. Port mapping correct:
  3. Service running in VM:
  4. Firewall blocking:

Image Issues

Image Pull Failed

Symptom:
Checks:
  1. Network connectivity:
  2. DNS resolution:
  3. Proxy settings: If behind corporate proxy, set HTTP_PROXY and HTTPS_PROXY.

Image Not Found

Symptom:
Checks:
  1. Correct image name:
  2. Tag exists: Check registry for available tags.
  3. Architecture match: Some images only have x86_64 or ARM64 variants.

Build Failed

Symptom:
Checks:
  1. View build output: Build errors are printed to stdout.
  2. Missing dependencies: Add required packages in Dockerfile:
  3. Network in build: Build VMs have no network access. All downloads must happen in the base image or use multi-stage builds.
  4. Check Dockerfile syntax:

Network Issues

No Network in VM

Symptom: VM cannot reach external networks. Linux checks:
  1. Bridge exists:
  2. TAP attached:
  3. IP forwarding enabled:
    Enable:
  4. NAT configured:
macOS checks:
  1. vmnet service running: Check System Preferences > Sharing > Internet Sharing.
  2. libkrun permissions: May need to allow in Security & Privacy settings.

DNS Not Resolving

Symptom: VM cannot resolve hostnames. Inside VM:
Fix:

VMs Cannot Communicate

Symptom: VMs on same network cannot ping each other. Checks:
  1. Same network: Ensure both VMs are on the same network (default or custom).
  2. IP addresses:
  3. Test connectivity:

Custom Network Not Working

Symptom: VMs on custom network cannot communicate. Checks:
  1. Network exists:
  2. Network configuration:
  3. VMs attached: Check compose file has correct networks: section.

Volume Issues

Volume Not Found

Symptom:
Checks:
  1. List volumes:
  2. Check name: Stack volumes are prefixed: <stack>_<volume>
  3. Check path:

Volume In Use

Symptom:
Solution:
  1. Stop the VM:
  2. Or force remove:

Permission Denied on Volume

Symptom: VM cannot read/write to volume. Checks:
  1. Host permissions:
  2. Change permissions:

GPU Issues

GPU Not Detected (Linux)

Symptom:
Checks:
  1. GPU present:
  2. IOMMU enabled:
    Add to kernel cmdline:
    • Intel: intel_iommu=on
    • AMD: amd_iommu=on
  3. VFIO modules:
    Load:

GPU Passthrough Failed

Symptom:
Solution:
  1. Unbind from current driver:
  2. Bind to vfio-pci:

Metal Not Available (macOS)

Symptom: GPU option does nothing on Apple Silicon. Checks:
  1. macOS version: Requires macOS 14 (Sonoma) or later.
  2. libkrun-efi version:
    Update: brew upgrade libkrun-efi

Compose Issues

Stack Deploy Failed

Symptom:
Checks:
  1. Compose file syntax:
  2. Image availability:
  3. Port conflicts: Check if ports are already in use.

Service Dependency Timeout

Symptom: Service waits forever for dependency. Solution: Check if dependent service actually starts:

Volumes Not Created

Symptom: Volume mount fails in compose. Checks:
  1. Volume defined: Ensure volume is in top-level volumes: section.
  2. Check volume:

Disk Space Issues

No Space Left

Symptom:
Solution:
  1. Check usage:
  2. Prune unused resources:
  3. Prune volumes:
  4. Remove specific images:

Debug Mode

Enable debug logging for detailed information:

Getting Help

  1. Check logs: journalctl -u hyprd -f (Linux) or tail -f /var/log/hypr/hyprd.log (macOS)
  2. Enable debug logging: RUST_LOG=debug
  3. Check system resources: hypr system df
  4. Report issues: https://github.com/hyprhq/hypr/issues

Common Error Messages