The problem with qemu-guest-agent on pfSense 2.6.0

perrfect

Hello.
I'm trying to install qemu-guest-agent on pfSense 2.6.0, but getting the error when the service starts:

debug: disabling command: guest-suspend-disk
debug: disabling command: guest-suspend-ram
debug: disabling command: guest-suspend-hybrid
debug: disabling command: guest-set-vcpus
debug: disabling command: guest-get-memory-blocks
debug: disabling command: guest-set-memory-blocks
debug: disabling command: guest-get-memory-block-size
debug: disabling command: guest-get-memory-block-info
debug: disabling command: guest-fsfreeze-status
debug: disabling command: guest-fsfreeze-freeze
debug: disabling command: guest-fsfreeze-freeze-list
debug: disabling command: guest-fsfreeze-thaw
debug: disabling command: guest-fstrim
critical: error opening channel: No such file or directory
critical: error opening channel
critical: failed to create guest agent channel
critical: failed to initialize guest agent channel

I'm using the article pfsense-qemu-guest-agent for install pfsense-qemu-guest-agent.

Can please help me?

viragomann

@perrfect
Seems the agent cannot find the channel.
Did you provide the guest channel in the hypervisor as well?

johnpoz

@perrfect I just ran thru this not on proxmox but on VM on synology which uses qemu

[2.6.0-RELEASE][admin@pfSense.home.arpa]/usr/local/etc/rc.d: service qemu-guest-agent start
Starting qemu_guest_agent.
[2.6.0-RELEASE][admin@pfSense.home.arpa]/usr/local/etc/rc.d: service qemu-guest-agent status
qemu_guest_agent is running as pid 15340.
[2.6.0-RELEASE][admin@pfSense.home.arpa]/usr/local/etc/rc.d:

I just rebooted the pfsense vm to make sure everything came up on its own

Looks like everything is working here.. I don't currently have a proxmox to play with - but I did have one a while back, and was running both 2.6 and snapshot of 2.7 on it, and don't recall any issues installing the qemu agent.. Was working fine.

edit: I think I read somewhere that you might have to actually stop the VM and then start it vs just a "reboot" for proxmox - been awhile since did it on proxmox, and don't currently have one to test with..