Dependency failed for QEMU Guest Agent

[taich]

After I did the update to 7.4.3 one of my VM's can not start qemu-guaest-agent.

I have powered the VM off, I uninstalled and reinstalled qemu guest agent and still get this error msg.


Mar 27 11:49:49 testdns systemd[1]: Dependency failed for QEMU Guest Agent. Subject: A start job for unit qemu-guest-agent.service has failed Defined-By: systemd Support: http://www.ubuntu.com/support A start job for unit qemu-guest-agent.service has finished with a failure. The job identifier is 721 and the job result is dependency. Mar 27 11:49:49 testdns systemd[1]: qemu-guest-agent.service: Job qemu-guest-agent.service/start failed with result 'dependency'. Mar 27 11:49:49 testdns systemd[1]: dev-virtio\x2dports-org.qemu.guest_agent.0.device: Job dev-virtio\x2dports-org.qemu.guest_agent.0.device/start failed with result timeout'.

 

[fabian]

is the agent enabled in the VM config? it seems it errors out waiting for the device to communicate with the host, and that device is only added if the "Use Agent" checkbox is ticked.

 

[runningshort]

Any luck with this? I'm having the same issue on 7.4.3 with a win10 VM. The QEMU guest agent checkbox is ticked and the Virtio/qemu drivers are installed on the VM. This VM was working with the guest agent prior to the update. I destroyed and rebuilt this VM and notice the memory ballooning not working properly.

Apr 05 21:01:48 pve systemd[1]: dev-virtio\x2dports-org.qemu.guest_agent.0.device: Job dev-virtio\x2dports-org.qemu.guest_agent.0.device/start >
Apr 05 21:01:48 pve systemd[1]: Timed out waiting for device /dev/virtio-ports/org.qemu.guest_agent.0.
Subject: A start job for unit dev-virtio\x2dports-org.qemu.guest_agent.0.device has failed
Defined-By: systemd
Support: https://www.debian.org/support
A start job for unit dev-virtio\x2dports-org.qemu.guest_agent.0.device has finished with a failure.

The job identifier is 1592 and the job result is timeout.
Apr 05 21:01:48 pve systemd[1]: Dependency failed for QEMU Guest Agent.
Subject: A start job for unit qemu-guest-agent.service has failed
Defined-By: systemd
Support: https://www.debian.org/support

A start job for unit qemu-guest-agent.service has finished with a failure.

The job identifier is 1504 and the job result is dependency.
Apr 05 21:01:48 pve systemd[1]: qemu-guest-agent.service: Job qemu-guest-agent.service/start failed with result 'dependency'.
Apr 05 21:01:48 pve systemd[1]: dev-virtio\x2dports-org.qemu.guest_agent.0.device: Job dev-virtio\x2dports-org.qemu.guest_agent.0.device/start failed with result 'timeout'.

 

[Nuke Bloodaxe]

Which version of Debian, and are you using the distro-included version?
In terms of the Windows instance, which version of the QEMU iso is this?
(I'm asking, as more info = more likely people can help.)

 

[runningshort]

Which version of Debian, and are you using the distro-included version?
In terms of the Windows instance, which version of the QEMU iso is this?
(I'm asking, as more info = more likely people can help.)

Yes, using the distro version:

pve-manager/7.4-3/9002ab8a (running kernel: 5.15.104-1-pve)

QEMU iso:

virtio-win-0.1.217.iso

 

[Nuke Bloodaxe]

Okay, you could try a little experiment, make a backup of the VM beforehand.
There's a newer version of virtio-win, 0.1.229, could be worth trying.
Also, the QEMU versions can be chosen:

Make absolutely sure you've backed the VM up before you test it out.
Note: Only suggestions for areas to investigate, they may help

 

[fiona]

Hi,
@runningshort it sounds like you installed the guest agent on the Proxmox VE host. You don't need that. The guest agent is supposed to be installed in the guest only. I'd just remove the package again, to avoid the failing systemd unit. What does qm guest cmd <ID> ping give you with the VM's ID? Did you follow the instructions here: https://pve.proxmox.com/wiki/Qemu-guest-agent#Windows

 

[runningshort]

Hi,
@runningshort it sounds like you installed the guest agent on the Proxmox VE host. You don't need that. The guest agent is supposed to be installed in the guest only. I'd just remove the package again, to avoid the failing systemd unit. What does qm guest cmd <ID> ping give you with the VM's ID? Did you follow the instructions here: https://pve.proxmox.com/wiki/Qemu-guest-agent#Windows

I have removed the guest agent package from the host and rebooted the host.

qm guest cmd <ID> ping does not return anything, which I'm assuming means there are no errors.

I did follow the instructions linked for the installation. I removed the qemu guest agent from the Win10 VM and added virtio-win, 0.1.229 drivers. I re-installed the qemu guest agent and confirmed it is up via powershell.

The host sees the IP address, however the memory usage is still incorrect which is the issue I'm having as the IP has always shown:

VM:



Host:

 

[Nuke Bloodaxe]

In the performance tab, there will be a section showing if there is cached data from the disk. Now, it has to go somewhere
The idea is your processes might be taking up 25% of RAM, but where is that cached data being stored? In RAM.

So, do some quick addition and see if that is what is happening; I see this quite commonly in Linux VMs.

 

[runningshort]

In the performance tab, there will be a section showing if there is cached data from the disk. Now, it has to go somewhere
The idea is your processes might be taking up 25% of RAM, but where is that cached data being stored? In RAM.

So, do some quick addition and see if that is what is happening; I see this quite commonly in Linux VMs.

Just getting back to this, and appreciate the input so far! But cached data is not the issue here. This is a small VM only hosting a few application files that require a Windows machine.

It's just odd that this was previously working and showing the correct RAM usage with the QEMU guest agent. I destroyed the VM, updated proxmox and then recreated the new VM a few days later and just can't seem to get this working. I have other Windows machines on other nodes that are working fine, this one is just being difficult.

When I get some time later I'll create another Windows VM on this node and see if this can be duplicated. But any other troubleshooting thoughts are welcomed!

 

[LnxBil]

It's just odd that this was previously working and showing the correct RAM usage with the QEMU guest agent.

Just my two cents:
What do you mean by correct? Windows does not show the correct RAM usage, only what is used to their weird interpretation excluding cached data. PVE shows the RAM that is ACTUALLY used, which is MORE important because the limit is what PVE sees, not the lies your Windows VM tells you.