sys-net cannot start because private image unavailable, 'vm-sys-net-private-tmp' exists

13 views

Skip to first unread message

Pablo Di Noto

unread,

Apr 26, 2018, 12:03:28 PM4/26/18

to qubes-users

Hello,

After a normal reboot I had a working dom0 without any ServiceVM started.
Found that `sys-net` could not start because the 'vm-sys-net-private' LVM volume was missing.

Looking around I found that the '-tmp' version of it was available, and after mounting it I could see the contents of the working 'sys-net' rw volume, so I renamed it back to the proper name and then evertything worked fine.

I am assuming some kind of interrupted internal renaming happened.

What would be the proper way to enable debugging on Qubes LVM operations? Many qvm-* commands --verbose do nothing. Would like to understand the root cause of this if it happens again, but also to understand the inner workings of the Qubes volumen management.

Sometimes I have a 45 second delay from a `qvm-start` and anything showing up on `xl list`, and I suspect some LVM operations may be taking long time to execute.