Run a disp1234 independent of the calling system

[rustybird]

@SteveC

So what I am getting from this is, if I (say) open an email attachment in a disposable, and then I close the VM my email client is running in, that disposable will go away as well?

I think that’s the intention, except due to the linked bug it might take a while (or, in the case of qubes.OpenInVM RPC which IIRC doesn’t attempt to send back data until it’s finished anyway, it probably would look like it doesn’t happen at all).

If you need more control over the lifecycle of the disp1234, you’d have to use the admin API as previously discussed:

Disposable VMs' names--can the launcher know the name?

It can be done with the admin API. Assuming you’re in a qube named foo and want to spawn (and communicate with) a new disp1234 qube, which will automatically be cleaned up when it shuts down: readarray -d '' -s 1 disp < <(qrexec-client-vm dom0 admin.vm.CreateDisposable </dev/null) wait $! || # handle error ... qrexec-client-vm "$disp" admin.vm.Start </dev/null qrexec-client-vm "$disp" myservice1+arg1 qrexec-client-vm "$disp" myservice2+arg2 qrexec-client-vm "$disp" admin.vm.Kill </dev/null Wh…