> > > > Template for DispVM needs to be an AppVM. So, first create AppVM (or use > fedora-25-dvm provided for this purpose), then set > template_for_dispvms=True and use that AppVM for your DispVM. >
Still confused. The second thing i tried above was make an appvm, then set template_for_dispvms=True. that command returned without error, but it made a standard AppVM, preserving data. Just tried making an appvm to use as a template for a dispvm, qvm-create --class AppVM --template fedora-25 --label black dispvm-template qvm-prefs dispvm-template template_for_dispvms True qvm-create --class DispVM --template dispvm-template --label red mydvm That created a DispVM thats only visible from qvm-ls, and somehow has a black border if you start it with qvm-start. its the only one listed as a DispVM. the two working ones, fedora-25-dvm and whonix-ws-dvm are listed as AppVM Trying the third command with --class AppVM gave an error in journalct that ended with "TypeError: wrong VM class: domains[<AppVM at ... name='dispvm-template'...] is of type AppVM and not TemplateVM" -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-devel+unsubscr...@googlegroups.com. To post to this group, send email to qubes-devel@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/08e685c7-6ca8-46a5-b2cb-3167bb4365a3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
