-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
"Service VM autostart failed" at boot screen after deleting VM #4014
Comments
If domain is set to autostart, qubes-vm@ systemd service is used to start it at boot. Cleanup the service when domain is removed, and similarly enable the service when domain is created and already have autostart=True. Fixes QubesOS/qubes-issues#4014
If domain is set to autostart, qubes-vm@ systemd service is used to start it at boot. Cleanup the service when domain is removed, and similarly enable the service when domain is created and already have autostart=True. Fixes QubesOS/qubes-issues#4014
If domain is set to autostart, qubes-vm@ systemd service is used to start it at boot. Cleanup the service when domain is removed, and similarly enable the service when domain is created and already have autostart=True. Fixes QubesOS/qubes-issues#4014
If domain is set to autostart, qubes-vm@ systemd service is used to start it at boot. Cleanup the service when domain is removed, and similarly enable the service when domain is created and already have autostart=True. Fixes QubesOS/qubes-issues#4014
If domain is set to autostart, qubes-vm@ systemd service is used to start it at boot. Cleanup the service when domain is removed, and similarly enable the service when domain is created and already have autostart=True. Fixes QubesOS/qubes-issues#4014
If domain is set to autostart, qubes-vm@ systemd service is used to start it at boot. Cleanup the service when domain is removed, and similarly enable the service when domain is created and already have autostart=True. Fixes QubesOS/qubes-issues#4014
If domain is set to autostart, qubes-vm@ systemd service is used to start it at boot. Cleanup the service when domain is removed, and similarly enable the service when domain is created and already have autostart=True. Fixes QubesOS/qubes-issues#4014
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
Or update dom0 via Qubes Manager. |
Qubes OS version:
R4.0
Affected component(s):
qvm-service, Qubes-Manager(?)
Steps to reproduce the behavior:
Expected behavior:
Since VM is deleted, it shouldn't show any error message.
Actual behavior:
Failed to start log of removed VM on boot screen.
General notes:
Here are some command outputs.
[Polygonbugs@dom0 ~] systemctl status [email protected]
qvm-service : error : no such domain : Sys-USB-1
[email protected]: Main Process exited, code=exited, status=2/INVALIDARGUMENT
Failed to start Start Qubes VM Sys-USB-1
[email protected]: Unit entered failed state
[email protected]: Failed with result 'exit-code'
[Polygonbugs@dom0 ~] qvm-service -l Sys-USB-1
qvm-service : error : no such domain : Sys-USB-1
[Polygonbugs@dom0 ~] qvm-service -d Sys-USB-1
qvm-service : error : no such domain : Sys-USB-1
The text was updated successfully, but these errors were encountered: