Bug 1405750

Summary:	Error on spice-vdagent after boot
Product:	[Fedora] Fedora	Reporter:	sthirugn <sthirugn>
Component:	spice-vdagent	Assignee:	Christophe Fergeau <cfergeau>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	25	CC:	alon, bertranjlopez, cfergeau, crobinso, marcandre.lureau, sandmann, sthirugn, victortoso, virt-maint
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-16 13:58:11 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description sthirugn@redhat.com 2016-12-18 04:51:30 UTC

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:

Comment 1 sthirugn@redhat.com 2016-12-18 05:05:43 UTC

# rpm -q kernel
kernel-4.8.6-300.fc25.x86_64
kernel-4.8.13-300.fc25.x86_64

Comment 2 sthirugn@redhat.com 2016-12-18 05:06:21 UTC

Additional info: This is a fresh Fedora 25 install

Comment 3 Victor Toso 2016-12-19 08:14:09 UTC

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.

Comment 4 Cole Robinson 2017-01-16 13:58:11 UTC

No response for almost a month, so closing. If anyone can still reproduce, please reopen with the info requested in Comment #3

Comment 5 Bertran Lopez 2017-05-06 13:27:40 UTC

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.

Comment 6 Victor Toso 2017-05-09 12:52:18 UTC

(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.