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 upQubes R4 qvm-run --all regression (starts all VMs) (blocking rather than non-blocking) #3162
Comments
adrelanos
changed the title from
Qubes R4 qvm-run --all regression (starts all VMs)
to
Qubes R4 qvm-run --all regression (starts all VMs) (blocking rather than non-blocing)
Oct 9, 2017
adrelanos
changed the title from
Qubes R4 qvm-run --all regression (starts all VMs) (blocking rather than non-blocing)
to
Qubes R4 qvm-run --all regression (starts all VMs) (blocking rather than non-blocking)
Oct 9, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
marmarek
Oct 9, 2017
Member
This should be fixed in qubes-core-admin-client 4.0.5, what version do you have?
|
This should be fixed in qubes-core-admin-client 4.0.5, what version do you have? |
andrewdavidwong
added
bug
C: core
labels
Oct 10, 2017
andrewdavidwong
added this to the Release 4.0 milestone
Oct 10, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
3hhh
commented
Oct 13, 2017
•
edited
Edited 1 time
-
3hhh
edited Oct 13, 2017 (most recent)
edited
Edited 1 time
-
Oct 13, 2017 (most recent)
|
Related: #3083 |
marmarek
closed this
Oct 19, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
adrelanos
Oct 19, 2017
Member
Marek Marczykowski-Górecki:
This should be fixed in qubes-core-admin-client 4.0.5, what version do you have?
Yes, the updates from Qubes testing sorted this out, thanks! :)
|
Marek Marczykowski-Górecki:
This should be fixed in qubes-core-admin-client 4.0.5, what version do you have?
Yes, the updates from Qubes testing sorted this out, thanks! :)
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
adrelanos commentedOct 9, 2017
•
edited
Edited 1 time
-
adrelanos
edited Oct 9, 2017 (most recent)
Qubes OS version (e.g.,
R3.2):Qubes R4 RC1 with all stable upgrades
Affected TemplateVMs (e.g.,
fedora-23, if applicable):dom0
Steps to reproduce the behavior:
(This was useful in Qubes R2 to work around various reboot/shutdown related hickups. (Shutdown never completing.))
Expected behavior:
Like in Qubes R3.2. The command only being run in VMs currently being running. Not starting all VMs to run the command.
Non-blocking. Running that command on all VMs at once.
Actual behavior:
Starts all VMs.
Blocking. Runs the command in first VM, goes on the next one. Very slow process. No longer useful.