Hide Forgot
Description of problem: Boot a guest and open some windows or open a text document in the desktop and then stop the guest by 'stop' qemu command. Do some operation inside guest while the guest is 'paused' status. For example, input some string in the opened text document, or close the text document/windows. Then resume the guest by 'cont' qemu command. As a result all the operation above will be executed after resume the guest. That is not good if some important program is running or the shutdown button is displayed on desktop but will be mis-operated unexpectedly. Version-Release number of selected component (if applicable): kernel-2.6.32-171.el6.x86_64 qemu-kvm-0.12.1.2-2.171.el6.x86_64 seabios-0.6.1.2-3.el6.x86_64 vgabios-0.6b-3.6.el6.noarch How reproducible: Always Steps to Reproduce: 1.Boot a guest and open a text document or some windows in the guest desktop. 2.stop the guest {"execute":"stop"} 3.Do some operation inside guest while the guest is paused. For example, close the text document or close the windows. 4. Resume the guest. {"execute":"cont"} Actual results: the windows/text document will be closed after resume the guest. Expected results: All the operation should be disabled when guest is in 'paused' status. Additional info:
Interesting, low priority but worth fixing
Shouldn't this be done in virt-manager? virt-manager already know the state of the guest and can (a) inform the user and (b) stop sending events. The only thing qemu-kvm could do is silently throw away events which isn't exactly user friendly ... Not sure how to do it best for the rhev-m use case. Guess this one needs broader discussion.
Hmm, this sort-of conflicts with bug #766303 ...
(In reply to comment #5) > Hmm, this sort-of conflicts with bug #766303 ... Not necessarily since #766303 is only in case of s3 but not pause mode. I do think qemu should block it regardless of virt-manager. It is low priority so I'll close it as won't fix and Gerd is welcome to solve it upstream