I’m working on a split-veracrypt schema.
Let’s say dom0 starts a disposable VM…one with the default disp-1234 naming scheme. (Unlocking a veracrypt container and making it available to other vms turns out to be a multi-step process.)
Can dom0 determine what number was appended, in the event s/he wants to communicate with it? Or otherwise have a “handle” to the DVM? Or is it purely “launch and forget”?
(Also applies to other qubes creating the disposable VM via qrexec. Since I might go that route instead.)
I know I could manage this with a named template (one for each veracrypt volume), but if I do that I’m likely going to end up a lot of them cluttering the manager, menus, etc. when they only should be dealt with by other pieces of the split-veracrypt schema.