Dom0 faling to update: UpdateVM not running, not starting it in non-interactive mode

User Support
1

I can’t update my dom0 and I know there’s an update because another device running Qubes got an update.

update manager

When I try to update via the update manager I get this output:

  • Checking for available updates for dom0…
    Using sys-whonix as UpdateVM for Dom0
    Checking for dom0 updates…
    ERROR: UpdateVM not running, not starting it in non-interactive mode

Dom0 Xfce terminal

When trying to update from the xfce dom0 cli I get this output:

  • Updating and loading repositories:
    Fedora 37 - x86_64 - Updates ???% | 0.0 B.0 B

What I did after that

  • I created an sys-update vm over vpn and I got the same result.

What did I check?

  • I checked the Qubes global config and it’s set to my update vm.

What else did you notice?

  • All other updates are running, except for dom0

Did I check other posts?

Yes, I checked this error before asking and the only post that shows up is this one:
Github Issue #885 - qubes-dom0-update could check whether /boot is mounted - #15 by alimirjamali —> This doesn’t seems like it doesn’t have to do with my issue.

Question

Please help I, I don’t know how to fix this.

2

That is correct. It is not related to your issue.

Are you 100% percent certain that sys-whonix was running at the time of update?

And if sys-whonix was running, did the Whonix systray widget show the Tor to be connected?

3

Yes, I know for sure! Why do I know? Because I had other updates too - these updated fine. Dom0 was the first to get updated and immediately switched off showing a red cross icon. Furthermore, I’ve been trying to update dom0 for a couple of days now since the other device did get an update. All attempts failed.

→ both tor and vpn updates fail

4

Ok, I’ll switch It back to updating over Whonix maybe that will fix it.

5

Is still

I updated via whonix again and it won’t update :frowning: All the other Qubes are updating as normal.

6

For anyone reading this:

I found the solution:
My default disposable was set to an offline disposable. Therefore dom0 couldn’t connect to the internet and couldn’t update. After I reset my default disposable in Qubes Global config to the normal DVM (disposable virtual machine) it updated as normal.

:grinning:

1 Like