Bug 1371243

Summary: No sound when VM is started with both Spice and VNC
Product: Red Hat Enterprise Linux 7 Reporter: jniederm
Component: libvirtAssignee: Pavel Hrdina <phrdina>
Status: CLOSED DUPLICATE QA Contact: Fangge Jin <fjin>
Severity: low Docs Contact:
Priority: medium    
Version: 7.3CC: bugs, dyuan, gianluca.cecchi, jniederm, mgoldboi, michal.skrivanek, phrdina, rbalakri, tjelinek, xuzhang, zpeng
Target Milestone: pre-dev-freeze   
Target Release: 7.4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1376510 (view as bug list) Environment:
Last Closed: 2017-03-24 08:31:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
vm_device_screenshot
none
vm_device_screenshot none

Description jniederm 2016-08-29 17:05:50 UTC
Description of problem:
When graphics protocol is set to "SPICE + VNC", libvirt stars qemu process with environment variable QEMU_AUDIO_DRV=none which causes that client can't hear the VM. (If graphical protocol is set to "SPICE" only, then libvirt sets QEMU_AUDIO_DRV=spice and audio works fine.)

Version-Release number of selected component (if applicable):
rhevm 3.6.8.1-0.1.el6,
ovirt 4.1.0-0.0.master.20160802171327.gitd8decfe.el7.centos

How reproducible:
100%

Steps to Reproduce:
1. Create a VM with settings: Optimized for=Desktop, Graphics Protocol=SPICE+VNC, check "Soundcard enabled" (Console side-tab)
2. Run the VM
3. Connect to the host the VM is running on and on that host:
4. Check qemu process environment variables (also in /var/log/libvirt/qemu/{vm-name}.log

Actual results:
QEMU_AUDIO_DRV=none and consequently no sound from VM

Expected results:
VM sound is accessible even with graphics protocol set to "SPICE + VNC". 

Additional info:
Origin: http://lists.ovirt.org/pipermail/users/2016-August/042233.html

Comment 1 Moran Goldboim 2016-08-30 06:56:44 UTC
is it a regression? do we know from when?

Comment 2 Tomas Jelinek 2016-08-30 07:08:36 UTC
I don't think it ever worked. When you use only SPICE or only VNC, the sound works. Than we introduced the feature of SPICE + VNC together and the sound does not work in this case. So it is not really a regression but a bug in the feature.

Comment 3 Gianluca Cecchi 2016-08-30 07:54:44 UTC
Confirmed (environment described in the additional info web link of description section) with:


Comment 4 Gianluca Cecchi 2016-08-30 07:55:24 UTC
Engine: oVirt 3.6.6.2-1.el7.centos
Host CentOS 7.2 based on 3.6.6 with:
qemu-kvm-ev-2.3.0-31.el7_2.10.1.x86_64
libvirt-daemon-1.2.17-13.el7_2.4.x86_64
vdsm-4.17.28-0.el7.centos.noarch

Comment 5 jniederm 2016-08-30 14:27:43 UTC
Created attachment 1195935 [details]
vm_device_screenshot

Comment 6 jniederm 2016-08-30 14:42:35 UTC
Created attachment 1195939 [details]
vm_device_screenshot

Comment 7 jniederm 2016-08-30 14:44:17 UTC
The device is actually present but sound is not transferred over the protocol.

Comment 8 jniederm 2016-09-15 15:48:05 UTC
The patch http://gerrit.ovirt.org/63093 will be tracked in cloned bug 1376510.

Comment 9 Michal Skrivanek 2016-12-21 08:23:22 UTC
proper fix should be in libvirt when both SPICE and VNC is configured

Comment 10 Pavel Hrdina 2017-03-24 08:31:54 UTC

*** This bug has been marked as a duplicate of bug 1375433 ***