Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upqvm-shutdown --timeout exits with libvirtError #3755
Comments
andrewdavidwong
added
bug
C: core
labels
Mar 29, 2018
andrewdavidwong
modified the milestones:
Release 4.0,
Release 4.0 updates
Mar 29, 2018
marmarek
closed this
in
QubesOS/qubes-core-admin@f4be284
Apr 5, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
qubesos-bot
Apr 16, 2018
Automated announcement from builder-github
The package qubes-core-dom0-4.0.26-1.fc25 has been pushed to the r4.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
qubesos-bot
commented
Apr 16, 2018
|
Automated announcement from builder-github The package
|
qubesos-bot
added
the
r4.0-dom0-cur-test
label
Apr 16, 2018
qubesos-bot
referenced this issue
in QubesOS/updates-status
Apr 16, 2018
Closed
core-admin v4.0.26 (r4.0) #477
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
qubesos-bot
May 14, 2018
Automated announcement from builder-github
The package qubes-core-dom0-4.0.27-1.fc25 has been pushed to the r4.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.
qubesos-bot
commented
May 14, 2018
|
Automated announcement from builder-github The package
Or update dom0 via Qubes Manager. |
tasket commentedMar 28, 2018
Qubes OS version:
R4.0rc5
Affected component(s):
dom0 tools
Steps to reproduce the behavior:
qvm-shutdown --all --timeout 20Expected behavior:
All VMs are shutdown or killed without errors.
Actual behavior:
One or more VMs are left running and the command exits with an error:
Here is the log output:
General notes:
I'd suggest that qvm_shutdown trap its qvm_kill calls and maybe set a flag noting when an exception occurs. Then a follow-up loop can check VM status and exit with an exception only if VMs remain and could not be killed.
Related issues: