pgs ofera un flux manual si predictibil pentru:
- suspend to disk la VM-uri QEMU aflate in rulare
- shutdown graceful la containere LXC aflate in rulare
- resume/start dupa mentenanta pe baza unui state file local
/usr/local/sbin/pgs/usr/local/lib/xdev/pve-guests-state/uninstall.sh/usr/local/share/doc/xdev/pve-guests-state/var/lib/xdev/pve-guests-state/pgs-state.json/var/lib/pve-manager/pgs-state.json/run/pgs.lockState file-ul contine:
- timestamp
- hostname
- to_resume
- was_suspended
- ct_to_start
- vm_details
- mode
- suspend_volume
- suspend_file_date
/usr/local/sbin/pgs suspend [-v] [--dry-run]
/usr/local/sbin/pgs resume [-v] [--dry-run]
/usr/local/sbin/pgs cleanup [-v] [--dry-run]
vm-*-state-suspend-YYYY-MM-DD.rawqm suspend --todisk 1 -> adaugat in to_resumeto_resumelock: suspended, vmstate: in config si un volum de saved-state rezolvabil in storagepct shutdown --timeout 120 -> adaugat in ct_to_startsuspend face merge peste state-ul existent si pastreaza intentia anterioara de to_resumesuspend_volume plus suspend_file_datedir cu content images definite in /etc/pve/storage.cfgvm-*-state-suspend-YYYY-MM-DD.rawvm-*-state-cp*.rawstate-suspend este referit de un VM valid suspendat, il pastreazastate-suspend este referit, dar VM-ul nu mai are stare valida de suspend, curata lock, vmstate si volumulstate-suspend nu mai este referit de niciun VM, il trateaza ca orphan si il stergeto_resume -> qm resumect_to_start -> pct startsuspend_volume curent nu mai corespunde cu cel din state, VM-ul este tratat ca alterat dupa salvarea state-ului si nu este auto-resumatvm-*-state-suspend-YYYY-MM-DD.rawpvecm expected 1 in fereastra de mentenanta, cand eroarea indica lipsa de quorumlock: suspended cand VM-ul este deja runningstopped: lock: suspended, vmstate: ramas in config si volume orphaned de saved-statepgsExemple:
journalctl -t pgs -n 50 --no-pager
journalctl -t pgs -f
systemd/ sunt legacy si nu fac parte din install-ul curent/etc/xdev/...