Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.
18.3. SPICE Log Files
SPICE log files are useful when troubleshooting SPICE connection issues. To start SPICE debugging, change the log level to
debugging
. Then, identify the log location.
Both the clients used to access the guest machines and the guest machines themselves have SPICE log files. For client side logs, if a SPICE client was launched using a browser plug-in, debugging is generally controlled by environment variables. If a SPICE client is launched using the native client, for which a
console.vv
file is downloaded, use the remote-viewer
command to enable debugging and generate log output.
18.3.1. SPICE Logs for Hypervisor SPICE Servers Link kopierenLink in die Zwischenablage kopiert!
Link kopierenLink in die Zwischenablage kopiert!
Log Type | Log Location | To Change Log Level: |
---|---|---|
Host/Hypervisor SPICE Server
|
/var/log/libvirt/qemu/(guest_name).log
|
Run
export SPICE_DEBUG_LEVEL=5 on the host/hypervisor prior to launching the guest.
|
18.3.2. SPICE Logs for Guest Machines Link kopierenLink in die Zwischenablage kopiert!
Link kopierenLink in die Zwischenablage kopiert!
Log Type | Log Location | To Change Log Level: |
---|---|---|
Windows Guest
|
C:\Windows\Temp\vdagent.log
C:\Windows\Temp\vdservice.log
|
Not applicable
|
Red Hat Enterprise Linux Guest
|
/var/log/spice-vdagent.log
| Create a /etc/sysconfig/spice-vdagentd file with this entry: SPICE_VDAGENTD_EXTRA_ARGS=”-d -d” |
18.3.3. SPICE Logs for SPICE Clients Launched Using Browser Plug-ins Link kopierenLink in die Zwischenablage kopiert!
Link kopierenLink in die Zwischenablage kopiert!
For SPICE client launched using browser plug-ins, the log location and change log level instructions are different depending on the OS type, OS version, and system type.
Log Type | Log Location | To Change Log Level: |
---|---|---|
SPICE Client (Windows 7)
|
C:\Windows\Temp\spicex.log
|
|
SPICE Client (Red Hat Enterprise Linux 6)
|
~/home/.spicec/spice-xpi.log
|
Edit the
/etc/spice/logger.ini file and change the log4j.rootCategory variable from INFO, R to DEBUG, R .
|
SPICE Client (Red Hat Enterprise Linux 7)
|
~/.xsession-errors
|
Launch Firefox from the command line with debug options:
G_MESSAGES_DEBUG=all SPICE_DEBUG=1 firefox .
Touch the
~/.xsession-errors file.
|
USB Redirector on Windows Client
|
C:\Windows\Temp\usbclerk.log
|
Not applicable.
|
18.3.4. SPICE Logs for SPICE Clients Launched Using console.vv Files Link kopierenLink in die Zwischenablage kopiert!
Link kopierenLink in die Zwischenablage kopiert!
For Linux client machines:
- Enable SPICE debugging by running the
remote-viewer
command with the--spice-debug
option. When prompted, enter the connection URL, for example, spice://[virtual_machine_IP]:[port].remote-viewer --spice-debug
# remote-viewer --spice-debug
Copy to Clipboard Copied! Toggle word wrap Toggle overflow - To view logs, download the
console.vv
file and run theremote-viewer
command with the--spice-debug
option and specify the full path to theconsole.vv
file.remote-viewer --spice-debug /path/to/console.vv
# remote-viewer --spice-debug /path/to/console.vv
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
For Windows client machines:
- Download the
debug-helper.exe
file and move it to the same directory as theremote-viewer.exe
file. For example, theC:\Users\[user name]\AppData\Local\virt-viewer\bin
directory. - Execute the
debug-helper.exe
file to install the GNU Debugger (GDB). - Enable SPICE debugging by executing the
debug-helper.exe
file.debug-helper.exe remote-viewer.exe --spice-controller
debug-helper.exe remote-viewer.exe --spice-controller
Copy to Clipboard Copied! Toggle word wrap Toggle overflow - To view logs, connect to the virtual machine, and you will see a command prompt running GDB that prints standard output and standard error of remote-viewer.