Rusty Bird f96fd70f76 Don't fire domain-stopped/-shutdown while VM is still Dying ... Lots of code expects the VM to be Halted after receiving one of these events, but it could also be Dying or Crashed. Get rid of the Dying case at least, by waiting until the VM has transitioned out of it. Fixes e.g. the following DispVM cleanup bug: $ qvm-create -C DispVM --prop auto_cleanup=True -l red dispvm $ qvm-start dispvm $ qvm-shutdown --wait dispvm # this won't remove dispvm $ qvm-start dispvm $ qvm-kill dispvm # but this will		2018-02-22 19:53:29 +00:00
..
mix	vm/mix/net: fix handling network detach/attach on VM startup	2018-01-29 23:06:21 +01:00
__init__.py	vm: include tag/feature name in event name	2018-01-06 15:05:34 +01:00
adminvm.py	vm/adminvm: fix type of AdminVM.qid	2017-12-21 18:18:12 +01:00
appvm.py	Fix too long line	2018-02-13 11:27:59 +01:00
dispvm.py	Make AppVM/DispVM root volume rw to avoid CoW-on-CoW	2018-02-12 21:20:04 +00:00
qubesvm.py	Don't fire domain-stopped/-shutdown while VM is still Dying	2018-02-22 19:53:29 +00:00
standalonevm.py	Change license to LGPL v2.1+	2017-10-12 00:11:50 +02:00
templatevm.py	Change license to LGPL v2.1+	2017-10-12 00:11:50 +02:00