troubleshooting

name	troubleshooting
description	Guide for diagnosing Nanvix build, runtime, and test failures, including cleanup and debugging workflows. Use this when asked to investigate errors or unstable behavior.

Troubleshooting Nanvix

Use this skill when the user reports problems, errors, or unexpected behavior while developing, building, or running Nanvix. This covers common failure modes and their resolutions.

Resource Leaks and Cleanup

Crashes or abnormal termination may leave stale resources. Clean them up with:

Quick Cleanup

# Remove all stale Nanvix resources.
sudo rm -rf /tmp/nvx:*
rm -rf /tmp/nanvix-test-*
sudo rm -f /tmp/*.socket

There is also a cleanup script for nanvixd resources:

./scripts/cleanup-nanvixd.sh

Resource Types

Resource	Location	Created By
Temp directories	/tmp/nvx:*	nanvixd
Test directories	/tmp/nanvix-test-*	Unit tests
Unix sockets	/tmp/*.socket	syscomm

Build Failures

Full Reset (Last Resort)

Symptom: Build or test issues persist after normal cleanup.

Fix: Perform a full cleanup, then rebuild:

./z distclean

./z build -- all

sccache Crashes

Symptom: Intermittent build failures with sccache errors.

Fix: sccache is automatically disabled for non-artifact targets. For manual builds, unset it:

./z build -- all SCCACHE=

Runtime Failures

KVM Not Available

Symptom: Could not access KVM kernel module or similar.

Fix:

sudo kvm-ok
sudo lsmod | grep kvm
sudo usermod -aG kvm $USER
newgrp kvm

Port Already in Use

Symptom: Address already in use when starting nanvixd in HTTP mode.

Fix: Kill existing processes or use a different port:

lsof -i :8080
kill <PID>
# Or use different port:
./bin/nanvixd.elf -http-addr 127.0.0.1:9090

TIME_WAIT Socket Connections

Symptom: After HTTP-mode runs, connections linger.

Fix: Check and wait for them to clear:

ss -tan | grep 8181

Tests Fail Due to Stale Resources

Symptom: CI tests fail with resource-exists or port-in-use errors.

Fix: Run the full cleanup script (see Resource Leaks section above).

Debugging

Enable Verbose Logging

# Nanvixd daemon logging.
RUST_LOG=debug ./bin/nanvixd.elf \
    -console-file /dev/stdout \
    -- ./bin/hello-rust-nostd.elf
RUST_LOG=trace ./bin/nanvixd.elf \
    -http-addr 127.0.0.1:8080

# Build with trace-level guest logging.
./z build -- all LOG_LEVEL=trace

Standalone UserVM Debugging

Bypass the full stack for low-level kernel debugging:

RUST_LOG=debug ./bin/uservm.elf \
    -kernel ./bin/kernel.elf \
    -initrd ./bin/hello-rust-nostd.elf

Check Build Errors

# Rust check with JSON output for IDE integration.
./z build -- check

Log Files

Runtime logs are stored under logs/ with timestamped directory names (e.g., logs/2026_02_24_13_04_54/).

Windows-Specific Issues

WHP Not Enabled

Symptom: UserVM fails to start with hypervisor-related errors.

Fix:

# Run in an elevated PowerShell prompt.
Enable-WindowsOptionalFeature -Online -FeatureName HypervisorPlatform -All
# Restart the machine.

Symlink Errors on Windows Clone

Symptom: Build or tool errors because Git checked out symlinks as text files.

Fix: Re-clone with Developer Mode enabled and symlinks flag:

git clone -c core.symlinks=true https://github.com/nanvix/nanvix.git

To repair an existing clone (including an optional backup of local changes):

# Optional: back up any local changes before resetting the working tree.
git status
# Either commit your work-in-progress, or stash it:
# git commit -am "WIP backup"
# git stash -u

git config core.symlinks true
git checkout -- .