[GH-ISSUE #84] [Bug]: LXC container snapshots fail with "vmstate: property is not defined in schema" #132

New issue

Closed

opened 2026-03-13 17:17:23 +03:00 by kerem · 1 comment

kerem commented

2026-03-13 17:17:23 +03:00

Owner

Originally created by @Psycs on GitHub (Mar 8, 2026).
Original GitHub issue: https://github.com/adminsyspro/proxcenter-ui/issues/84

Bug Description

When attempting to take a snapshot of an LXC container through ProxCenter the below error is generated;

Error (snapshot): PVE 400 /nodes/proxmox01/lxc/109/snapshot: {"errors":{"vmstate":"property is not defined in schema and the schema does not allow additional properties"},"message":"Parameter verification failed.\n","data":null}

Steps to Reproduce

Add a Proxmox node with one or more LXC containers
Navigate to an LXC container in ProxCenter
Attempt to take a snapshot

Expected Behavior

Snapshot is created successfully.

Actual Behavior

Snapshot fails with a PVE 400 error:

ProxCenter Version

87bedd9

Proxmox VE Version

9.0.10

Browser

No response

Logs / Screenshots

Originally created by @Psycs on GitHub (Mar 8, 2026). Original GitHub issue: https://github.com/adminsyspro/proxcenter-ui/issues/84 ### Bug Description When attempting to take a snapshot of an LXC container through ProxCenter the below error is generated; Error (snapshot): PVE 400 /nodes/proxmox01/lxc/109/snapshot: {"errors":{"vmstate":"property is not defined in schema and the schema does not allow additional properties"},"message":"Parameter verification failed.\n","data":null} ### Steps to Reproduce 1. Add a Proxmox node with one or more LXC containers 2. Navigate to an LXC container in ProxCenter 3. Attempt to take a snapshot ### Expected Behavior Snapshot is created successfully. ### Actual Behavior Snapshot fails with a PVE 400 error: ### ProxCenter Version 87bedd9 ### Proxmox VE Version 9.0.10 ### Browser _No response_ ### Logs / Screenshots <img width="560" height="337" alt="Image" src="https://github.com/user-attachments/assets/b6b99f58-96a7-4f26-9d2c-5a13c0e297c1" />

kerem

2026-03-13 17:17:23 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-13 17:17:40 +03:00

Author

Owner

@adminsyspro commented on GitHub (Mar 8, 2026):

Thanks for the report! This is now fixed — the vmstate parameter was being sent to the Proxmox API for all guest types, but LXC containers don't support it (only QEMU VMs do).

The fix filters out the vmstate parameter for LXC snapshots on the backend, and hides the "Include RAM" toggle in the UI when working with containers.

Will be included in the next release.

@adminsyspro commented on GitHub (Mar 8, 2026): Thanks for the report! This is now fixed — the `vmstate` parameter was being sent to the Proxmox API for all guest types, but LXC containers don't support it (only QEMU VMs do). The fix filters out the `vmstate` parameter for LXC snapshots on the backend, and hides the "Include RAM" toggle in the UI when working with containers. Will be included in the next release.