Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
So, when using systemd as the init system, the system vdagent daemon is a hardware-activated service. In other words, it is only started when the appropriate virtio port device is added. At boot, the device is added, which causes a udev rule to add spice-vdagentd.target to the list of targets wanted by systemd.
When you issue the command "systemctl isolate multi-user.target", it starts the multi-user.target unit (and all of its dependencies) and stops all others. Since spice-vdagent.target is not a dependency of multi-user.target, it will get stopped.
Now you issue the command "systemctl isolate graphical.target", and it starts the graphical.target unit and stops all others. This still does not start the vdagent service because it is not a dependency of graphical.target either. The only thing that starts the spice-vdagentd service is the udev "add" event for the appropriate virtio device.
At this point, you can fix this issue by manually starting the vdagent daemon before logging back into GNOME:
systemctl start spice-vdagentd.service
I think we could also patch the vdagent daemon so that it supported systemd socket activation. Then when the user session agent was started, it would attempt to connect to the system daemon socket, which would cause the system daemon to get restarted. I have a proof of concept that does this and it seems to work.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2018:1017