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 upMake it possible to use DispVM as UpdateVM #2801
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
mig5
May 11, 2017
In any case there is a simple way to set up a 'quasi'-disposable VM by writing a wrapper script around the main qubes-dom0-update.
Leaving this here in case the idea is rejected but others still want to do something similar:
https://mig5.net/content/using-quasi-disposable-vm-updatevm-qubes
mig5
commented
May 11, 2017
•
|
In any case there is a simple way to set up a 'quasi'-disposable VM by writing a wrapper script around the main qubes-dom0-update. Leaving this here in case the idea is rejected but others still want to do something similar: https://mig5.net/content/using-quasi-disposable-vm-updatevm-qubes |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
This will be trivial in Qubes 4.0... |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
May 11, 2017
Member
You can create semi-persistent DispVM there - the VM stays on the list, together with its name etc, but its state is discarded as soon as it is stopped.
|
You can create semi-persistent DispVM there - the VM stays on the list, together with its name etc, but its state is discarded as soon as it is stopped. |
andrewdavidwong
added this to the Release 4.0 milestone
May 12, 2017
andrewdavidwong
added
C: core
enhancement
labels
May 12, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Oct 23, 2017
Member
As said before, it is easy in Qubes 4.0:
qvm-create --class DispVM -t fedora-25-dvm -l orange disp-updatevm
qubes-prefs updatevm disp-updatevm
|
As said before, it is easy in Qubes 4.0:
|
mig5 commentedMay 11, 2017
Qubes OS version (e.g.,
R3.2):R3.2
It would be nice to have the ability to make the UpdateVM a Disposable VM. Say, to mitigate the (albeit rare) risk of some existing persistent malware in /rw on the relevant UpdateVM, interfering with handling the dom0 updates before they make their way back to dom0.
Do you think it's possible?
I tried already hacking a solution via piping the tar -C stuff to '/usr/lib/qubes/qfile-daemon-dvm qubes.VMShell dom0 red' but I couldn't get it to work. Maybe it's not possible given how restricted dom0 is in terms of how it can run commands on a dispVM (compared to the easier appVM -> dispVM)