Bug 1136846 – Cannot control Win7 guest sound volume using guest volume controller

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1136846 - Cannot control Win7 guest sound volume using guest volume controller

Summary:	Cannot control Win7 guest sound volume using guest volume controller

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Virtualization Manager
Classification:	Red Hat
Component:	mingw-virt-viewer (Show other bugs)
Sub Component:
Version:	3.5.0
Hardware:	All Windows

Priority	medium Severity medium
Target Milestone:	ovirt-3.6.0-rc
Target Release:	3.6.0
Assigned To:	Victor Toso
QA Contact:	SPICE QE bug list
Docs Contact:

URL:
Whiteboard:
Keywords:	Reopened

Depends On:	1181289
Blocks:
	Show dependency tree / graph

Reported:	2014-09-03 08:18 EDT by Amador Pahim
Modified:	2016-03-09 15:09 EST (History)
CC List:	13 users (show)

See Also:
Fixed In Version:	mingw-virt-viewer-2.0-1.el7ev
Doc Type:	Bug Fix
Doc Text:	Previously, users could not control a Windows 7 virtual machine's sound volume with the guest volume controls. This occurred because the Windows client's audio back-end (GStreamer) did not have mute and volume control capabilities for playback and record. This was fixed by updating GStreamer to version 1.0, and implementing volume and mute capabilities in the directsoundsrc element. Volume control on Windows virtual machines now works as expected.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2016-03-09 15:09:06 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	Spice
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHEA-2016:0377	normal	SHIPPED_LIVE	rhevm-spice-client bug fix and enhancement update	2016-03-09 19:39:05 EST

Groups: None (edit)

Description Amador Pahim 2014-09-03 08:18:34 EDT

Using client volume control, I can control Guest sound volume, but I'm not able to control guest volume using guest volume controller in some envs: 

Unable to control sound volume inside the guest
- Client Win7, vier-viewer 0.5.6-25(rhev current) / Guest Win7, RHEV-Spice-Agent 4.11.2
- Client Win7, vier-viewer 1.0256(newest available msi) / Guest Win7, RHEV-Spice-Agent 4.11.2

But using client on Fedora20 or using a RHEL7 Guest, I can control guest sound volume inside the guest:
- Client Win7, vier-viewer 0.5.6-25 / Guest RHEL7
- Client Fedora20, virt-viewer-0.6.0-1.fc20.x86_64 / Guest Win7, RHEV-Spice-Agent 4.11.2

Comment 1 Marc-Andre Lureau 2014-09-03 08:36:13 EDT

The problems stems from the audio sink/src not implementing the GstStreamVolume interface.

In >1.0, directsoundsink implements it, however directsoundsrc is still missing volume control.

Perhaps we should first rebase gstreamer to 1.x series, and fix directsoundsrc upstream.

this all sounds too late for 3.5

Comment 3 Victor Toso 2015-02-19 09:14:18 EST

Just an update: Last upstream release of virt-viewer is using gstreamer1 and you can control guest playback audio inside the guest;

For the record audio (directsoundsrc), there is a patch upstream at:
https://bugzilla.gnome.org/show_bug.cgi?id=744383

Comment 4 Victor Toso 2015-04-01 04:18:10 EDT

The patch for directsoundsrc element is now upstream.

Closing this bug as NEXTRELEASE as this patch should be available in next virt-viewer windows release.

If you find any problems related to volume control, please open a new bug for it.

Comment 5 Victor Toso 2015-04-01 04:46:28 EDT

Closing as NEXTRELEASE is not right. Sorry. Moving it to POST.

The bz for directsoundsrc fix is
https://bugzilla.gnome.org/show_bug.cgi?id=744383

The patch is upstream on gst-plugins-bad hash
1b564bfb8b0db43a24cf311dca24038558b80a68

It should be included in version 1.4.6

Comment 10 errata-xmlrpc 2016-03-09 15:09:06 EST

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://rhn.redhat.com/errata/RHEA-2016-0377.html

Note You need to log in before you can comment on or make changes to this bug.