Description of problem: Error on spice-vdagent after boot Version-Release number of selected component (if applicable): fedora-repos-25-1.noarch fedora-release-25-1.noarch lenovo W541 laptop How reproducible: Always Steps to Reproduce: The boot happens successfully but the spice-vdagent errors are shown everytime in journalctl as shown below: # journalctl -p err -b -- Logs begin at Thu 2016-12-15 15:12:47 EST, end at Sat 2016-12-17 23:38:15 EST. -- Dec 17 23:35:33 host1 spice-vdagent[1598]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 Dec 17 23:36:07 host1 spice-vdagent[2036]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 Actual results: Error as shown above Expected results: No error Additional info:
# rpm -q kernel kernel-4.8.6-300.fc25.x86_64 kernel-4.8.13-300.fc25.x86_64
Additional info: This is a fresh Fedora 25 install
Do you have the /dev/virtio-ports/com.redhat.spice.0 ? Does disabling selinux help? Can you provide the libvirt domain or qemu command line? virsh dumpxml $domain-name for the former. I've just tested spice-vdagent 0.16-3 and I don't see any error so I'm thinking this is some configuration issue.
No response for almost a month, so closing. If anyone can still reproduce, please reopen with the info requested in Comment #3
I also encounter this error on a ThinkPad T430s running Fedora 25 natively without virtualization. The directory /dev/virtio-ports/com.redhat.spice.0 does not exist on my system. I believe it should only exist if the system were running on a virtual machine? Maybe spice-vdagent falsely assumes the OS is running on a virtual machine and hence expects /dev/virtio-ports/com.redhat.spice.0 to exist? It doesn't seem to be an SELinux policy issue as there are no permission denial alerts logged on my system. Removing spice-vdagent prevents this error message.
(In reply to Bertran Lopez from comment #5) > I also encounter this error on a ThinkPad T430s running Fedora 25 natively > without virtualization. > > The directory /dev/virtio-ports/com.redhat.spice.0 does not exist on my > system. I believe it should only exist if the system were running on a > virtual machine? With the right qemu parameters, that's correct. > Maybe spice-vdagent falsely assumes the OS is running on a virtual machine > and hence expects /dev/virtio-ports/com.redhat.spice.0 to exist? > > It doesn't seem to be an SELinux policy issue as there are no permission > denial alerts logged on my system. > > Removing spice-vdagent prevents this error message. Spice-vdagent is supposedly to run in a Virtual Machine, not in a bare-metal system. The communication between the remote system and the agent happens using "/dev/virtio-ports/com.redhat.spice.0" and for that reason it'll trigger errors.