Dependency failed for QEMU Guest Agent

CCWTech

Member
Mar 3, 2020
49
3
13
52
I'm trying to use the QEMU guest agent in a headless Debain 10 server. I am getting this error: Dependency failed for QEMU Guest Agent

Can anyone help please?
 

Fabian_E

Proxmox Staff Member
Staff member
Aug 1, 2019
1,810
320
88
Hi,
where exactly does this error message show up/what command did you use?
 

CCWTech

Member
Mar 3, 2020
49
3
13
52
root@backupprox:~# apt-get install qemu-guest-agent Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: qemu-guest-agent 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 256 kB of archives. After this operation, 723 kB of additional disk space will be used. Get:1 http://security.debian.org buster/updates/main amd64 qemu-guest-agent amd64 1:3.1+dfsg-8+deb10u8 [256 kB] Fetched 256 kB in 1s (281 kB/s) Selecting previously unselected package qemu-guest-agent. (Reading database ... 44064 files and directories currently installed.) Preparing to unpack .../qemu-guest-agent_1%3a3.1+dfsg-8+deb10u8_amd64.deb ... Unpacking qemu-guest-agent (1:3.1+dfsg-8+deb10u8) ... Setting up qemu-guest-agent (1:3.1+dfsg-8+deb10u8) ... Processing triggers for man-db (2.8.5-2) ... Processing triggers for systemd (241-7~deb10u4) ... root@backupprox:~# systemctl start qemu-guest-agent A dependency job for qemu-guest-agent.service failed. See 'journalctl -xe' for details. root@backupprox:~#
 

leesteken

Famous Member
May 31, 2020
1,519
297
88
Please show us the output of systemctl status qemu-guest-agent.service and/or journalctl -xe, which should contain the actual error message.
Have you enabled agent in the vmid.conf (could you post the vmid.conf?) and/or "QEMU Guest Agent" in the Proxmox Web UI for this VM?
 

CCWTech

Member
Mar 3, 2020
49
3
13
52
root@debian:~# systemctl status qemu-guest-agent.service ● qemu-guest-agent.service - QEMU Guest Agent Loaded: loaded (/lib/systemd/system/qemu-guest-agent.service; static; vendor Active: inactive (dead)


Code:
root@debian:~# journalctl -xe
--
-- The job identifier is 153.
Sep 15 15:36:24 debian su[509]: (to root) acrist on pts/0
Sep 15 15:36:24 debian su[509]: pam_unix(su-l:session): session opened for user
Sep 15 15:40:38 debian systemd[1]: dev-virtio\x2dports-org.qemu.guest_agent.0.de
Sep 15 15:40:38 debian systemd[1]: Timed out waiting for device /dev/virtio-port
-- Subject: A start job for unit dev-virtio\x2dports-org.qemu.guest_agent.0.devi
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit dev-virtio\x2dports-org.qemu.guest_agent.0.device has fi
--
-- The job identifier is 273 and the job result is timeout.
Sep 15 15:40:38 debian 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 215 and the job result is dependency.
Sep 15 15:40:38 debian systemd[1]: qemu-guest-agent.service: Job qemu-guest-agen
Sep 15 15:40:38 debian systemd[1]: dev-virtio\x2dports-org.qemu.guest_agent.0.de
lines 1300-1322/1322 (END)
 

CCWTech

Member
Mar 3, 2020
49
3
13
52
That's the trick. I was focused on a Debian service issue and didn't realize how important it was to have that enabled. Thanks.
 
  • Like
Reactions: zombie-man

pawelos

New Member
Nov 28, 2020
4
0
1
42
Have the same problem

