On Sat, Jul 11, 2020 at 04:40:57PM -0700, Robert Spigler wrote: > I have a debian-10-dvm and a whonix-ws-15-dvm. I also had a fedora-30-dvm, > but when upgrading to fedora-32, I followed "Creating a New DisposableVM > Template" here: (https://www.qubes-os.org/doc/disposablevm-customization/), > so no longer have the fedora-30-dvm. Instead, I have a > custom-disposablevm-template based on fedora-32. I would prefer to rename > this to fedora-32-dvm-template, but renaming fails with 'Failed to clone > appmenus'. > > My main question/problem is that unlike the debian-10-dvm and > whonix-ws-15-dvm, opening an application in fedora-32-dvm-template does not > open a disposableVM (disp####), instead it opens > 'custom-disposablevm-template'. IIUC, that is because I am supposed to > create fedora-32-dvm from the dvm-template. But I cannot figure out how to > do that. It is set as the default disposableVM template, so opening files > through the GUI in a disposableVM will open them in a disposableVM based on > fedora-32, but I would still like to be able to open an application through > the GUI/start menu in a fedora-32-dvm. > > What I am also having trouble understanding is what dvm-template is the > debian-10-dvm and whonix-ws-15-dvm based on? I know Qubes4.0 introduced > multiple DVMTemplates, but I don't see any other DVMTemplates listed under > the start menu. In Qubes Manager, debian-10-dvm and whonix-ws-15-dvm are > marked as being their own DVMTemplates? But also DVM's themselves? > > Thank you, > > Robert >
Hi Robert, As you say, Qube 4.0 allowed for the use of many DVMTemplates - any qube can be used as the basis for disposableVMs. So the debian-10-dvm is not based on a dvm-template - it *is* a dvm-template, a qube using the debian-10 template which has had the `template_for_dvms` flag set. That's all there is to it. In your case, I suspect that the appmenus have not been correctly set, so that they still refer to 'custom-disposablevm-template', instead of using that as the basis for a disposableVM. You can try running the command `qvm-features custom-disposablevm-template appmenus-dispvm 1`, although there was an open issue about this command failing in some cases. In dom0, (and therefore the menus), the difference is between: qvm-run custom-disposablevm-template --service qubes.StartApp+xterm and qvm-run dispvm=custom-disposablevm-template --service qubes.StartApp+xterm hth unman -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20200712122741.GC922%40thirdeyesecurity.org.
