[GH-ISSUE #17] QEMU Agent enabled but not recognized v1.1.2

kerem commented

2026-02-26 17:43:57 +03:00

Owner

Originally created by @francio87 on GitHub (Sep 4, 2019).
Original GitHub issue: https://github.com/Corsinvest/cv4pve-autosnap/issues/17

Hi, the latest release, always show the warning of QEMU Agent not enabled, on both windows and linux VM:

VM XXX consider enabling QEMU agent see https://pve.proxmox.com/wiki/Qemu-guest-agent

VM500 - W10 Pro, Latest QEMU-GA
VM800 - Debian 10 apt'd get qemu-ga
VM900 - Ubuntu lxc container

ACTION Snap 
VMs:   all  
Label: Daily 
Keep:  7 
State: False
----- VM 500 -----
VM 500 consider enabling QEMU agent see https://pve.proxmox.com/wiki/Qemu-guest-agent
Create snapshot: autoDaily190904155355
----- VM 800 -----
VM 800 consider enabling QEMU agent see https://pve.proxmox.com/wiki/Qemu-guest-agent
Create snapshot: autoDaily190904155408
----- VM 900 -----
Create snapshot: autoDaily190904155409

EDIT:

After some digging, i've found that the error show up only if the option "Run guest-trim after clone disk" it's enabled

Originally created by @francio87 on GitHub (Sep 4, 2019). Original GitHub issue: https://github.com/Corsinvest/cv4pve-autosnap/issues/17 Hi, the latest release, always show the warning of QEMU Agent not enabled, on both windows and linux VM: > VM XXX consider enabling QEMU agent see https://pve.proxmox.com/wiki/Qemu-guest-agent VM500 - W10 Pro, Latest QEMU-GA VM800 - Debian 10 apt'd get qemu-ga VM900 - Ubuntu lxc container ``` ACTION Snap VMs: all Label: Daily Keep: 7 State: False ----- VM 500 ----- VM 500 consider enabling QEMU agent see https://pve.proxmox.com/wiki/Qemu-guest-agent Create snapshot: autoDaily190904155355 ----- VM 800 ----- VM 800 consider enabling QEMU agent see https://pve.proxmox.com/wiki/Qemu-guest-agent Create snapshot: autoDaily190904155408 ----- VM 900 ----- Create snapshot: autoDaily190904155409 ``` > EDIT: After some digging, i've found that the error show up only if the option "Run guest-trim after clone disk" it's enabled

kerem

2026-02-26 17:43:57 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 17:43:57 +03:00

Author

Owner

@franklupo commented on GitHub (Sep 4, 2019):

Hi,
I check if the "Agent" option is enabled.
What solution can there be?

best regards

@franklupo commented on GitHub (Sep 4, 2019): Hi, I check if the "Agent" option is enabled. What solution can there be? best regards

kerem commented

2026-02-26 17:43:57 +03:00

Author

Owner

@francio87 commented on GitHub (Sep 4, 2019):

hi,
to be honest i don't have idea what could be the solution, but i could help you debug it.
Btw what's the command you send to the agent to check if it's enable ?
I could try to reproduce it on proxmox host to see if it change the output when the option it's enabled / disabled.

@francio87 commented on GitHub (Sep 4, 2019): hi, to be honest i don't have idea what could be the solution, but i could help you debug it. Btw what's the command you send to the agent to check if it's enable ? I could try to reproduce it on proxmox host to see if it change the output when the option it's enabled / disabled.

kerem commented

2026-02-26 17:43:57 +03:00

Author

Owner

@franklupo commented on GitHub (Sep 5, 2019):

Hi,
i'm using API,
You can check using my other software CLI https://github.com/Corsinvest/cv4pve-cli.
Execute

cv4pve-cli --host={host} --username=root@pam --password={password} get /nodes/{node}/qemu/500/status/current

or in interactive shell mode
get /nodes/{node}/qemu/500/status/current

Check if key agent equal 1

Best regards

@franklupo commented on GitHub (Sep 5, 2019): Hi, i'm using API, You can check using my other software CLI https://github.com/Corsinvest/cv4pve-cli. Execute cv4pve-cli --host={host} --username=root@pam --password={password} get /nodes/{node}/qemu/500/status/current or in interactive shell mode get /nodes/{node}/qemu/500/status/current Check if key **agent** equal **1** Best regards

kerem commented

2026-02-26 17:43:58 +03:00

Author

Owner

@francio87 commented on GitHub (Sep 5, 2019):

Hi,
i'm using API,
You can check using my other software CLI https://github.com/Corsinvest/cv4pve-cli.
Execute

cv4pve-cli --host={host} --username=root@pam --password={password} get /nodes/{node}/qemu/500/status/current

or in interactive shell mode
get /nodes/{node}/qemu/500/status/current

Check if key agent equal 1

Best regards

Uhm, i've tried with pvesh since i'm at work right now and can't check your other software, but it seems that proxmox return the correct information via API.

** Run guest-trim after clone disk DISABLE **
root@px01:~# pvesh get /nodes/px01/qemu/610/status/current
┌───────────┬───────────────┐
│ key       │ value         │
├───────────┼───────────────┤
│ agent     │ 1             │
├───────────┼───────────────┤
│ cpus      │ 4             │
├───────────┼───────────────┤
│ ha        │ {"managed":0} │
├───────────┼───────────────┤
│ maxdisk   │ 128.00 GiB    │
├───────────┼───────────────┤
│ maxmem    │ 4.00 GiB      │
├───────────┼───────────────┤
│ name      │ W10P-CL-M     │
├───────────┼───────────────┤
│ pid       │ 4264          │
├───────────┼───────────────┤
│ qmpstatus │ running       │
├───────────┼───────────────┤
│ status    │ running       │
├───────────┼───────────────┤
│ uptime    │ 2h 58m 6s     │
├───────────┼───────────────┤
│ vmid      │ 610           │
└───────────┴───────────────┘
----- VM 610 -----
Create snapshot: autoDaily190905110121
Remove snapshot: autoDaily190904235014
-----------------------------------------------------------

** Run guest-trim after clone disk ENABLE **
root@px01:~# pvesh get /nodes/px01/qemu/610/status/current
┌───────────┬───────────────┐
│ key       │ value         │
├───────────┼───────────────┤
│ agent     │ 1             │
├───────────┼───────────────┤
│ cpus      │ 4             │
├───────────┼───────────────┤
│ ha        │ {"managed":0} │
├───────────┼───────────────┤
│ maxdisk   │ 128.00 GiB    │
├───────────┼───────────────┤
│ maxmem    │ 4.00 GiB      │
├───────────┼───────────────┤
│ name      │ W10P-CL-M     │
├───────────┼───────────────┤
│ pid       │ 10324         │
├───────────┼───────────────┤
│ qmpstatus │ running       │
├───────────┼───────────────┤
│ status    │ running       │
├───────────┼───────────────┤
│ uptime    │ 50s           │
├───────────┼───────────────┤
│ vmid      │ 610           │
└───────────┴───────────────┘

----- VM 610 -----
VM 610 consider enabling QEMU agent see https://pve.proxmox.com/wiki/Qemu-guest-agent
Create snapshot: autoDaily190905110121
Remove snapshot: autoDaily190904235014
--------------------------------------------------------------------------

Also if you compare the output in json format, you will recive the simple agent : 1 there aren't any notable difference between the enable and disable version.

https://www.diffchecker.com/lwBPWkIr

btw, can you replicate the issue ?

I'll check out cv4pve-cli as soon as i get home

Thanks

@francio87 commented on GitHub (Sep 5, 2019): > Hi, > i'm using API, > You can check using my other software CLI https://github.com/Corsinvest/cv4pve-cli. > Execute > > cv4pve-cli --host={host} --username=root@pam --password={password} get /nodes/{node}/qemu/500/status/current > > or in interactive shell mode > get /nodes/{node}/qemu/500/status/current > > Check if key **agent** equal **1** > > Best regards Uhm, i've tried with pvesh since i'm at work right now and can't check your other software, but it seems that proxmox return the correct information via API. ``` ** Run guest-trim after clone disk DISABLE ** root@px01:~# pvesh get /nodes/px01/qemu/610/status/current ┌───────────┬───────────────┐ │ key │ value │ ├───────────┼───────────────┤ │ agent │ 1 │ ├───────────┼───────────────┤ │ cpus │ 4 │ ├───────────┼───────────────┤ │ ha │ {"managed":0} │ ├───────────┼───────────────┤ │ maxdisk │ 128.00 GiB │ ├───────────┼───────────────┤ │ maxmem │ 4.00 GiB │ ├───────────┼───────────────┤ │ name │ W10P-CL-M │ ├───────────┼───────────────┤ │ pid │ 4264 │ ├───────────┼───────────────┤ │ qmpstatus │ running │ ├───────────┼───────────────┤ │ status │ running │ ├───────────┼───────────────┤ │ uptime │ 2h 58m 6s │ ├───────────┼───────────────┤ │ vmid │ 610 │ └───────────┴───────────────┘ ----- VM 610 ----- Create snapshot: autoDaily190905110121 Remove snapshot: autoDaily190904235014 ----------------------------------------------------------- ** Run guest-trim after clone disk ENABLE ** root@px01:~# pvesh get /nodes/px01/qemu/610/status/current ┌───────────┬───────────────┐ │ key │ value │ ├───────────┼───────────────┤ │ agent │ 1 │ ├───────────┼───────────────┤ │ cpus │ 4 │ ├───────────┼───────────────┤ │ ha │ {"managed":0} │ ├───────────┼───────────────┤ │ maxdisk │ 128.00 GiB │ ├───────────┼───────────────┤ │ maxmem │ 4.00 GiB │ ├───────────┼───────────────┤ │ name │ W10P-CL-M │ ├───────────┼───────────────┤ │ pid │ 10324 │ ├───────────┼───────────────┤ │ qmpstatus │ running │ ├───────────┼───────────────┤ │ status │ running │ ├───────────┼───────────────┤ │ uptime │ 50s │ ├───────────┼───────────────┤ │ vmid │ 610 │ └───────────┴───────────────┘ ----- VM 610 ----- VM 610 consider enabling QEMU agent see https://pve.proxmox.com/wiki/Qemu-guest-agent Create snapshot: autoDaily190905110121 Remove snapshot: autoDaily190904235014 -------------------------------------------------------------------------- ``` Also if you compare the output in json format, you will recive the simple agent : 1 there aren't any notable difference between the enable and disable version. https://www.diffchecker.com/lwBPWkIr btw, can you replicate the issue ? I'll check out cv4pve-cli as soon as i get home Thanks

kerem commented

2026-02-26 17:43:58 +03:00

Author

Owner

@franklupo commented on GitHub (Sep 5, 2019):

ok run command autosnap with option --debug and save (> log.txt") to file.
In output are present the password.

Send me file.

best regards

@franklupo commented on GitHub (Sep 5, 2019): ok run command autosnap with option **--debug** and save (> log.txt") to file. In output are present the password. Send me file. best regards

kerem commented

2026-02-26 17:43:58 +03:00

Author

Owner

@francio87 commented on GitHub (Sep 5, 2019):

ok run command autosnap with option --debug and save (> log.txt") to file.
In output are present the password.

Send me file.

best regards

Hi, here's the logs:

With both guest-trim enable and disable, it's a test environment, so i don't mind if the passwords are shown ;)

log_guest-trim_enable.txt
log_guest-trim_disable.txt

Best Regards

@francio87 commented on GitHub (Sep 5, 2019): > ok run command autosnap with option **--debug** and save (> log.txt") to file. > In output are present the password. > > Send me file. > > best regards Hi, here's the logs: With both guest-trim enable and disable, it's a test environment, so i don't mind if the passwords are shown ;) [log_guest-trim_enable.txt](https://github.com/Corsinvest/cv4pve-autosnap/files/3578794/log_guest-trim_enable.txt) [log_guest-trim_disable.txt](https://github.com/Corsinvest/cv4pve-autosnap/files/3578796/log_guest-trim_disable.txt) Best Regards

kerem commented

2026-02-26 17:43:58 +03:00

Author

Owner

@franklupo commented on GitHub (Sep 5, 2019):

Ok, found error.
I check angent equal "1" but the string is structured.

"agent": "1,fstrim_cloned_disks=1",

Create fix

@franklupo commented on GitHub (Sep 5, 2019): Ok, found error. I check angent equal "1" but the string is structured. > "agent": "1,fstrim_cloned_disks=1", Create fix

kerem commented

2026-02-26 17:43:58 +03:00

Author

Owner

@francio87 commented on GitHub (Sep 5, 2019):

Great!
Thanks

@francio87 commented on GitHub (Sep 5, 2019): Great! Thanks

kerem commented

2026-02-26 17:43:58 +03:00

Author

Owner

@franklupo commented on GitHub (Sep 5, 2019):

See new release 1,2.0

Best regards

@franklupo commented on GitHub (Sep 5, 2019): See new release 1,2.0 Best regards

kerem referenced this issue

2026-02-26 17:44:25 +03:00

[PR #13] [MERGED] Add quiet option #99

Rows
Columns

[GH-ISSUE #17] QEMU Agent enabled but not recognized v1.1.2 #13