NodeWeaver
Prerequisites
- Access to the Sunstone (or FireEdge) web UI - typically
http://<one-ip>:9869(Sunstone) orhttp://<one-ip>:2616(FireEdge) oneadminor a user with image management and VM instantiation rights- The built
navengine.qcow2image on a host that NodeWeaver can reach (HTTP server, or the front-end host itself) - A virtual network with internet access already defined in NodeWeaver
Deployment Steps
Step 1 - Upload the image
Via Sunstone UI
- Log in to Sunstone.
- In the left sidebar go to Storage → Images.
- Click the green + button (top-right).
- Fill in the Create Image form:
- Name:
navengine - Type: OS (not Datablock, not CDROM)
- Datastore: choose your default image datastore (usually
defaultorimages) - Image location: choose Upload and select
navengine.qcow2from your workstation, or choose Provide a path and enter the absolute path on the front-end host if you have already copied the file there (faster for large images). - Format:
qcow2 - Persistent: leave unchecked - this lets you run multiple VMs from the same base image.
- Name:
- Click Create.
- The image enters LOCKED state while it transfers. Wait until the status changes to READY (refresh the Images list; takes 1–5 minutes depending on datastore speed).
Via CLI (faster for large images)
Copy the qcow2 to the NodeWeaver front-end, then:
oneimage create \
--name navengine \
--type OS \
--format qcow2 \
--datastore default \
--path /path/to/navengine.qcow2
Wait for oneimage show navengine to report STATE: READY.
Step 2 - Create a VM template
- In Sunstone go to Templates → VM Templates.
- Click + to create a new template.
General tab
| Field | Value |
|---|---|
| Name | navengine-template |
| Memory (MB) | 8192 |
| CPU (virtual) | 4 |
| vCPU | 4 |
Storage tab
- Click Add another disk.
- In the Disk 0 row:
- Image: select
navengine(the image you just uploaded) - Bus: VirtIO - open the dropdown and choose
virtio. This is critical; the defaultidewill cause the restart loop. - Cache:
writeback - IO:
threads
- Image: select
Network tab
- Click Add network interface.
- In the NIC 0 row:
- Network: select the virtual network that has internet access.
- Model: VirtIO - set this explicitly; the default varies by
NodeWeaver version and may be
e1000.
OS & CPU tab
- Expand Boot order: ensure disk0 is first (drag it to the top if needed).
- Under Machine type: enter
pc-q35-7.2(or simplyq35- NodeWeaver passes this string directly to QEMU’s-machineargument). If you leave this blank NodeWeaver usespc(i440fx) which does not support VirtIO-PCIe correctly. - Under BIOS / Firmware: select BIOS (SeaBIOS), NOT UEFI. If the field is absent the default is BIOS which is correct.
NodeWeaver raw template equivalent - if you prefer editing the template directly (Advanced / Template tab) the minimum additions are:
DISK = [ IMAGE="navengine", BUS="virtio", CACHE="writeback", IO="threads" ] NIC = [ NETWORK="<your-network>", MODEL="virtio" ] OS = [ BOOT="disk0", MACHINE="q35" ]
Context tab
NodeWeaver’s contextualization injects a cloud-init-like ISO into the VM. NavEngine uses Ignition (embedded in the OEM partition), not NodeWeaver contextualization. If the context ISO is attached NodeWeaver assigns it as a CDROM device which is harmless, but to keep the VM clean:
- Uncheck Add Network context and Add SSH key (they have no effect on a Flatcar image that ignores NodeWeaver context).
- You may leave the context block entirely blank or remove it.
Step 3 - Instantiate the VM
- In Templates → VM Templates select
navengine-template. - Click Instantiate (the play icon).
- In the dialog:
- VM name:
navengine-01(or any name) - Leave all other fields at template defaults.
- VM name:
- Click Instantiate.
The VM appears in Instances → VMs with state PENDING → PROLOG → RUNNING.
Step 4 - Monitor the boot
- In Instances → VMs click on your VM row.
- Click the Console button (VNC or SPICE icon) to open the graphical console.
Expected boot sequence (same as HC3):
Flatcar Container Linux by Kinvolk ...
First boot: allow 5–10 minutes.
If the VM reboots in a loop:
Check the console at the moment of failure. Common patterns and fixes:
| Console shows | Cause | Fix |
|---|---|---|
Kernel panic - not syncing: VFS: Unable to mount root fs | Disk bus is IDE, kernel has no IDE driver | Edit template, set Disk BUS to virtio |
dracut-emergency shell, network errors | NIC model not recognized | Edit template, set NIC MODEL to virtio |
UEFI shell prompt (Shell>) | Wrong firmware | Edit template OS section, remove UEFI firmware path, use SeaBIOS |