-
-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Very long system shutdown when some VMs were running #1425
Comments
One problem (fans at 100%) is because xenconsoled is stopped while some VMs are still running. But even when that is fixed, shutdown time isn't improved. |
Otherwise still running VMs will hang, consuming 100% CPU. QubesOS/qubes-issues#1425
It may happen (especially when VM doesn't close cleanly and needs to be killed) that qubesdb-daemon will not notice VM shutdown immediately. Normally it would stop after 60s timeout, but speed it up in case of system shutdown QubesOS/qubes-issues#1425
Otherwise still running VMs will hang, consuming 100% CPU. QubesOS/qubes-issues#1425 (cherry picked from commit 46cbb4a)
This is workaround for missing libxl/libvirt functionality: QubesOS/qubes-issues#1426 Also it should improve system shutdown time, as this is the situation where all the VMs are shutting down simultaneously. Fixes QubesOS/qubes-issues#1425 (cherry picked from commit 7359e39)
It may happen (especially when VM doesn't close cleanly and needs to be killed) that qubesdb-daemon will not notice VM shutdown immediately. Normally it would stop after 60s timeout, but speed it up in case of system shutdown QubesOS/qubes-issues#1425 (cherry picked from commit bae493d)
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
Or update dom0 via Qubes Manager. |
When VM is shutting down it doesn't disconnect PCI frontend (?), so when VM is destroyed it ends up in timeouts in PCI backend shutdown (which can't communicate with frontend at that stage). Prevent this by detaching PCI devices while VM is still running. Fixes QubesOS/qubes-issues#1494 Fixes QubesOS/qubes-issues#1425
When VM is shutting down it doesn't disconnect PCI frontend (?), so when VM is destroyed it ends up in timeouts in PCI backend shutdown (which can't communicate with frontend at that stage). Prevent this by detaching PCI devices while VM is still running. Fixes QubesOS/qubes-issues#1494 Fixes QubesOS/qubes-issues#1425 (cherry picked from commit 2658c9a)
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
Or update dom0 via Qubes Manager. |
It takes few minutes to shutdown Qubes when some VMs were running. Additionally system is getting hot at that time (fans spin at 100%).
This problem was supposed to vanish in R3.0 (#903), but apparently it is still there.
The text was updated successfully, but these errors were encountered: