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 upConsider implementing persistent VM custom config setting #895
Comments
marmarek
assigned
rootkovska
Mar 8, 2015
marmarek
added this to the
Release 2.1 (post R2) milestone
Mar 8, 2015
marmarek
added
enhancement
C: core
P: major
labels
Mar 8, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
andrewdavidwong
Apr 21, 2016
Member
Just doing a routine check: Is it still correct that @rootkovska is assigned to this issue?
|
Just doing a routine check: Is it still correct that @rootkovska is assigned to this issue? |
marmarek
unassigned
rootkovska
Apr 21, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
No. That must be some bug in ticket migration script. |
andrewdavidwong
added
the
help wanted
label
Jun 9, 2016
added a commit
that referenced
this issue
Jun 9, 2016
marmarek
modified the milestones:
Release 4.0,
Release 2.0 updates
Oct 5, 2016
marmarek
assigned
woju
Oct 5, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
fixed as side effect of #1798 |
woju
closed this
Oct 6, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
marmarek commentedMar 8, 2015
Reported by marmarek on 4 Sep 2014 22:15 UTC
Currently the only (easy) way to use custom Xen config is to provide --custom-config option to qvm-start '''every time'''. Alternatively one can edit qubes.xml, which isn't easy at all.
Perhaps the better idea is to provide some persistent way to set config file, or simply use
custom.confin VM directory if exists. But it will require clear UI indication that most of VM settings will be ignored in that case (memory size, kernel, netvm etc).Migrated-From: https://wiki.qubes-os.org/ticket/895