Guests

The Guests page lists every VM and container across all your hosts, no host selection required.

The guests list

Columns include OS, host (linking to its node page), node, VMID, name, type, status, IP, cores, memory and storage. You can 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 through:

1. Placement: host, node, guest type (VM or container) and name.
2. Resources: pick a Plan to fill and lock cores/memory/disk, or go custom.
3. OS: for VMs, a cloud-init OS template from your library; for containers, a CT template and a root password.
4. Network: DHCP, or a static address allocated from an IP zone.
5. Access: assign an owner and attach their SSH keys, or paste one directly.

Tip

If at least one SSH key is attached, the root password becomes optional.

For containers, the Access step also exposes the privilege level (unprivileged, recommended) and container features: Nesting, keyctl, FUSE, and extra mount types (nfs, cifs).

Tip

Running Docker inside a container? Enable an unprivileged container with Nesting and keyctl. Nesting lets Docker and systemd run inside; keyctl is required for Docker in an unprivileged container. The same options are available on the REST API (unprivileged, nesting, keyctl, fuse, mount) — the REST API create endpoint includes a ready-to-use Docker-in-LXC example.

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 for containers, or change a VM’s password through the guest agent.
• Delete: remove a guest; a zone-allocated IP is released automatically.

Note

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 behind the scenes.

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 without a serial console 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 cover:

• Monitoring: live charts.
• Network/IPAM: an animated server-to-NIC-to-address topology.
• Console: the inline terminal or noVNC session.
• Activity: a full permanent log of the guest’s lifecycle events.
• Dangerous: 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 organized into groups (each with a name and an uploaded image), and those groups become the picker shown when creating or reinstalling a VM.

Note

Images are fetched on demand by the host agent at create/reinstall time and cleaned up immediately afterward, nothing is staged permanently, so 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 on the same settings page.

Next steps

• Networking & NAT for IP zones and exposing private guests.
• Plans & quotas for resource bundles and enforcement.
• REST API to script guest creation and power actions.