VMs cannot start

[tortugaverde98]

Qubes 4.0

Affected component(s):

All VMs

Steps to reproduce the behavior:

Boot computer, decrypt, and log in.

Expected behavior:

VMs start as usual, sys-usb, sys-net, sys-firewall, etc.

Actual behavior:

No VMs start. No USB items function. When attempting to start a VM, an error is provided:

ERROR: b' Logical Volume "vm-sys-usb-root-snap" already exists in volume group "qubes_dom0" \n'

Everything appeared normal when I shut it down last night, with the exception that I had to kill the vault VM since it repeatedly prompted for it. That was the first time vault didn't shut down cleanly on its own. Typically that only happens with the VPN VMs and it never caused a problem.

I rebooted repeatedly today in hopes it would resolve itself but to no avail.

Any VM which has internet access, when attempting to start, references vm-sys-net-root-snap in the error. Presumably because that is the first VM in the chain that must start.

Oddly, except sys-usb which references itself, VMs which do not have internet access, such as vault, when attempting to start, provide a different, puzzling error:

ERROR: b" Can't create snapshot vm-sys-whonix-private as origin vm-sys-whonix-private -snap is not suspended.\n Failed to suspend qubes_dom0/pool00 with queued messages.\n"

Why offline VMs should refer to sys-whonix is beyond me.

I lack the skills to troubleshoot this. Any and all help would be extremely appreciated.

General notes:

---

Related issues:

[tortugaverde98]

I ran:
sudo lvm

Template have three items listed:
templatename-private
templatename-root
templatename-root-152682xxxx-back

Most app VMs have two items:
vmname-private
vmname-15282xxxxx-private

But sys-usb, sys-net, and sys-firewall have five:
-private
-private-15282xxxxx-back
-private-snap
-root-snap
-volatile

sys-whonix has four:
-private
-private-15282xxxxx-back
-private-snap
-private-tmp

I'm at risk of losing a couple weeks worth of intense work. Please advise.

[tortugaverde98]

I ran:
sudo lvm

Template have three items listed:
templatename-private
templatename-root
templatename-root-152682xxxx-back

Most app VMs have two items:
vmname-private
vmname-15282xxxxx-private

But sys-usb, sys-net, and sys-firewall have five:
-private
-private-15282xxxxx-back
-private-snap
-root-snap
-volatile

sys-whonix has four:
-private
-private-15282xxxxx-back
-private-snap
-private-tmp

I'm at risk of losing a couple weeks worth of intense work. Please advise.

[marmarek]

You can remove -root-snap volume of VMs not currently running (sys-usb, sys-net etc) - it is created during VM startup (as a snapshot of template), but apparently it failed to remove it after previous shutdown (a crash?)

But first check one more thing - in lvs command output there is Data% and Meta% column - check if any of volumes isn't full or nearly full, especially in Meta% column.

[marmarek]

You can remove -root-snap volume of VMs not currently running (sys-usb, sys-net etc) - it is created during VM startup (as a snapshot of template), but apparently it failed to remove it after previous shutdown (a crash?)

But first check one more thing - in lvs command output there is Data% and Meta% column - check if any of volumes isn't full or nearly full, especially in Meta% column.

[tortugaverde98]

Data% for pool00 is 62.11
Meta for pool00 is 34.22

The data column is populated for all items, but meta has data only for pool00.

I ran:
sudo lvremove qubes_dom0 vm-sys-usb-root-snap

After a brief heart attack, i said 'n' to removing the pool(!). Then i said no to every other prompt, watching for vm-sys-usb-root-snap. However, no -root-snaps were ever presented in the list of items to which i had to declare y/n.

Yet they continue to exist in sudo lvm.

Another note is when declaring no to -private-snaps for sys-usb and sys-net, instead of the usual response 'logical volume xxx not removed', additional errors were displayed:
Can't create snapshot vm-sys-whonix-private as origin vm-sys-whonix-private-snap is not suspended.
Failed to suspend qubes_dom0/pool00 with queued messages.
Failed to update pool qubes_dom0/pool00.

Is there a way i can attempt to suspend vm-sys-whonix-private-snap? Is that what is holding everything up?

[tortugaverde98]

