markmorado/pvemanager
1
0
Fork 0
Code Issues Pull Requests Actions 3 Packages Projects Releases 3 Wiki Activity

fix(instances): show RAM in correct units (MiB to bytes) in config
All checks were successful
Deploy to Production / Trigger production update (push) Successful in 7s
Details

Browse Source 
VM config `memory` is in MiB but formatBytes treated it as bytes,
rendering "2 KB RAM" instead of "2 GB RAM". Convert before formatting.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
Dilshod Rasulov
2026-06-27 18:46:39 +05:00
parent 9b1000ba76
commit 1d1bd33e03
1 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
frontend/src/lib/format.ts
View File

@@ -40,8 +40,9 @@ export function vmVcpuCount(config?: { cores?: number; sockets?: number } | null
/**
* Formats a VM/LXC hardware configuration as "N vCPU / X GB RAM / Y GB".
* `memory` and `maxdisk` come from the cached instances list in bytes;
* `disk_size` (when present) is already in GB.
* `memory` comes from the Proxmox config in MiB; `maxmem` comes from the
* cluster/resources list in bytes. `maxdisk` is in bytes and `disk_size`
* (when present) is already in GB.
*/
export function formatVmConfig(vm: {
cores?: number;
@@ -52,7 +53,7 @@ export function formatVmConfig(vm: {
}): string {
const parts: string[] = [];
if (vm.cores) parts.push(`${vm.cores} vCPU`);
const memBytes = vm.memory || vm.maxmem;
const memBytes = vm.memory ? vm.memory * 1024 ** 2 : vm.maxmem;
if (memBytes) parts.push(`${formatBytes(memBytes, 0)} RAM`);
const diskGb = vm.disk_size ?? (vm.maxdisk ? Math.round(vm.maxdisk / 1024 ** 3) : 0);
if (diskGb) parts.push(`${diskGb} GB`);