Managing VMs

Every VM in Kyvenza supports a small, predictable set of lifecycle actions.

Lifecycle actions

Action	Description
Start	Boot the VM. The console becomes available once the guest is running.
Stop	Request a graceful shutdown through the guest OS.
Restart	Stop and start the VM.
Pause	Suspend the running VM. Resumes where it left off.
Clone	Make a full copy of the VM (Pro feature — see Licensing).
Delete	Remove the VM from the library. You will be asked to confirm. Kyvenza does not move VM image files to the Trash automatically — delete them manually if you no longer need them.

Actions are available from:

• The toolbar when a VM is selected.
• The right-click menu in the sidebar.
• The detail view for the current VM.

Configuration changes

Most configuration edits — CPU count, memory, disk size, networking — require the VM to be stopped. Kyvenza grays out fields that cannot be changed while running, rather than silently dropping edits.

Renaming

Double-click the VM name in the sidebar, or use the detail view's name field. Rename does not affect the underlying disk image.

Storage

All VM data lives under the storage path you chose during onboarding. You can see and change the path in Settings → General.

Moving the storage path does not migrate existing VMs automatically. To move an existing VM, stop it, quit Kyvenza, move the VM folder to the new location, and restart Kyvenza.