Guests

The guests list

The Guests page lists every VM and container across all your hosts: with its OS, host, node, name, type, status, IP, cores, memory and disk. Search, filter and sort, and select multiple guests to start, reboot, shut down or stop them in bulk.

Creating a guest

A step-by-step wizard walks you through placement (host, node, type, name), resources, OS, network and access. Pick a Plan to fill and lock the resources, or go custom. For VMs you choose a cloud-init OS template from your library; for containers you pick a template and set a root password. You can assign an owner and attach their SSH keys right in the wizard.

Day-to-day actions

• Power: start, shut down, reboot, stop, suspend and resume, with progress tracking.
• Reinstall: rebuild a guest while keeping its ID and specs (and its IP for zone-allocated guests).
• Reset password: the root password (containers), or change a VM password through the guest agent.
• Delete: remove a guest (zone IPs are released automatically).

Create, reinstall, delete and power actions run asynchronously: the panel records the action and returns instantly while a background worker performs the real Proxmox call and refreshes state.

Consoles

Open a console straight from the browser. Containers and serial-capable VMs get a crisp text terminal (xterm.js) with real copy-paste and resize; graphical VMs fall back to a noVNC screen. The connection is proxied through NexoVirt's own origin, so your Proxmox session cookie never reaches the browser.

The guest detail page

Each guest has its own page with a power-status card, live CPU / RAM / disk usage donuts, full specifications, and an owner picker. Side tabs give you live monitoring charts, a network / IPAM view with an animated topology, an inline console, a full activity log, and the “dangerous” actions (reinstall, change IP, reset password, delete). If the guest is on a plan, a Plan card shows its limits with renew / resume buttons.

OS templates & cloud images

Under Settings → OS templates you define your own cloud-init OS templates: a base cloud image plus its cloud-init configuration (user, SSH, networking, upgrades, root-SSH). Templates are organised into groups (each with a name and an uploaded image), and those groups become the picker you see when creating or reinstalling a VM.

Images are fetched on demand by the host agent at create/reinstall time and cleaned up afterwards, so nothing is staged permanently and you always get the real download result if something goes wrong. A per-template Test image URL button verifies a URL before you rely on it. Container (LXC) templates and downloadable cloud images are managed here too.