-
-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Display an icon indicating the VM is in some transient state #520
Comments
Comment by marmarek on 18 Apr 2012 09:15 UTC |
Comment by joanna on 18 Apr 2012 21:05 UTC
One things to consider: Perhaps the green icon (#3 above) should appear only after qrexec connected fine, and before that happens we should still be showing a yellow icon, even though the VM is in state Running already. I think we should go this way, unless it was somehow difficult to implement. |
Comment by marmarek on 18 Apr 2012 22:10 UTC |
Comment by marmarek on 18 Apr 2012 23:16 UTC |
Comment by aga on 19 Apr 2012 13:05 UTC But the super-weak point of this is that it would only work with starting vms from manager, not with qvm-start. However - if the solution offered by Marek doesn't always work - it may be a way of making it slightly better... |
Comment by aga on 20 Apr 2012 16:40 UTC |
Reported by joanna on 14 Apr 2012 12:30 UTC
Currently we either display a Green dot, indicating the VM is running, or not, implicitly indicting the VM is stopped. However, the VM might be in other states between Running and Halted, such as e.g. "Halting". It is important to indicate this to the user (e.g. by displaying a yellow icon), as otherwise the user things the VM is shutdown and might be trying to e.g. start it again, which however will fail, as the VM is still in some other state, not ready for another start. This is confusing.
Perhaps this could be done by adding an is_in_transient_state() method to QubesVm class, and for all domains where this is true, to display a yellow icon.
Migrated-From: https://wiki.qubes-os.org/ticket/520
The text was updated successfully, but these errors were encountered: