Hide Forgot
Description of problem: spice-vdagent on Linux is two-part just as in Windows but documentation (Administration Guide - Table 18.4) captures just system part that is responsible for message passing between server (and by extension, client) and per-session part. To get debug output of per-session part of the agent, it has to be killed in the session to be debugged and restarted in foreground with debug output on: $ killall spice-vdagent $ spice-vdagent -x -d [-d] [ | tee spice-vdagent.log ] Version-Release number of selected component (if applicable): 4.0.4 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: direct link: https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/single/administration-guide/#idm140139776698608
Assigning to Emma for review.
(In reply to David Jaša from comment #0) I think David has a good point, especially as this can be done without root permissions. A few comments: > Description of problem: > spice-vdagent on Linux is two-part just as in Windows but documentation > (Administration Guide - Table 18.4) captures just system part that is That's probably Table 19.4 here > responsible for message passing between server (and by extension, client) > and per-session part. > > To get debug output of per-session part of the agent, it has to be killed in > the session to be debugged and restarted in foreground with debug output on: > $ killall spice-vdagent This works but perhaps we should come up with a command that does not try to kill other users processes. > $ spice-vdagent -x -d [-d] [ | tee spice-vdagent.log ] Here it should be "|&" ^^^ Apparently spice-vdagent writes to stderr. In addition: The reference to /var/log/vdagent.log should be removed and instead tell users to use journalctl instead.
Uri, do (In reply to Uri Lublin from comment #3) > (In reply to David Jaša from comment #0) > I think David has a good point, especially as this can be done without root > permissions. > > A few comments: > > > Description of problem: > > spice-vdagent on Linux is two-part just as in Windows but documentation > > (Administration Guide - Table 18.4) captures just system part that is > > That's probably Table 19.4 here > > > responsible for message passing between server (and by extension, client) > > and per-session part. > > > > To get debug output of per-session part of the agent, it has to be killed in > > the session to be debugged and restarted in foreground with debug output on: > > $ killall spice-vdagent > > This works but > perhaps we should come up with a command that does not try to kill other > users processes. Uri, which command should I use in order to not kill other users' processes? > > $ spice-vdagent -x -d [-d] [ | tee spice-vdagent.log ] > > Here it should be "|&" ^^^ > Apparently spice-vdagent writes to stderr. > > > In addition: > The reference to /var/log/vdagent.log should be removed > and instead tell users to use journalctl instead.
(In reply to emma heftman from comment #4) > (In reply to Uri Lublin from comment #3) > > > To get debug output of per-session part of the agent, it has to be killed in > > > the session to be debugged and restarted in foreground with debug output on: > > > $ killall spice-vdagent > > > > This works but > > perhaps we should come up with a command that does not try to kill other > > users processes. > > Uri, which command should I use in order to not kill other users' processes? For example: killall -u $USER spice-vdagent
Davide, please review the changes that I have made to the Administration Guide: http://file.tlv.redhat.com/~eheftman/bz1373263/html-single/#sect-SPICE_Log_Files Section 19.3.2
Links to the documentation on the Customer portal. 4.0: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.0/html-single/administration_guide/ 4.1: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1-beta/html-single/administration_guide/