Data% for pool00 is 62.11
Meta for pool00 is 34.22

The data column is populated for all items, but meta has data only for pool00.

I ran:
sudo lvremove qubes_dom0 vm-sys-usb-root-snap

After a brief heart attack, i said 'n' to removing the pool(!). Then i said no to every other prompt, watching for vm-sys-usb-root-snap. However, no -root-snaps were ever presented in the list of items to which i had to declare y/n.

Yet they continue to exist in sudo lvm.

Another note is when declaring no to -private-snaps for sys-usb and sys-net, instead of the usual response 'logical volume xxx not removed', additional errors were displayed:
Can't create snapshot vm-sys-whonix-private as origin vm-sys-whonix-private-snap is not suspended.
Failed to suspend qubes_dom0/pool00 with queued messages.
Failed to update pool qubes_dom0/pool00.

Is there a way i can attempt to suspend vm-sys-whonix-private-snap? Is that what is holding everything up?

[tortugaverde98]

The Origin column is blank except for sys-usb, sys-net, sys-firewall, and sys-whonix.
For usb, net, and fw, origin shows -private and the template -root.

For sys-whonix, origin shows -snap and two -tmp.

I attempted qvm-shutdown on all four of these VMs, but gave Shutdown error: domain is powered off. No VMs are running.

[tortugaverde98]

The Origin column is blank except for sys-usb, sys-net, sys-firewall, and sys-whonix.
For usb, net, and fw, origin shows -private and the template -root.

For sys-whonix, origin shows -snap and two -tmp.

I attempted qvm-shutdown on all four of these VMs, but gave Shutdown error: domain is powered off. No VMs are running.

[tortugaverde98]

I ran:
sudo lvremove vm-sys-whonix-private-tmp

But it is still there, referenced twice in Origin column, once for -private-15268xxxx-back and once for -snap.

However, when i ran it again, it did not appear in the list of items for y/n, but still listed in sudo lvm.

Attempted:
qvm-remove sys-whonix
qvm-remove: error: Domain is in use: 'sys-whonix'; details in system log

systemctl | grep sys-whonix
qubes-vm@sys-whonix.service loaded failed failed Start Qubes VM sys-whonix

Rebooted, no change.

[tortugaverde98]

I ran:
sudo lvremove vm-sys-whonix-private-tmp

But it is still there, referenced twice in Origin column, once for -private-15268xxxx-back and once for -snap.

However, when i ran it again, it did not appear in the list of items for y/n, but still listed in sudo lvm.

Attempted:
qvm-remove sys-whonix
qvm-remove: error: Domain is in use: 'sys-whonix'; details in system log

systemctl | grep sys-whonix
qubes-vm@sys-whonix.service loaded failed failed Start Qubes VM sys-whonix

Rebooted, no change.

[marmarek]

sudo lvremove qubes_dom0 vm-sys-usb-root-snap

Should be lvremove qubes_dom0/vm-sys-usb-root-snap

Can't create snapshot vm-sys-whonix-private as origin vm-sys-whonix-private-snap is not suspended.
Failed to suspend qubes_dom0/pool00 with queued messages.
Failed to update pool qubes_dom0/pool00.

Is sys-whonix running?

qvm-remove sys-whonix
qvm-remove: error: Domain is in use: 'sys-whonix'; details in system log

See journalctl command for details. Probably it is set as a netvm to anon-whonix and whonix-ws-dvm. Anyway, removing sys-whonix shouldn't be needed to fix your problem.

[marmarek]

sudo lvremove qubes_dom0 vm-sys-usb-root-snap

Should be lvremove qubes_dom0/vm-sys-usb-root-snap

Can't create snapshot vm-sys-whonix-private as origin vm-sys-whonix-private-snap is not suspended.
Failed to suspend qubes_dom0/pool00 with queued messages.
Failed to update pool qubes_dom0/pool00.

Is sys-whonix running?

qvm-remove sys-whonix
qvm-remove: error: Domain is in use: 'sys-whonix'; details in system log

See journalctl command for details. Probably it is set as a netvm to anon-whonix and whonix-ws-dvm. Anyway, removing sys-whonix shouldn't be needed to fix your problem.

