Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upoption to set the TemplateVM setting for TemplateBasedVMs to none #2062
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Jun 12, 2016
Member
Having template set to "none" means it is Standalone VM (with own root.img etc). So not that simple. But maybe we should ship dummy template?
|
Having template set to "none" means it is Standalone VM (with own |
marmarek
added
enhancement
help wanted
C: core
C: templates
P: major
labels
Jun 12, 2016
marmarek
added this to the Release 4.0 milestone
Jun 12, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
andrewdavidwong
Jun 12, 2016
Member
This makes template reinstallation instructions more difficult than possible.
I started to rewrite that page to generalize it so that the procedure could be used for any TemplateVM (not just Whonix). However, I stopped when the discussion turned toward creating special tools for the job (rather than having the user manually create the dummy template). Here is the latest draft. If you think it's worth finishing and adding to the docs, let me know. If not (e.g., because we don't want users trying to do that, or it's going to be deprecated soon by this option), then that's ok.
I started to rewrite that page to generalize it so that the procedure could be used for any TemplateVM (not just Whonix). However, I stopped when the discussion turned toward creating special tools for the job (rather than having the user manually create the dummy template). Here is the latest draft. If you think it's worth finishing and adding to the docs, let me know. If not (e.g., because we don't want users trying to do that, or it's going to be deprecated soon by this option), then that's ok. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
adrelanos
Jun 12, 2016
Member
I think it's worth being documented because until the improved solution
gets available, users updated, old versions are deprecated and so forth
will probably still take quite some time.
|
I think it's worth being documented because until the improved solution |
added a commit
to QubesOS/qubes-doc
that referenced
this issue
Jun 12, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
andrewdavidwong
Jun 12, 2016
Member
I think it's worth being documented because until the improved solution gets available, users updated, old versions are deprecated and so forth will probably still take quite some time.
|
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Jul 13, 2017
Member
In Qubes 4.0, it's simple to create "dummy" template for this purpose:
qvm-create --class TemplateVM --label red dummy
|
In Qubes 4.0, it's simple to create "dummy" template for this purpose:
|
adrelanos commentedJun 12, 2016
Setting the template to an arbitrary different temporary template during template reinstallation is a bit dangerous. Easily forgotten. Lets say oneyou would not want boot some my-whonix-ws AppVM in a debian-8 template.
This makes template reinstallation instructions more difficult than possible.
Feature request:
Please have an option for
qvm-prefsas well as in QVMM to allow setting the template tonone.Related mailing list discussion:
Is there a standard procedure to reinstall whonix?
Since this touches usability, I am looping in @bnvk.