Infinite build template clean debian 12/13 : Error getting WinRM host: 500 QEMU guest agent is not running
Hi everyone
I've tried installing Ludus several times but it never works (debian 12 and 13). Spec :
42G ram
Intel® Core™ i5-9600K CPU @ 3.70GHz
300G ssd (fast nvme)
When I buid vms (template), windows11 and windows server won't build. This error is displayed with the command ```ludus templates logs -f --verbose``` :
==============================================================================
⠋ Waiting for server...2025/09/08 10:04:23.299004 DEBUG RESTY
==============================================================================
~~~ REQUEST ~~~
GET /templates/logs?cursor=664 HTTP/1.1
HOST : 198.51.100.1:8080
HEADERS:
User-Agent: ludus-client/1.10.1+54abb3e
X-Api-Key: SO.***REDACTED***
BODY :
***** NO CONTENT *****
------------------------------------------------------------------------------
~~~ RESPONSE ~~~
STATUS : 200 OK
PROTO : HTTP/2.0
RECEIVED AT : 2025-09-08T10:04:23.298980018+02:00
TIME DURATION: 30.790526ms
HEADERS :
Content-Length: 191
Content-Type: application/json; charset=utf-8
Date: Mon, 08 Sep 2025 08:04:23 GMT
BODY :
{
"cursor": 665,
"result": "2025/09/08 10:04:21 packer-plugin-proxmox_v1.2.3_x5.0_linux_amd64 plugin: 2025/09/08 10:04:21 [DEBUG] Error getting WinRM host: 500 QEMU guest agent is not running\n"
}So I naturally looked at "qemu guest agent" (https://pve.proxmox.com/wiki/Qemu-guest-agent):
```apt update && apt -y install qemu-guest-agent
systemctl start qemu-guest-agent
systemctl enable qemu-guest-agent
```
I get this error when looking at the qemu guest agent startup logs ```journalctl -xe``` :
root@ludus:~# journalctl -xe
░░
░░ L'unité (unit) dev-virtio\x2dports-org.qemu.guest_agent.0.device a commencé à démarrer.
sept. 08 10:31:59 ludus pveproxy[3471]: worker exit
sept. 08 10:31:59 ludus pveproxy[3472]: worker exit
sept. 08 10:32:09 ludus systemd[1]: Reloading.
sept. 08 10:32:09 ludus systemd[1]: Reloading.
sept. 08 10:32:10 ludus systemd[1]: Reloading.
sept. 08 10:33:27 ludus systemd[1]: dev-virtio\x2dports-org.qemu.guest_agent.0.device: Job dev-virtio\x2dports-org.qemu.guest_agent.0.device/start timed out.
sept. 08 10:33:27 ludus systemd[1]: Timed out waiting for device dev-virtio\x2dports-org.qemu.guest_agent.0.device - /dev/virtio-ports/org.qemu.guest_agent.0.
░░ Subject: L'unité (unit) dev-virtio\x2dports-org.qemu.guest_agent.0.device a échoué
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ L'unité (unit) dev-virtio\x2dports-org.qemu.guest_agent.0.device a échoué, avec le résultat timeout.
sept. 08 10:33:27 ludus systemd[1]: Dependency failed for qemu-guest-agent.service - QEMU Guest Agent.
░░ Subject: L'unité (unit) qemu-guest-agent.service a échoué
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ L'unité (unit) qemu-guest-agent.service a échoué, avec le résultat dependency.
sept. 08 10:33:27 ludus systemd[1]: qemu-guest-agent.service: Job qemu-guest-agent.service/start failed with result 'dependency'.
sept. 08 10:33:27 ludus 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'.
sept. 08 10:36:40 ludus pvedaemon[3402]: <so@pam> starting task UPID:ludus:0000109C:0000B63C:68BE9598:qmdestroy:103:so@pam:
sept. 08 10:36:40 ludus pvedaemon[4252]: destroy VM 103: UPID:ludus:0000109C:0000B63C:68BE9598:qmdestroy:103:so@pam:
sept. 08 10:36:40 ludus pvedaemon[3402]: <so@pam> end task UPID:ludus:0000109C:0000B63C:68BE9598:qmdestroy:103:so@pam: OK
sept. 08 10:36:48 ludus pvedaemon[3400]: <so@pam> starting task UPID:ludus:000010B3:0000B97D:68BE95A0:qmdestroy:102:so@pam:
sept. 08 10:36:48 ludus pvedaemon[4275]: destroy VM 102: UPID:ludus:000010B3:0000B97D:68BE95A0:qmdestroy:102:so@pam:
sept. 08 10:36:48 ludus pvedaemon[3400]: <so@pam> end task UPID:ludus:000010B3:0000B97D:68BE95A0:qmdestroy:102:so@pam: OK
sept. 08 10:37:01 ludus cron[1007]: (*system*vzdump) RELOAD (/etc/cron.d/vzdump)
sept. 08 10:37:04 ludus systemd[1]: Expecting device dev-virtio\x2dports-org.qemu.guest_agent.0.device - /dev/virtio-ports/org.qemu.guest_agent.0...
░░ Subject: L'unité (unit) dev-virtio\x2dports-org.qemu.guest_agent.0.device a commencé à démarrer
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ L'unité (unit) dev-virtio\x2dports-org.qemu.guest_agent.0.device a commencé à démarrer.
sept. 08 10:38:34 ludus systemd[1]: dev-virtio\x2dports-org.qemu.guest_agent.0.device: Job dev-virtio\x2dports-org.qemu.guest_agent.0.device/start timed out.
sept. 08 10:38:34 ludus systemd[1]: Timed out waiting for device dev-virtio\x2dports-org.qemu.guest_agent.0.device - /dev/virtio-ports/org.qemu.guest_agent.0.
░░ Subject: L'unité (unit) dev-virtio\x2dports-org.qemu.guest_agent.0.device a échoué
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ L'unité (unit) dev-virtio\x2dports-org.qemu.guest_agent.0.device a échoué, avec le résultat timeout.
sept. 08 10:38:34 ludus systemd[1]: Dependency failed for qemu-guest-agent.service - QEMU Guest Agent.
░░ Subject: L'unité (unit) qemu-guest-agent.service a échoué
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ L'unité (unit) qemu-guest-agent.service a échoué, avec le résultat dependency.
sept. 08 10:38:34 ludus systemd[1]: qemu-guest-agent.service: Job qemu-guest-agent.service/start failed with result 'dependency'.
sept. 08 10:38:34 ludus 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'.Do you have any idea?
Edited by soso