Description of problem:
Volume on the client gets increase after migration gets successfully completed
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Connect to a Windows guest (tried this using rhevm3.4)
2. Play something on the guest
3. Lower volume on client
4. Migrate the guest to a different host
Playback volume gets increased
there is already a similar bug open, and it is some ac97 qemu bug iirc.
Could you attach SPICE_DEBUG=1 log when migration occurs
Can you verify which audio device is used by guest?
also it could be a dup of bug 1012868
Created attachment 917120 [details]
Log from client
This is the requested log file.
The audio device on guest is intel-hda, not AC97.
Bug present also in RHEL7.
Also, the log file was taken with spice-gtk3-0.20-8.el7.x86_64 and RHEL7 client, hope you don't mind. As there was no debug console output with spice-gtk-0.22-7 and virt-viewer 0.6.0-9 on RHEL6...
Also, yes, it's possibly a duplicate (quick search didn't show anything)
(In reply to Tomas Jamrisko from comment #4)
> Created attachment 917120 [details]
> Log from client
> This is the requested log file.
> The audio device on guest is intel-hda, not AC97.
> Bug present also in RHEL7.
Ok, from the log the volume didn't change, it's always 60138.
How do you change the volume of the client? via client master volume? then it's a dup of bug 1012868
> Also, the log file was taken with spice-gtk3-0.20-8.el7.x86_64 and RHEL7
> client, hope you don't mind. As there was no debug console output with
> spice-gtk-0.22-7 and virt-viewer 0.6.0-9 on RHEL6...
What do you mean? SPICE_DEBUG=1 didn't work? strange that works for me. Looks like you may have old spice-gtk with new glib, that requires G_MESSAGES_DEBUG=all
G_MESSAGES_DEBUG=all doesn't work either, neither does --spice-debug
versions: spice-gtk-0.22-7, which is in errata for 6.6
spice-glib is the same, 0.22-7,
(In reply to Tomas Jamrisko from comment #7)
> G_MESSAGES_DEBUG=all doesn't work either, neither does --spice-debug
> versions: spice-gtk-0.22-7, which is in errata for 6.6
> spice-glib is the same, 0.22-7,
you need both G_MESSAGES_DEBUG=all and SPICE_DEBUG=1
What is glib version?
*** This bug has been marked as a duplicate of bug 1012868 ***
And there still isn't any debugging output, even with both of those env variables set.
Reopening, and "repurposing" for missing debug output introduced by rebase.
most likely I forgot v0.6.0-50-g48d8fa7
virt-viewer filters out debug messages with glib < 2.32, unless you run with --debug (see bug 1107518).
we could make it filter only its own messages instead..
this a regression from 1107518, I am tempted to push the fix and mark as duplicate. please ack otherwise.
Jonathon, Christophe, can you ack the patch for RHEL6 only atm? thanks
As I explained in ML, Christophe G_MESSAGES_DEBUG patch doesn't solve this bug, and is a change of logging behaviour compared to other rhel6 apps. It's also the wrong place to backport imho.
Clearing needinfo as I replied on email list: https://www.redhat.com/archives/virt-tools-list/2014-July/msg00080.html
push fix as regression of 1107518
*** This bug has been marked as a duplicate of bug 1107518 ***