[SOLVED] Starting qemu guest always leads to errors

Proximate

Member
Feb 13, 2022
219
12
23
64
I installed the qemu guest on centos 8 servers that I migrated from esx to proxmox.
When rebooting the system, the service seems to start or at least status shows active.

However, if I stop it and try to start it, it never works and this is on every centos machine I migrated. I looked online and still am searching but cannot seem to find an answer. Hoping for some leads by posting this.

I found this and working through other posts.
https://forum.proxmox.com/threads/dependency-failed-for-qemu-guest-agent.75797/

I followed this to enable the service but it won't come up.
I uninstalled it and re-installed it and rebooted.
The proxmox GUI still shows it as disabled.


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



Code:
-- The unit session-37.scope has successfully entered the 'dead' state.
Mar 31 15:32:01 cp159 systemd[1]: dev-virtio\x2dports-org.qemu.guest_agent.0.device: Job dev-virtio\x2dports-org.qemu.guest_agent.0.d>
Mar 31 15:32:01 cp159 systemd[1]: Timed out waiting for device dev-virtio\x2dports-org.qemu.guest_agent.0.device.
-- Subject: Unit dev-virtio\x2dports-org.qemu.guest_agent.0.device has failed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit dev-virtio\x2dports-org.qemu.guest_agent.0.device has failed.
--
-- The result is timeout.
Mar 31 15:32:01 cp159 systemd[1]: Dependency failed for QEMU Guest Agent.
-- Subject: Unit qemu-guest-agent.service has failed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit qemu-guest-agent.service has failed.
--
-- The result is dependency.
Mar 31 15:32:01 cp159 systemd[1]: qemu-guest-agent.service: Job qemu-guest-agent.service/start failed with result 'dependency'.
Mar 31 15:32:01 cp159 systemd[1]: dev-virtio\x2dports-org.qemu.guest_agent.0.device: Job dev-virtio\x2dports-org.qemu.guest_agent.0.d>
Mar 31 15:32:01 cp159 systemd[1]: Started Session 38 of user root.
-- Subject: Unit session-38.scope has finished start-up
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit session-38.scope has finished starting up.
--
-- The start-up result is done.
Mar 31 15:32:01 cp159 systemd[1]: Started Session 39 of user root.
-- Subject: Unit session-39.scope has finished start-up
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit session-39.scope has finished starting up.


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

Mar 31 15:32:01 cp159 systemd[1]: Dependency failed for QEMU Guest Agent.
Mar 31 15:32:01 cp159 systemd[1]: qemu-guest-agent.service: Job qemu-guest-agent.service/start failed with result 'dependency'.
 
Last edited:
I then stopped the vm completely and even used 'stop' to make sure.
I went back to the GUI, unckecked the qemu-agent enabled option, saved it then went back and set it to enabled again.
Then I re-started the vm and now it's on.

Strange combination of things to do I guess.
 

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 yours easily in our online shop.

Buy now!