Extra Volumes

[Johnboy]

Is there a simpler way to attach a LV to a AppVM?

sudo lvchange --persistent y --minor NN VG/LV

on thin_pools gives me

Command on LV X/Y with invalid LV type thinpool.
Command not permitted on LV X/Y.

I actually just want a second internal HDD to use in 2 or more AppVMs simulatenously.

This seems to be the solution I am looking for:

Persistent attach of device with varying backend name

I am trying to persistently attach a device which has a varying backend name. This is the guide that I followed to get the backend name It returns something like “dm-85”, but it changes with each boot, so I cant do qvm-block attach -p vmname dom0:dm-85 since it won’t exist on next boot. I can script it to attach it on boot, but then if I restart a VM it won’t be attached anymore. What could be some solutions?