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 4.0rc2, 17 Updates today 21/11, no vms are starting (log attached) #3324
Comments
mannp
changed the title from
Qubes 4.0rc2, 17 Updates today 21/11, no vms are starting
to
Qubes 4.0rc2, 17 Updates today 21/11, no vms are starting (log attached)
Nov 21, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
Check if you have some previous error about qubes-qmemman service. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
mannp
Nov 21, 2017
I had ;
qubes-qmemman.service: Job qubes-qmemman.service/start deleted to break ordering cycle starting with qubes-core.service/start
in red text.
mannp
commented
Nov 21, 2017
•
|
I had ;
in red text. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
Should be fixed here: |
marmarek
closed this
Nov 21, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
mannp
commented
Nov 21, 2017
|
Excellent response time :) thank you. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
marmarek
Nov 21, 2017
Member
Immediate solution is to start qmemman: sudo systemctl start qubes-qmemman.service
|
Immediate solution is to start qmemman: |
andrewdavidwong
added
the
resolved
label
Nov 22, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
mannp commentedNov 21, 2017
•
edited
Edited 6 times
-
mannp
edited Nov 21, 2017 (most recent)
-
mannp
edited Nov 21, 2017
-
mannp
edited Nov 21, 2017
-
mannp
edited Nov 21, 2017
-
mannp
edited Nov 21, 2017
-
mannp
edited Nov 21, 2017
Qubes OS version:
v4rc2
Affected TemplateVMs:
All
Steps to reproduce the behavior:
Install all 17 updates from this morning and reboot the machine.
Expected behavior:
Vm's start as usual.
Actual behavior:
Nothing starts and an error is reported in journalctl -> removed as fix provided.
Edit: A second reboot has allowed the sys-net and sys-firewall to start and things seem ok, will continue to check and leave this up incase the log flags anything.
General notes:
Thanks for all the updates to bugs though :)
Related issues: