Hello, Qubers. Looking for guidance/opinions/best practices. My current storage configuration is pretty simple: main disk (SSD) contains Qubes (dom0 + templates + VMs etc.) all other disks (HDDs) contain regular/personal (non-system) data all disks (SSD + HDDs) are encrypted with LUKS (same passp…

I’m closing this thread with a short report about my experiment: it works. It’s a bit annoying that every time dom0 decrypts a LUKS volume during boot the device gets assigned a new name (dom0:dm-*), but I’ve created a couple of shell scripts that handle that for me, so it’s not too bad. (It would …

Qubes OS Forum

Mounting other disks (HDD, SSD, etc.)

User Support

Johnboy September 6, 2024, 4:38am 7

Persistent attach of device with varying backend name User Support

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?

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled