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 upFeature request: start VM on boot but after login screen #3724
Comments
andrewdavidwong
added
enhancement
C: core
P: minor
labels
Mar 21, 2018
andrewdavidwong
added this to the Far in the future milestone
Mar 21, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
3hhh
commented
Mar 21, 2018
|
related: #3149 |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
shunju
Mar 21, 2018
@3hhh Thank you for making me aware of your issue. I hadn’t found it because the title is phrased in a completely different way, but it basically is the same thing. I’ll close this issue in favor of yours.
shunju
commented
Mar 21, 2018
|
@3hhh Thank you for making me aware of your issue. I hadn’t found it because the title is phrased in a completely different way, but it basically is the same thing. I’ll close this issue in favor of yours. |
shunju
closed this
Mar 21, 2018
andrewdavidwong
added
the
duplicate
label
Mar 22, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
shunju commentedMar 20, 2018
Qubes OS version:
R4.0-rc5
Affected component(s):
I don’t know
Steps to reproduce the behavior:
Select “Start qube automatically on boot” in the settings of a qube.
Expected behavior:
Qubes start after showing the login screen.
Actual behavior:
Qube starts before login screen is shown. Multiple start jobs block the boot process and the login screen is only shown after all qubes are booted. When many qubes are started automatically, this results in a very long boot time.
General notes:
I understand that the current behavior may be desired for sys-usb (when an external keyboard is used for login) and possibly for sys-net and sys-firewall (here I already don’t see when this would be beneficial, because Qubes is a single-user system and therefore doesn’t login via network). But for my work VM, which I always want to start automatically to ensure that files are always synchronized with my NextCloud, there is no reason why its booting process should block the Qubes booting process and prevent me from logging in while it’s booting.
I would try to do this on my own. However, I have neither sufficient knowledge of Qubes nor of X to even know where to start. Also, other users might also consider this an important feature.
My temporary workaround is to put
qvm-runcommands into the Session and Startup. However, in this case VMs start only after I login (thereby wasting time) and sometimes not at all due to #3533.Related issues:
None found.