Bonjour!
Today (16 February 2026), I updated my Qubes, and after the update, all running VMs were shut down on their on. Now, whenever I try to start any VM, it does not start. Additionally, when I try to open the settings of any VM, I get the following error:
Value Error: Invalid literal for Int () with base 10: 92274688B at line 33 of file/usr/bin/qubes-vm-settings
Any guidance?
Can you post details of that error message?
Do you see also similar error in sudo journalctl -u qubesd output?
This is the output of sudo journalctl -u qubesd :
qubesd.service: start start operation timed out. Terminating.
qubesd.service: Failed with result ‘timeout’.
qubesd.service: Unit process 1931 (lvm) remains running after unit stopped.
Failed to start qubesd.service - Qubes OS daemon.
qubesd.service: Scheduled restart job, restart counter is at 1.
qubesd.service: Found left-over process 1931 (lvm) in control group while starting unit. Ignoring.
qubesd.service: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
qubesd.service: Found left-over process 2976 (lvm) in control group while starting unit. Ignoring.
Uh, start timeout is bad. And lvm that remains running also is not good (it should be short call, should not remain running after qubesd stops). I guess something about LVM itself went wrong. Can you check just sudo journalctl about that time if you seem some LVM-related errors (or generally some other errors before that start timeout)? Maybe something from the kernel about device-mapper (“dm” in short)?