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 upqvm-prefs claims to be able to modify dom0 #2722
Comments
kulinacs
referenced this issue
in QubesOS/qubes-core-admin
Mar 22, 2017
Merged
Added dom0 check to qvm-prefs #96
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
andrewdavidwong
Mar 22, 2017
Member
[Copying Marek's response here for anyone who doesn't look at the thread.]
On 2017-03-21 18:09, Marek Marczykowski-Górecki wrote:
On Tue, Mar 21, 2017 at 07:54:12PM -0500, Nicklaus McClendon wrote:
Currently, qvm-prefs allows you to edit dom0 settings, while Qubes
Manager does not. When listing attributes, qvm-prefs claims dom0 has a
VM directory, when it currently doesn't. Is qvm-prefs' ability to
modify dom0 desired behavior?No, it isn't. Those settings have no effect on dom0.
|
[Copying Marek's response here for anyone who doesn't look at the thread.] On 2017-03-21 18:09, Marek Marczykowski-Górecki wrote:
|
kulinacs commentedMar 22, 2017
Qubes OS version (e.g.,
R3.2):R3.2
Affected TemplateVMs (e.g.,
fedora-23, if applicable):dom0
Expected behavior:
qvm-prefs should not list dom0, or allow it to be edited
Actual behavior:
qvm-prefs does list dom0 and allow it to be edited
Steps to reproduce the behavior:
run
qvm-prefs -l dom0in dom0General notes:
Mailing list thread: https://groups.google.com/forum/#!topic/qubes-devel/pRkDqzK0hzg