Bug 1158665

Summary:	spice-vdagentd is not always started
Product:	[Fedora] Fedora	Reporter:	David Shea <dshea>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	21	CC:	johannbg, jsynacek, lnykryn, msekleta, s, systemd-maint, vpavlin, zbyszek
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-12-09 02:15:06 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 David Shea 2014-10-29 20:05:40 UTC

Description of problem:

Using the Fedora 21 Server Beta RC2 boot media.

Sometimes spice-vdagentd is not started. Using a VM created by virt-manager with 4 virtual CPUs. The virtio_console and various other virtio kernel modules are loaded, /dev/virtio-ports/com.redhat.spice.0 and /dev/virtio-ports/org.qemu.guest_agent.0 exist, and /lib/udev/rules.d/70-spice-vdagentd.rules, which adds the spice-vdagentd.target wants, is present, but systemctl list-dependencies --reverse spice-vdagentd.target does not list anything but the target.

Version-Release number of selected component (if applicable):
systemd-216-5.fc21


How reproducible:
occasionally, once every four or five boots or so

Comment 1 Lennart Poettering 2014-12-09 02:15:06 UTC


*** This bug has been marked as a duplicate of bug 1160222 ***