Qemu Guest Agent is not running - VM 100 qmp command 'guest-ping' failed - got timeout

[rcd]

So, another vzdump problem:

# vzdump 100 --mode suspend
INFO: starting new backup job: vzdump 100 --mode suspend
INFO: Starting Backup of VM 100 (qemu)
INFO: Backup started at 2020-01-28 19:10:11
INFO: status = running
INFO: update VM 100 : -lock backup
INFO: backup mode: suspend
INFO: ionice priority: 7
INFO: VM Name: 100
INFO: include disk 'virtio0' 'vmdata:vm-100 -disk-0' 10G
INFO: suspend vm
INFO: creating archive '/var/lib/vz/dump/vzdump-qemu-100 -2020_01_28-19_10_11.vma'
Qemu Guest Agent is not running - VM 100 qmp command 'guest-ping' failed - got timeout
INFO: skipping guest-agent 'fs-freeze', agent configured but not running?
INFO: started backup task '7f9ae009-a251-4d5e-b49d-dcf1616637aa'
INFO: status: 1% (194576384/10737418240), sparse 0% (3035136), duration 3, read/write 64/63 MB/s
INFO: status: 7% (764739584/10737418240), sparse 2% (305688576), duration 6, read/write 190/89 MB/s
INFO: status: 8% (878510080/10737418240), sparse 2% (308658176), duration 9, read/write 37/36 MB/s

But the thing is, guest agent IS installed on the VM and enabled in the Proxmox gui.

# qm agent 100 ping comes back without errors as it should.

This is not just a single VM but ALL VM on this hypervisor.

It's a newly installed hypervisor, so it has likely never worked. It's installed with ZFS with plenty of space.

# pvesm status
Name          Type     Status           Total            Used       Available        %
local          dir     active      3474117760        39195648      3434922112    1.13%
vmdata     zfspool     active      3540043983       105121775      3434922208    2.97%

What's going on?

Oh, and as a PS -- like in my other vzdump problem (that still hasn't been resolved) - why does vzdump just keep going on when it encounters a fail? If I explicitly request --mode suspend it should not just go "oh, I can't suspend, but I will keep this server down for hours while i do the dump anyway". It should fail out. This is really annoying!

 

[tom]

Your VM agent seems not working, fix it.

And if you do not want downtime, do a snapshot backup (and not suspend).

 

[tom]

or do a stop backup. (your VM is just rebootet, minimal downtime).

 

[rcd]

Uhm, ok. How do you "fix" a VM agent? It's installed ("yum install qemu-guest-agent") and reports that it was called. The caller didn't get the message though.

# systemctl status qemu-guest-agent.service
● qemu-guest-agent.service - QEMU Guest Agent
   Loaded: loaded (/usr/lib/systemd/system/qemu-guest-agent.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2020-01-28 13:34:21 EST; 1h 55min ago
 Main PID: 688 (qemu-ga)
   CGroup: /system.slice/qemu-guest-agent.service
           └─688 /usr/bin/qemu-ga --method=virtio-serial --path=/dev/virtio-ports/org.qemu.guest_agent.0 --blacklist...

Jan 28 13:34:21 100 systemd[1]: Started QEMU Guest Agent.
Jan 28 14:15:51 100 qemu-ga[688]: info: guest-ping called
...

Anyway, the snapshot option seems to work. I don't know, I kinda assumed with suspend not working, snapshot wouldn't work either.

Thanks!