-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
qvm-run should unpause paused VMs #5967
Comments
If qvm-run is run with the autostart option (true by default), it will also unpause paused VMs. fixes QubesOS/qubes-issues#5967
If qvm-run is run with the autostart option (true by default), it will also unpause paused VMs. fixes QubesOS/qubes-issues#5967
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
Or update dom0 via Qubes Manager. |
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
Or update dom0 via Qubes Manager. |
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The component
|
- removed workaround for QubesOS/qubes-issues#5967 as it's fixed upstream - doc - set correct exit code on qvm-start
Qubes OS version
4.0
Affected component(s) or functionality
qvm-run
Brief summary
qvm-run
/qvm-run -a
should unpause paused VMsTo Reproduce
Expected behavior
xterm
is startedActual behavior
After a while (I guess qrexec timeout)
command failed with code: 1
Additional context
qvm-run -a
starts VMs to reach the goal of executing the command.So why not also unpause paused VMs?
qvm-run -n
should still not change the VM state (i.e. keep the VM paused).Maybe the doc would have to be changed to something like
-a
= make the VM run/operate and-n
= do not change the run state of the VM.Solutions you've tried
qvm-unpause somevm
beforeqvm-run
obviously. It's rather inconvenient for manual usage though.Relevant documentation you've consulted
Related, non-duplicate issues
The text was updated successfully, but these errors were encountered: