blob: 4ae4f4f48f7982ad8be51105dd46e53ed2cd169c (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
|
virtual: 0.954
graphic: 0.915
hypervisor: 0.880
device: 0.878
vnc: 0.872
debug: 0.860
performance: 0.840
network: 0.795
peripherals: 0.774
semantic: 0.761
ppc: 0.705
architecture: 0.704
PID: 0.694
assembly: 0.655
x86: 0.652
risc-v: 0.632
register: 0.629
VMM: 0.592
mistranslation: 0.554
socket: 0.537
i386: 0.501
files: 0.493
TCG: 0.484
user-level: 0.478
permissions: 0.468
KVM: 0.424
arm: 0.356
kernel: 0.339
boot: 0.338
no sound in spice when VNC enabled
Running Fedora32 with virt-manager → libvirt → qemu I noticed that I got no sound in my spice client. The VM is configured with a SPICE-server and a QXL display, and in addition a VNC display.
Apparently when I remove the VNC display, then the sound is routed just fine to the spice client: I can hear it, and `G_MESSAGES_DEBUG=all remote-viewer --spice-debug spice://localhost:5900` mentions SpicePlaybackChannel and SpiceRecordChannel. With the VNC server configured, such messages are missing, and I cannot hear the sound (which is sent by the guest OS to the virtual hardware).
What is in the libvirt logs (/var/log/libvirt/qemu/${guest}.log) ?
If VNC is enabled, then libvirt sets QEMU_AUDIO_DRV=none unless /etc/libvirt/qemu.conf is set to allow output to host audio.
Clearly this doesn't do the right thing when SPICE is present at the same time as VNC, but that's libvirt's fault rather than QEMU.
So if this is libvirt's fault, can we close this ticket here? Has anybody already reported this to in the libvirt bug tracker?
[Expired for QEMU because there has been no activity for 60 days.]
|