[GH-ISSUE #69] [Bug]: QEMU Guest Agent shows (Disabled) but its enabled on the PVE Hosts #84

New issue

Closed

opened 2026-03-07 19:27:23 +03:00 by kerem · 2 comments

kerem commented

2026-03-07 19:27:23 +03:00

Owner

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

Bug Description

Checking Guest Agents, all VMs show "disabled" but its actually enabled on the host itself for each VM.
Seems proxcenter is not recognizing that flag.

Steps to Reproduce

Go to VM > Options > Scroll down to QEMU Guest Agent

Expected Behavior

VMs to show that its actually enabled when it truly is.

Actual Behavior

Shows disabled.

ProxCenter Version

latest

Proxmox VE Version

latest

Browser

Chrome

Logs / Screenshots

Proxcenter Display

PVE Host

Originally created by @Trembler34 on GitHub (Mar 3, 2026). Original GitHub issue: https://github.com/adminsyspro/proxcenter-ui/issues/69 ### Bug Description Checking Guest Agents, all VMs show "disabled" but its actually enabled on the host itself for each VM. Seems proxcenter is not recognizing that flag. ### Steps to Reproduce Go to VM > Options > Scroll down to QEMU Guest Agent ### Expected Behavior VMs to show that its actually enabled when it truly is. ### Actual Behavior Shows disabled. ### ProxCenter Version latest ### Proxmox VE Version latest ### Browser Chrome ### Logs / Screenshots Proxcenter Display <img width="967" height="112" alt="Image" src="https://github.com/user-attachments/assets/bd9eefd0-1023-47ef-be30-06c3c0ac8ed6" /> PVE Host <img width="475" height="38" alt="Image" src="https://github.com/user-attachments/assets/9f745757-8a31-4ca9-b4b9-b798c8de83b3" />

kerem

2026-03-07 19:27:23 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-13 17:16:07 +03:00

Author

Owner

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

Thanks for reporting this!

Root cause identified: The guest agent field parsing only checked for the enabled=1 format, but Proxmox most commonly stores the agent config as just 1 (or 1,fstrim_cloned_disks=1, etc.). Since "1" doesn't contain the string "enabled=1", the status was always showing as Disabled.

Fix: Updated the parsing logic to also detect values starting with "1", which covers all Proxmox agent config formats:

1 → ✅ now detected
1,fstrim_cloned_disks=1 → ✅ now detected
enabled=1 → ✅ already worked
enabled=1,type=virtio → ✅ already worked

Pushed in commit 2fe90ce. The fix will be available in the next build.

@adminsyspro commented on GitHub (Mar 4, 2026): Thanks for reporting this! **Root cause identified**: The guest agent field parsing only checked for the `enabled=1` format, but Proxmox most commonly stores the agent config as just `1` (or `1,fstrim_cloned_disks=1`, etc.). Since `"1"` doesn't contain the string `"enabled=1"`, the status was always showing as Disabled. **Fix**: Updated the parsing logic to also detect values starting with `"1"`, which covers all Proxmox agent config formats: - `1` → ✅ now detected - `1,fstrim_cloned_disks=1` → ✅ now detected - `enabled=1` → ✅ already worked - `enabled=1,type=virtio` → ✅ already worked Pushed in commit 2fe90ce. The fix will be available in the next build.

kerem commented

2026-03-13 17:16:12 +03:00

Author

Owner

@Trembler34 commented on GitHub (Mar 4, 2026):

Fixed! Thank you.

@Trembler34 commented on GitHub (Mar 4, 2026): Fixed! Thank you.

kerem referenced this issue

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

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