Skip to content
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

Closed
marmarek opened this issue Nov 14, 2015 · 5 comments
Closed

Very long system shutdown when some VMs were running #1425

marmarek opened this issue Nov 14, 2015 · 5 comments
Labels
C: core C: Xen P: minor Priority: minor. The lowest priority, below "default." r3.0-dom0-stable T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.

Comments

@marmarek
Copy link
Member

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.

@marmarek marmarek added T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists. C: core C: Xen P: minor Priority: minor. The lowest priority, below "default." labels Nov 14, 2015
@marmarek marmarek added this to the Release 3.0 updates milestone Nov 14, 2015
@marmarek
Copy link
Member Author

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.
I guess it's about stopping uplink VMs (NetVMs, ProxyVMs) while still some VMs are connected there - which makes clean network detach impossible (from libvirt point of view).

marmarek added a commit to marmarek/old-qubes-core-admin that referenced this issue Nov 15, 2015
Otherwise still running VMs will hang, consuming 100% CPU.

QubesOS/qubes-issues#1425
marmarek added a commit to marmarek/old-qubes-core-admin that referenced this issue Nov 15, 2015
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
marmarek added a commit to QubesOS/qubes-core-admin that referenced this issue Nov 15, 2015
Otherwise still running VMs will hang, consuming 100% CPU.

QubesOS/qubes-issues#1425

(cherry picked from commit 46cbb4a)
marmarek added a commit to QubesOS/qubes-core-admin that referenced this issue Nov 15, 2015
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)
marmarek added a commit to QubesOS/qubes-core-admin that referenced this issue Nov 15, 2015
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)
@marmarek
Copy link
Member Author

Automated announcement from builder-github

The package qubes-core-dom0-3.0.26-1.fc20 has been pushed to the r3.0 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

@marmarek
Copy link
Member Author

Automated announcement from builder-github

The package qubes-core-dom0-3.0.26-1.fc20 has been pushed to the r3.0 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update

marmarek added a commit to marmarek/old-qubes-core-admin that referenced this issue Dec 6, 2015
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
marmarek added a commit to QubesOS/qubes-core-admin that referenced this issue Jan 15, 2016
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)
@marmarek
Copy link
Member Author

Automated announcement from builder-github

The package qubes-core-dom0-3.0.27-1.fc20 has been pushed to the r3.0 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

@marmarek
Copy link
Member Author

Automated announcement from builder-github

The package qubes-core-dom0-3.0.28-1.fc20 has been pushed to the r3.0 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: core C: Xen P: minor Priority: minor. The lowest priority, below "default." r3.0-dom0-stable T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.
Projects
None yet
Development

No branches or pull requests

1 participant