Bottom Line: QEMU Guest Agent Needs Both a Host Channel and a Guest Daemon
Turning on “QEMU Guest Agent” in a hypervisor UI is only half of the setup. The VM definition must expose a virtio-serial channel named org.qemu.guest_agent.0, and the guest operating system must actually run qemu-guest-agent. If either side is missing, the agent cannot work.
The libvirt Guest Agent guide documents both requirements. QEMU describes the same host/guest channel model in its Guest Agent architecture notes.
If ZimaOS Is the Guest on Proxmox
The normal Debian instruction apt install qemu-guest-agent does not translate directly to stock ZimaOS. ZimaOS is an appliance-style Buildroot system rather than a Debian/Ubuntu host, so apt and yum are not general package-management paths. The ZimaOS package-manager guide explains that boundary.
That means enabling the Proxmox guest-agent checkbox does not magically install a daemon inside ZimaOS. The ZimaOS on Proxmox guide is the safer baseline for VM testing.
If ZimaOS Is the Hypervisor Running Another VM
A separate April 2026 test in the thread checked a ZVM guest and found no /dev/virtio-ports inside the guest and no org.qemu.guest_agent.0 channel in the VM XML. That result explains why installing the guest daemon alone would not have helped in that tested build.
# Inside a Linux guest
ls -l /dev/virtio-ports/
# On a libvirt host
virsh dumpxml <vm-name> | grep -A4 -B2 guest_agentDo not treat the April 2026 result as a permanent product guarantee. Verify the channel on the current build before concluding that ZVM still lacks it.
What to Do When You Need Reliable Guest-Agent Features
If your workflow depends on clean guest shutdown, IP reporting, filesystem freeze/thaw or backup orchestration, use a guest/hypervisor combination where both sides explicitly support QEMU Guest Agent. For current ZimaOS virtualization planning, see the Virtual Machine Manager requirements and Zima virtual-machine overview.
