Description of problem: On a heavily loaded system, I ran into a case where a dialog box showed up for one of my VMs saying that it was not responding. There were two buttons, one of them being "Wait". I clicked on it, but this did not dismiss the dialog. So I clicked on the dialog's close box in the top-right, and this quit virt-manager. The VMs kept running, fortunately. How reproducible: 1. Run a VM with a high load. In my case, building linux kernel at -j8 on a 4-VCPU machine. 2. Simultaneously run a high load on the host. In my case, building linux kernel at -j20 on a 8-CPU machine. 3. Wait until a message pops up indicating that the VM is not responsive. 4. Try to dismiss the dialog using the Wait button. 5. Try to dismiss the dialog using the dialog close button in top-right corner. Actual results: The Wait button has no visible effect. In my case, the VM was clearly running in the background. The dialog close button closes the application. Expected results: The Wait button should dismiss the dialog and show the VM. The dialog close button should do like Wait, and not close the application.
Thanks for the report. That dialog comes from GTK, it automatically pops up when it detects that that the app is not responding for a few seconds, meaning it might be hung. The 'X' stopping the associated app is expected behavior as far as I know, so closing You can try filing a bug about it against gtk but I'm certain they will say NOTABUG
I'm curious why the VM is seen as "hung" when it updates its display and responds to user input?
(In reply to Christophe de Dinechin from comment #2) > I'm curious why the VM is seen as "hung" when it updates its display and > responds to user input? Not sure, maybe due to the threading model of the spice-gtk widget. Is virt-manager responsive when the dialog pops up?