Qube autostart broken with assigned block device

Hey there,

I’ve several Qubes that shall autostart and have a block device assigned.
These Qubes won’t, successfully, autostart.

Regarding the block device.
I have a lvm thin pool which also is host to the qubes storage itself. Within I created LVs and assigned them static device mapper IDs, therefore the 410 is always valid.

After I logged in, lvs are active and I can manually start the Qube.

Other Qubes without such assigned block devices autostart just as expected.

Obviously I could try creating an overwrite to the specific qube autostart services but that would miss the point of switching the autostart behavior within the qube config.

Any ideas or leads ?

Well, in an FYI manner for future someone …

Assigning block devices via GUI as “Required Devices” or cli as “qvm-block attach” - bad

Assigning block devices via GUI as “Device Assignment” or cli as “qvm-block assign” - good

2 Likes