[tortugaverde98]

I ran lvremove qubes_dom0/vm-sys-usb-root-snap
Results in this error:
Can't create snapshot vm-sys-whonix-private as origin vm-sys-whonix-private -snap is not suspended.
Failed to suspend qubes_dom0/pool00 with queued messages.
Failed to update pool qubes_dom0/pool00.

Sys- whonix is not running. I also set it to autostart false and rebooted, no change.

Journalctl provides a mountain of info. I cannot scroll up to find a root cause.

[tortugaverde98]

I ran lvremove qubes_dom0/vm-sys-usb-root-snap
Results in this error:
Can't create snapshot vm-sys-whonix-private as origin vm-sys-whonix-private -snap is not suspended.
Failed to suspend qubes_dom0/pool00 with queued messages.
Failed to update pool qubes_dom0/pool00.

Sys- whonix is not running. I also set it to autostart false and rebooted, no change.

Journalctl provides a mountain of info. I cannot scroll up to find a root cause.

[tortugaverde98]

Success. I ran:
sudo lvremove qubes_dom0/vm-sys-whonix-private-snap

It successfully deleted. From there all VMs can start. I rebooted qubes to be sure. Everything comes up cleanly.

[tortugaverde98]

Success. I ran:
sudo lvremove qubes_dom0/vm-sys-whonix-private-snap

It successfully deleted. From there all VMs can start. I rebooted qubes to be sure. Everything comes up cleanly.

[subvertising]

Hello guys. I met the same problem. Just one hour ago I manually shutted down my Qubes 4 because it freezes during the work.
After reboot I try to run any AppVM and get:

ERROR: b" Can't create snapshot vm-sys-firewall-private-15288xxxxx-back as origin vm-sys-firewall-private is not suspended.\n Failed to suspend qubes_dom0/pool00 with queued messages.\n"

Then I try to start sys-net and see following:

ERROR: b' Lobical Volume "vm-sys-net-volatile" already exists in volume group "qubes_dom0"\n'

I don't know what to do to fix it. I tried yours " sudo lvremove qubes_dom0/vm-sys-whonix-private-snap" but, as I think (I'm noob) it is not connected with sys-net and sys-firewall in my case.

Then I tried
sudo lvremove qubes_dom0/vm-sys-firewall-private-snapand sudo lvremove qubes_dom0/vm-sys-firewall-private-15288xxxxx-back with no succes.

Please help me. I can't start any my AppVM and it's critically for me.

[subvertising]

Hello guys. I met the same problem. Just one hour ago I manually shutted down my Qubes 4 because it freezes during the work.
After reboot I try to run any AppVM and get:

ERROR: b" Can't create snapshot vm-sys-firewall-private-15288xxxxx-back as origin vm-sys-firewall-private is not suspended.\n Failed to suspend qubes_dom0/pool00 with queued messages.\n"

Then I try to start sys-net and see following:

ERROR: b' Lobical Volume "vm-sys-net-volatile" already exists in volume group "qubes_dom0"\n'

I don't know what to do to fix it. I tried yours " sudo lvremove qubes_dom0/vm-sys-whonix-private-snap" but, as I think (I'm noob) it is not connected with sys-net and sys-firewall in my case.

Then I tried
sudo lvremove qubes_dom0/vm-sys-firewall-private-snapand sudo lvremove qubes_dom0/vm-sys-firewall-private-15288xxxxx-back with no succes.

Please help me. I can't start any my AppVM and it's critically for me.

[subvertising]

When I try:
sudo lvremove qubes_dom0/vm-sys-net-volatile
I recieve:

Can't create snapshot vm-sys-firewall-private-15288xxxxx-back as origin vm-sys-firewall-private-snap is not suspended.
Failed to suspend qubes_dom0/pool00 with queued messages.
Failed to update pool qubes_dom0/pool00.

[subvertising]

When I try:
sudo lvremove qubes_dom0/vm-sys-net-volatile
I recieve:

Can't create snapshot vm-sys-firewall-private-15288xxxxx-back as origin vm-sys-firewall-private-snap is not suspended.
Failed to suspend qubes_dom0/pool00 with queued messages.
Failed to update pool qubes_dom0/pool00.