Starting, stopping, and rebooting a VM

Each VM row on the VMs tab has inline action buttons.

• Start / Stop — one button that flips based on the VM's current intent. If the VM is meant to be running it shows "Stop"; if it's stopped it shows "Start." Tapping it changes what the VM should be doing, and its host makes it so.
• Reboot — asks the host to cycle the VM once.

How it works under the hood:
The Cloud module is declarative. When you click Stop, you're setting the VM's desired state to "stopped" — you're not sending a live command that has to succeed right now. The host-agent on that hypervisor reconciles reality to match: it stops the VM and reports back. This is why it's safe if a host is briefly offline — the moment it's back, it catches up to whatever you asked for. Every action is idempotent, so a missed or repeated click converges to the same result.

Reading the state:
While a change is in flight the row shows the transition, e.g. "running → stopped." The colored dot tells you the observed state at a glance: green (running), grey (stopped), amber (a change in progress), red (error). See "VM and host states explained" for the full list.