Use the documentation of (Disposable VM Customization)
Following the ( Creating a new DisposableVM Template)
With these command…
[user@dom0 ~]$ qvm-create --template anon-whonix --label red custom-disposablevm-template
I hit enter to input and get
app: Error creating VM: Got empty response from Qubesd. See journal to in dom0 for details…
I see what the issue is. You’re selecting anon-whonix as the template. However that is not possible as `anon-whonix is not a Template (it’s an AppVM). The template you probably want is whonix-ws-15, which is also the same
[user@dom0 ~]$ qvm-create --template whonix-ws-15 --label red custom-disposablevm-template
And then you continue with the other commands suggester per documentation:
If you clone an infected the new one will also be infected. If you clone an AppVM that is not infected and the clone gets infected the original AppVM does not get infected.
qvm-create --template anon-whonix --label red custom-disposablevm-template
Others in this thread have already explained dispvm templates. For the
benefit of other reading this thread later let me add:
anon-whonix is a appvm based on the whonix-ws template
one can make it or any other appvm into a template for dispvms by
setting the respective property as discussed in this thread
one can also use qvm-create to create a named dispvm like so:
qvm-create --class DispVM --template dispvm-template --label red
named-dispvm
…where dispvm-template is the appvm with the template_for_dispvms
property set and named-dispvm is the name of the named dispvm to be created.
Such named dispvms behave just like the randomly named ones (disp1234)
in that there is no persistence at all, but it will always have the same
name and be listed in the Qube Manager.