Please help me i have done i think everything (including 6 new instalations proxmox on old laptop toshiba satellite d850-11q link to laptop: https://ie.dynabook.com/discontinued-products/satellite-c850d-11q/
and my agent still don't working. I installed quemu agent in console then run it on VM in GUI menu - restart VM few times and still don't working. My processor support AMD-V (virtualization)


commands and output:


~# systemctl start qemu-guest-agent
A dependency job for qemu-guest-agent.service failed. See 'journalctl -xe' for details.

# systemctl status qemu-guest-agent
● qemu-guest-agent.service - QEMU Guest Agent
Loaded: loaded (/lib/systemd/system/qemu-guest-agent.service; static; vendor preset: enabled)
Active: inactive (dead)

Nov 29 16:13:12 pve systemd[1]: Dependency failed for QEMU Guest Agent.
Nov 29 16:13:12 pve systemd[1]: qemu-guest-agent.service: Job qemu-guest-agent.service/start failed with result 'dependency'.

journalctl -xe
-- A start job for unit pvesr.service has begun execution.
--
-- The job identifier is 5284.
Nov 29 16:49:02 pve systemd[1]: pvesr.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit pvesr.service has successfully entered the 'dead' state.
Nov 29 16:49:02 pve systemd[1]: Started Proxmox VE replication runner.
-- Subject: A start job for unit pvesr.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit pvesr.service has finished successfully.
--
-- The job identifier is 5284.
Nov 29 16:50:00 pve systemd[1]: Starting Proxmox VE replication runner...
-- Subject: A start job for unit pvesr.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit pvesr.service has begun execution.
--
-- The job identifier is 5368.
Nov 29 16:50:02 pve systemd[1]: pvesr.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit pvesr.service has successfully entered the 'dead' state.
Nov 29 16:50:02 pve systemd[1]: Started Proxmox VE replication runner.
-- Subject: A start job for unit pvesr.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit pvesr.service has finished successfully.
--
-- The job identifier is 5368.
 
Last edited:
Nov 28, 2020
6
0
1
35
Have the same problem

Please help me i have done i think everything (including 6 new instalations proxmox on old laptop toshiba satellite d850-11q link to laptop: https://ie.dynabook.com/discontinued-products/satellite-c850d-11q/
and my agent still don't working. I installed quemu agent in console then run it on VM in GUI menu - restart VM few times and still don't working. My processor support AMD-V (virtualization)
[...]

When you say "restart", did you stop the VM and start them, or did you reboot them, because, as mentioned above...

Its red. This mean its not yet applied. Please stop the VM and start again. (a reboot is NOT enough)

-Russ
 

pawelos

New Member
Nov 28, 2020
4
0
1
42
Hi
i did it a few times it's not red anymore. I read everything in this post and did everything but qemu doesn't work even though it's on black and it's enabled
 
Last edited:

Fabian_E

Proxmox Staff Member
Staff member
Aug 1, 2019
1,810
320
88
Hi,
Have the same problem

Please help me i have done i think everything (including 6 new instalations proxmox on old laptop toshiba satellite d850-11q link to laptop: https://ie.dynabook.com/discontinued-products/satellite-c850d-11q/
and my agent still don't working. I installed quemu agent in console then run it on VM in GUI menu - restart VM few times and still don't working. My processor support AMD-V (virtualization)


commands and output:


~# systemctl start qemu-guest-agent
A dependency job for qemu-guest-agent.service failed. See 'journalctl -xe' for details.

# systemctl status qemu-guest-agent
● qemu-guest-agent.service - QEMU Guest Agent
Loaded: loaded (/lib/systemd/system/qemu-guest-agent.service; static; vendor preset: enabled)
Active: inactive (dead)

Nov 29 16:13:12 pve systemd[1]: Dependency failed for QEMU Guest Agent.
Nov 29 16:13:12 pve systemd[1]: qemu-guest-agent.service: Job qemu-guest-agent.service/start failed with result 'dependency'.

journalctl -xe
-- A start job for unit pvesr.service has begun execution.
--
-- The job identifier is 5284.
Nov 29 16:49:02 pve systemd[1]: pvesr.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit pvesr.service has successfully entered the 'dead' state.
Nov 29 16:49:02 pve systemd[1]: Started Proxmox VE replication runner.
-- Subject: A start job for unit pvesr.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit pvesr.service has finished successfully.
--
-- The job identifier is 5284.
Nov 29 16:50:00 pve systemd[1]: Starting Proxmox VE replication runner...
-- Subject: A start job for unit pvesr.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit pvesr.service has begun execution.
--
-- The job identifier is 5368.
Nov 29 16:50:02 pve systemd[1]: pvesr.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit pvesr.service has successfully entered the 'dead' state.
Nov 29 16:50:02 pve systemd[1]: Started Proxmox VE replication runner.
-- Subject: A start job for unit pvesr.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit pvesr.service has finished successfully.
--
-- The job identifier is 5368.
did you install the guest agent on the host? That's not what you want. You need to install the guest agent within the VM.
 

pawelos

New Member
Nov 28, 2020
4
0
1
42
i did it before i create Vm

# apt-get install qemu-guest-agent
Reading package lists... Done
Building dependency tree
Reading state information... Done
qemu-guest-agent is already the newest version (1:3.1+dfsg-8+deb10u8).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
 

Fabian_E

Proxmox Staff Member
Staff member
Aug 1, 2019
1,810
320
88
You need to do it after creating the VM inside of the VM.
 

pawelos

New Member
Nov 28, 2020
4
0
1
42
What?
I should create VM for ex. 100 and after that i should

# apt-get install qemu-guest-agent

after that i check enabled on quemu agent?

next start VM ex. 100?
 

Fabian_E

Proxmox Staff Member
Staff member
Aug 1, 2019
1,810
320
88
Installing the guest agent on the host does not have the desired effect. Start up the VM, and use the install tool of your VM to install the guest-agent in the VM. See also here.
 

ikidd

New Member
Jul 6, 2020
7
0
1
98
Its red. This mean its not yet applied. Please stop the VM and start again. (a reboot is NOT enough)
This needs to be added to the qemu-guest-agent wiki page along with setting the Option for the Agent to be checked on.

Troubleshooting this when that information should obviously be in the installation help is annoying as it's very specific to Proxmox, not libvirt.
 

Carnyx

New Member
Jul 19, 2020
3
0
1
50
Keep seeing this error pop up now and again. Just for reference.

Once the qemu-guest-agent is installed within the Debian 10 guest. You need to enable the agent in the Guest's Options area in the Proxmox admin web interface.

Stop - Start the guest and all should be well.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!