Skip to content
Security hardening, live updates and lease fixes
Verlocx

Resources and disk usage

Live CPU, memory and disk resizing, behaviour settings, and an on-demand scan of what fills a disk.

Live resize

  • Open the resize dialog from the Resources tab or the resources card on Overview (vm.edit.resources).
  • Changes go straight to Proxmox. Memory and vCPU hot-plug into a running guest where the OS supports it; disks grow online.
  • Disks only grow, in steps of +10, +25, +50, +100, +150, +250 or +500 GB. Shrinking is not offered because it destroys data.
  • Lower bounds come from the template's minimums, upper bounds from the template caps and project quotas. An existing off-grid memory value stays selectable, so editing never silently changes a VM.

Behaviour settings

  • CPU type (host passthrough, kvm64, x86-64-v3) and boot order (disk, network/PXE, CD-ROM).
  • Autostart when the node boots, and the QEMU guest agent toggle.
  • Deletion protection, a server-side lock that blocks deleting the VM. See Ownership and deletion.

Scan disk usage

  1. 1Open the VM's Storage tab.
  2. 2Optionally set a root path (C:\ on Windows, / on Linux). Leave it empty to scan the system drive.
  3. 3Turn Largest files off if you only need the folder breakdown.
  4. 4Click Scan disk usage. Results appear within seconds, up to about two minutes on large disks; the agent stays responsive meanwhile.

The scan is read-only and needs only vm.view. It runs through the Verlocx agent on Windows and Linux guests, one scan per VM at a time.

Reading the result

  • Disk used is the real usage reported by the operating system. The scanned total is the sum of file sizes and is usually a little higher; compression, shadow copies and filesystem metadata explain the difference.
  • The folder breakdown is a collapsible tree; each row's fill shows its share of the parent. An “(other files & folders)” row keeps the totals adding up.
  • Largest files ranks the biggest single files with their full path.
  • A partial badge means the scan hit its time budget and returned what it had.
The scan stays on one filesystem, never follows symlinks or junctions, and counts hard links once, so a scan of / or C:\ measures that volume only.

Features on this page

  • Live resize
  • Behaviour settings
  • Disk-usage scan
More in Virtual machinesAll topics

See Verlocx in action

A 30-minute walkthrough on your use case — deployments, workflows, governance.

Hypervisor

We use your details only to handle this request — privacy policy.

Type to search the docs, the user guide, all features, the product pages and the changelog.

↑ ↓ to move↵ to openesc to close