I messed up my template

I messed up my template. But I can’t reinstall it because it’s already installed.

I’m assuming this is due to this bug:

Now my question: How can I avoid this from the start?

I’m reinstalling Qubes OS and the TemplateVM as well.

What do I do next?
Can I create a “debian-minimal-2” TemplateVM from the “debian-minimal” TemplateVM?
And then create an AppVM from “debian-minimal-2”?

No need to reinstall QubeOS. Just delete the messed up template (make sure to temporarily assign your AppVMs to another template) and then re-install it. You can also clone the messed up template beforehand if you wish to keep it.

Can I create a “debian-minimal-2” TemplateVM from the “debian-minimal” TemplateVM?

Yes, by cloning the template. I have dozens of templates created in this way

2 Likes

Somewhat easier to use qvm-template
qvm-template reinstall TEMPLATE-NAME
which reinstalls in place even if qubes using the template are running.

I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.

5 Likes

If you haven’t restarted a VM too often since it became messed up, you can also revert its storage to a previous good state:

For a TemplateVM, it’s the ‘root’ volume though that should be reverted instead of (or in addition to) the ‘private’ volume.

2 Likes

Do not ever modify templates provided by Qubes OS - don’t even start them (except for updates via Qubes Update Manager thingy).

Clone them to new templates, give them a custom name, and then use those customized templates.

Its not a good idea to customize the original templates. Always clone, and customize those.

1 Like