Skip to main content

EmberRTOS MicroVM

The EmberRTOS MicroVM is the EmberRTOS node as a virtual machine. Two of the editions, Headless and Headless RT, are also published as virtual machine disks, so a cluster can run a full EmberRTOS node as one of its own workloads. The VM has its own kernel and its own setup, and the cluster places it the way it places any other app.

This page is the EmberRTOS side of it: what you get, how to run one, the switches, and what is proven. For installing from the App Store, see EmberRTOS MicroVM in the App Store. For where a MicroVM fits, read the white paper MicroVMs on EmberNet.

What you get​

Each MicroVM is the matching edition, built as a virtual machine disk. The Desktop edition has no MicroVM disk.

EditionKernelTuning
HeadlessGeneral-purposeNone
Headless RTReal-time, the default boot entryThe edition's tuning, with half the guest's cores isolated

Both editions keep the setup app, shown on the VM's display, and its Status screen shows the switches. arm64 is not part of this release. The arm64 disks follow as their own release.

Run one on your cluster​

Your cluster needs virtual machine support and a node with hardware virtualization and an amd64 CPU. The MicroVM apps are listed in the App Store under EmberRTOS, and installing one from there is the way to run a MicroVM. See EmberRTOS MicroVM in the App Store.

The image has a private maintenance login, which can use elevated rights for updates and restarts and is never root. Reach the VM through its console, its display for the setup app, or SSH with your key.

The real-time edition asks your cluster for dedicated CPUs and memory, and places the VM on a node set aside for real-time work. On a node that is not set aside, the VM runs, but you should not count on the full real-time guarantees. A latency figure measured inside a VM is never quoted here as a bare metal figure.

The switches​

Flux, a local cluster, and the Plasma firewall are switches, set per VM. The VM reads them on every boot, and a switch that is off stays off across a reboot while one that is on comes up again. Changing one takes effect at the VM's next boot.

SwitchDefaultWhat it does
FluxOnThe VM enrolls and joins Flux. With no credential yet it waits and says so.
Local clusterOffThe VM runs a small cluster of its own, or joins one you name. A MicroVM's local cluster stays local and is never registered with Clusters.
Plasma firewallOffThe firewall stands on a second port, the plant side.

Credentials are kept in one place for the install, and only the ones the switches that are on need. They are never written into the install's visible settings, and the VM keeps them in memory, never on its disk. A value a switch does not allow is ignored, so a typo never turns one on.

State and restarts​

A MicroVM's disk is ephemeral. Stopping or restarting the VM from the cluster gives it a fresh disk, and a reboot from inside the guest keeps it. A small state disk keeps the VM's Flux enrollment, setup state, and local cluster data, so a restart brings it back as the same node with no second credential. Turning the state disk off gives that up on purpose.

Status​

The login banner and the setup app's Status screen list the three switches and what each is doing: off, on, waiting for its credential, enrolling, starting, or failed. A shell on the VM can print the same words.

What is proven, and what is not​

What ran: each MicroVM disk is built by the release run's own steps and checked as a file, as a valid disk with the boot loader in the right place, then read back from the registry before its tag moves.

What the release notes say about booting them:

  • No 0.1.5 or 0.1.9 re-proof on a cluster. The 0.1.9 disks are the 0.1.4 disks rebuilt under the new version, with the update change in EmberRTOS Headless. The release run does not boot them in a cluster, and neither 0.1.5 nor 0.1.9 re-proved them there. The proof from the MicroVM work on 0.1.4 is the last one.
  • Rows that need Flux, a second network, or an enrolled tenant were not run. That covers a Flux enrollment that survives a restart, and the firewall on its second port.
  • Real-time latency in a VM, and on any hardware. Not measured.
  • arm64 MicroVM disks. They do not exist yet.

Next steps​