Bug 1158665 - spice-vdagentd is not always started
Summary: spice-vdagentd is not always started
Keywords:
Status: CLOSED DUPLICATE of bug 1160222
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-29 20:05 UTC by David Shea
Modified: 2014-12-09 02:15 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-12-09 02:15:06 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.