Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Self-Hosting

NavEngine ships as a qcow2 disk image with Ignition embedded in the OEM partition. On first boot the image self-provisions and starts the application stack.

SSH is intentionally disabled.


Minimum VM Specification

ResourceMinimumRecommended
vCPUs48
RAM8 GB16 GB
Disk20 GB (image default)60 GB
Network1 VirtIO NIC with internet accesssame
Machine typeq35q35
FirmwareSeaBIOS (BIOS)SeaBIOS (BIOS)
Disk busVirtIOVirtIO
NIC modelVirtIOVirtIO

Why These Settings Are Required

The NavEngine image runs Flatcar Container Linux, which only includes VirtIO drivers. Four QEMU settings are non-negotiable - if any are wrong, the boot sequence fails before systemd starts and the hypervisor interprets the immediate reboot as a crash loop.

SettingRequired because
VirtIO disk busFlatcar’s kernel has no IDE or AHCI drivers. Without VirtIO the root disk is invisible and the kernel panics.
VirtIO NIC modelSame reason - the e1000 and rtl8139 emulations are absent.
q35 machine typeRequired for the PCIe bus. VirtIO-PCI devices are only enumerated correctly on q35 or newer.
SeaBIOS (BIOS, not UEFI)Flatcar’s QEMU image ships with a BIOS-mode GRUB bootloader. UEFI requires a separate EFI system partition path and different firmware.

Deployment Guides

Select the guide for your hypervisor platform:


Post-Installation Checks

Once the VM is running on either platform,access your navengine instance on:

https://<public-ip>:4200