Opened 17 months ago
Closed 16 months ago
#396 closed defect (fixed)
VM shutdown is not clean
| Reported by: | joanna | Owned by: | joanna |
|---|---|---|---|
| Priority: | minor | Milestone: | Release 1 Beta 3 |
| Component: | core | Keywords: | |
| Cc: | marmarek |
Description
Every time I shutdown my system I get an error message that netvm cannot be shutdown because there are other VMs connected to it.
1) Maybe there is a missing '=' in the --exclude option in the command below:
qvm-run -q --shutdown --all --wait --exclude $NETVM
2) Even if we fixed the command above, it still doesn't solve the more generic problem when there are more than one NetVM, and also some more ProxyVMs, etc.
So, I think that qvm-run --shutdown should automatically take care about figuring out the VMs hierarchy (in terms of net service) and shut them down in an appropriate order.
Also, perhaps we should move the qvm-run --shutdown logic into a separate tool qvm-shutdown, as this logic got too shutdown-specific?
Change History (1)
comment:1 Changed 16 months ago by marmarek
- Resolution set to fixed
- Status changed from new to closed

All VMs can be stopped simultaneously (including ProxyVMs, NetVMs), netfront/back module should deal with it.
Fixed here:
http://git.qubes-os.org/gitweb/?p=marmarek/core.git;a=commit;h=cd64f8287cb29c1a5b9333284c1bf5a29f498bd7