Skip to content
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

Closed
Polygonbugs opened this issue Jun 18, 2018 · 2 comments · Fixed by QubesOS/qubes-core-admin#238
Closed
Labels
C: core r4.0-dom0-stable T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.

Comments

@Polygonbugs
Copy link

Polygonbugs commented Jun 18, 2018

Qubes OS version:

R4.0

Affected component(s):

qvm-service, Qubes-Manager(?)


Steps to reproduce the behavior:

  1. Create USB qube manually and check automatically start
  2. Assign PCI USB controller on the VM with pci_strict_reset false
  3. Delete USB qube via Qubes-Manager
  4. Restarting system
  5. Boot screen shows that "Deleted USB qube" failed to boot

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

@andrewdavidwong andrewdavidwong added T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists. C: core labels Jun 18, 2018
@andrewdavidwong andrewdavidwong added this to the Release 4.0 updates milestone Jun 18, 2018
marmarek added a commit to marmarek/qubes-core-admin that referenced this issue Oct 21, 2018
marmarek added a commit to marmarek/qubes-core-admin that referenced this issue Oct 21, 2018
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
marmarek added a commit to marmarek/qubes-core-admin that referenced this issue Oct 23, 2018
marmarek added a commit to marmarek/qubes-core-admin that referenced this issue Oct 23, 2018
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
marmarek added a commit to marmarek/qubes-core-admin that referenced this issue Oct 23, 2018
marmarek added a commit to marmarek/qubes-core-admin that referenced this issue Oct 23, 2018
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
marmarek added a commit to marmarek/qubes-core-admin that referenced this issue Oct 23, 2018
marmarek added a commit to marmarek/qubes-core-admin that referenced this issue Oct 23, 2018
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
marmarek added a commit to marmarek/qubes-core-admin that referenced this issue Oct 24, 2018
marmarek added a commit to marmarek/qubes-core-admin that referenced this issue Oct 24, 2018
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
marmarek added a commit to marmarek/qubes-core-admin that referenced this issue Oct 25, 2018
marmarek added a commit to marmarek/qubes-core-admin that referenced this issue Oct 25, 2018
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
marmarek added a commit to marmarek/qubes-core-admin that referenced this issue Oct 26, 2018
marmarek added a commit to marmarek/qubes-core-admin that referenced this issue Oct 26, 2018
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
@qubesos-bot
Copy link

Automated announcement from builder-github

The package qubes-core-dom0-4.0.33-1.fc25 has been pushed to the r4.0 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

@qubesos-bot
Copy link

Automated announcement from builder-github

The package qubes-core-dom0-4.0.37-1.fc25 has been pushed to the r4.0 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: core r4.0-dom0-stable T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants