core-dom0 upgarde should either close all vms or none

[marmarek]

Reported by joanna on 4 Apr 2011 21:00 UTC
Currently it tries to remain the netvm running but it actually confuses the netvm with firewallvm and leaves just the fwvm running, but netvm turned off. But it makes little sense to do that - we should either close all the vms (because we might be providing new daemons for Dom0 and we want them to be started after upgrade), or leave all the vms intact. I think we should just shutdown all of them?

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

[marmarek]

Comment by marmarek on 5 Apr 2011 10:06 UTC
I think we don't need VM shutdown on core-dom0 upgrade. Most updates are only qvm-* and qubes.py changes.
Perhaps more sense in shutting down all VMs is on gui-dom0 upgrade...

[marmarek]

Comment by marmarek on 5 Apr 2011 10:06 UTC
I think we don't need VM shutdown on core-dom0 upgrade. Most updates are only qvm-* and qubes.py changes.
Perhaps more sense in shutting down all VMs is on gui-dom0 upgrade...

[marmarek]

Modified by joanna on 6 Apr 2011 11:20 UTC

[marmarek]

Modified by joanna on 6 Apr 2011 11:20 UTC

[marmarek]

Modified by joanna on 6 Apr 2011 11:20 UTC

[marmarek]

Modified by joanna on 6 Apr 2011 11:20 UTC

[marmarek]

Comment by joanna on 6 Apr 2011 12:40 UTC
Decided not to restart qubes_{core,netvm}:

http://git.qubes-os.org/?p=joanna/core.git;a=commitdiff;h=e01b29dd76f081b475066245f194fb6b15e6b1e5

[marmarek]

Comment by joanna on 6 Apr 2011 12:40 UTC
Decided not to restart qubes_{core,netvm}:

http://git.qubes-os.org/?p=joanna/core.git;a=commitdiff;h=e01b29dd76f081b475066245f194fb6b15e6b1e5