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 upDispVM changes in Qubes 4.0 #2253
Comments
marmarek
added
C: core
task
labels
Aug 16, 2016
marmarek
added this to the Release 4.0 milestone
Aug 16, 2016
added a commit
to marmarek/qubes-linux-utils
that referenced
this issue
Aug 16, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Aug 16, 2016
Member
Some naive benchmark of non-savefile based DispVM:
- Qubes 3.2, savefile based DispVM startup, with savefile generation: 25.5s
- Qubes 3.2, savefile based DispVM startup, without savefile generation: 4s
- Qubes 4.0, non-savefile based DispVM startup: 9.5s
Test done calling time qvm-run --dispvm date from a VM. Starting some real application will take some more time, but probably will take the same time regardless of DispVM startup method.
Tests done on Librem 13, with SSD disk.
|
Some naive benchmark of non-savefile based DispVM:
Test done calling |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Aug 16, 2016
Member
Qrexec policy changes documented here: https://www.qubes-os.org/doc/qrexec3/#extra-keywords-available-in-qubes-40-and-later
|
Qrexec policy changes documented here: https://www.qubes-os.org/doc/qrexec3/#extra-keywords-available-in-qubes-40-and-later |
marmarek commentedAug 16, 2016
•
edited
Edited 1 time
-
marmarek
edited Jul 31, 2017 (most recent)
This ticket is for tracking DispVM changes in Qubes 4.0:
"DispVM" by adding "$dispvm:vmname" option. Have "$dispvm" mean "default
DispVM", not "any DispVM".
References: