Hi,
What I was thinking about is sending feedback about volume changes to
the guest is something completely different, let me explain in detail:
What we have in spice today is that the guests volume change request is
passed to the spice client, which in turn forwards it to
On Fri, Apr 11, 2014 at 10:25:59AM +0200, Gerd Hoffmann wrote:
On Do, 2014-04-10 at 18:20 +0300, Michael S. Tsirkin wrote:
On Thu, Apr 10, 2014 at 02:10:20PM +0200, Gerd Hoffmann wrote:
On Do, 2014-04-10 at 14:05 +0300, Michael S. Tsirkin wrote:
On Thu, Apr 10, 2014 at 11:07:53AM +0200,
On Do, 2014-04-10 at 18:20 +0300, Michael S. Tsirkin wrote:
On Thu, Apr 10, 2014 at 02:10:20PM +0200, Gerd Hoffmann wrote:
On Do, 2014-04-10 at 14:05 +0300, Michael S. Tsirkin wrote:
On Thu, Apr 10, 2014 at 11:07:53AM +0200, Gerd Hoffmann wrote:
Device for sending non-input control
On Thu, Apr 10, 2014 at 11:07:53AM +0200, Gerd Hoffmann wrote:
Device for sending non-input control messages to the guest. For now
this is only a single event: shutdown requests are sent as power button
press to the guest.
Possible other use is signaling sound volume changes to the guest
On Do, 2014-04-10 at 14:05 +0300, Michael S. Tsirkin wrote:
On Thu, Apr 10, 2014 at 11:07:53AM +0200, Gerd Hoffmann wrote:
Device for sending non-input control messages to the guest. For now
this is only a single event: shutdown requests are sent as power button
press to the guest.
On Thu, Apr 10, 2014 at 02:10:20PM +0200, Gerd Hoffmann wrote:
On Do, 2014-04-10 at 14:05 +0300, Michael S. Tsirkin wrote:
On Thu, Apr 10, 2014 at 11:07:53AM +0200, Gerd Hoffmann wrote:
Device for sending non-input control messages to the guest. For now
this is only a single event:
