https://github.com/QubesOS/qubes-issues/issues/1581
What do you think about adding "priority" to each vm to solve shutdown process issue? With highest (>=) priority number VM shutdown first and with the same number maybe synchronously. Example: sys-net -- shutdown priority 10 sys-firewall -- 20 sys-whonix -- 30 Some-ProxyVm with sys-whonix netvm -- auto priority 31 or manual selected 40 (Maybe user can choose priority. New vm must created with +1 shutdown priority by default or manually selected.) When shutdown process start it must shutdown VMs with highest priority first, then continue shutdown with lower priority number VMs. At the same time Qubes must show fullscreen list of all VMs and status of them with buttons to kill them. The idea to shutdown with dependencies. Like users do at QM when they wants to stop all vms. Maybe we can setup priorities automatically in most situations. We know sequences like: sys-new -> sys-firewall -> vmproxy1 -> sys-whonix -> vmvpn -> appvm So, we can stop them one-by-one from right to left. It is reasonable, then stop all of them at the same time. Or maybe 2-3 groups of vms by priority, e.g: default - automatic priority by sequences. highest - must shutdown before any other if we can do that (no dependences) low - shutdown after all other ps. as always sorry for my English -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/6d9d7287-e402-4097-8067-9ee6baed099c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
