Let a node's sessions run KVM guests
Some work needs a virtual machine inside the task: the Android emulator is the usual case. That needs the host's KVM, which a node's sessions can't use until you allow it. KVM for sessions allows it for one node.
Turning it on widens what a session can reach in the host's kernel, for every node on that host, not only this one. Turn it on only for the nodes whose projects need it, and only on a host where every node is yours.
Who can do this: Requires the org admin role, on a node that runs on a host your organization owns. On any other node, including one on a machine Jaah shares between organizations, the switch is not shown.
![]()
- In the sidebar, select Directory, then the Machines tab.
- Select the node's name. Its details open beside the list.
- Select the Properties tab.
- Find KVM for sessions in the host row, after Jaah home and Auto-update. If it isn't there, this node can't use it (see above).
- Tick KVM for sessions.
- Read the Turn on KVM for sessions dialog: its sessions can run KVM guests, and every node on the host shares the risk. Select Turn on, or cancel to leave it off.
- The change applies at once, with no Save. New sessions on the node can now start KVM guests.
To turn it off, clear the tick. That applies at once too, without asking. If the change fails, the reason shows under the row and the switch stays as it was.
Related
- What a host is and how its nodes share it: How nodes work.
- Keep that work on this node: Run a project on some nodes only.
- Every field on the tab: Nodes.