Do not allows to start TemplateVM again before all its AppMVs are restarted

[marmarek]

Reported by joanna on 30 Mar 2011 09:16 UTC
A practical situation:

1. I have a few AppVMs running
2. I decided to start a TemplateVM and install some new software
3. I restarted only one of my AppVMs (so it could see new software)
4. Now -- don't allow me to start the TemplateVM before I restart (update) all other running AppVMs.

Migrated-From: https://wiki.qubes-os.org/ticket/168

[marmarek]

Comment by marmarek on 30 Mar 2011 23:07 UTC
Is it really good idea to don't allow start new template update, until all AppVMs will be restarted?

This can be annoying, suppose this situation:

1. You have a few AppVMs running, with some applications
2. You decide to start a TemplateVM and install some new software (ex new, powerful editor)
3. You restarted only one of yours AppVMs - to check if new software works as expected
   3a) You discovered that, some essential plug-ins are missing (or simply that this version is buggy, and didn't open your documents)
4. Now, you are forced to restart (or stop) rest of running AppVMs to fix TemplateVM

In fact, you are forced to use buggy template in AppVMs, not good one (but without new software).

Maybe some warning will be enough? And/Or some mark in qubes-manager (red background of AppVM row?).

[marmarek]

Comment by marmarek on 30 Mar 2011 23:07 UTC
Is it really good idea to don't allow start new template update, until all AppVMs will be restarted?

This can be annoying, suppose this situation:

1. You have a few AppVMs running, with some applications
2. You decide to start a TemplateVM and install some new software (ex new, powerful editor)
3. You restarted only one of yours AppVMs - to check if new software works as expected
   3a) You discovered that, some essential plug-ins are missing (or simply that this version is buggy, and didn't open your documents)
4. Now, you are forced to restart (or stop) rest of running AppVMs to fix TemplateVM

In fact, you are forced to use buggy template in AppVMs, not good one (but without new software).

Maybe some warning will be enough? And/Or some mark in qubes-manager (red background of AppVM row?).

[marmarek]

Comment by joanna on 31 Mar 2011 08:39 UTC
Agree. (Just use something like yellow color, instead of red in the manager -- let's try to keep it somehow aesthetic ;)

[marmarek]

Comment by joanna on 31 Mar 2011 08:39 UTC
Agree. (Just use something like yellow color, instead of red in the manager -- let's try to keep it somehow aesthetic ;)

[marmarek]

Modified by marmarek on 1 Apr 2011 10:36 UTC

[marmarek]

Modified by marmarek on 1 Apr 2011 10:36 UTC

[marmarek]

Comment by marmarek on 2 Apr 2011 23:35 UTC
There is warning to restart AppVMs after template shutdown (only if template is stopped by "stop" button in qubes-manager...).
Outdated VMs are marked by red name (any background color change produced more problems, and doesn't look fine...).

[marmarek]

Comment by marmarek on 2 Apr 2011 23:35 UTC
There is warning to restart AppVMs after template shutdown (only if template is stopped by "stop" button in qubes-manager...).
Outdated VMs are marked by red name (any background color change produced more problems, and doesn't look fine...).