-
-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'qubesdb-read /qubes-vm-type' should not output 'DisposableVM' #1935
Comments
This is for compatibility with configuration/scripts created before |
And BTW - the case when it will be a problem with be possible only in Qubes 4.0 or later. Before that we don't support disposable ProxyVMs. |
In the future (Qubes 4.0), there will be no separate type ProxyVM or NetVM - it will be just VM property ( |
I think @adrelanos was right to say that |
|
This somehow diverge from class names in core scripts - where (in Qubes 4.0) the only think distinguishing classes is persistence, not purpose. There is |
@adrelanos does it block any Whonix-related task? If not, I'd postpone it until Qubes 4.0, where VM types will be greatly simplified. |
Marek Marczykowski-Górecki:
Qubes 4.0 is fine. (I was just forward thinking making a disposable |
Disp3030:
whonix-ws-14-dvm:
Therefore we can consider this issue solved? |
Qubes OS version (e.g.,
R3.1
):R3.1
Affected TemplateVMs (e.g.,
fedora-23
, if applicable):Probably all.
Expected behavior:
qubesdb-read /qubes-vm-type
should output either:AppVM
,ProxyVM
,NetVM
,TemplateVM'
Actual behavior:
qubesdb-read /qubes-vm-type
does output either:AppVM
,ProxyVM
,NetVM
,TemplateVM
,DisposableVM
Steps to reproduce the behavior:
Run
qubesdb-read /qubes-vm-type
in aDisposableVM
.General notes:
qubesdb-read /qubes-vm-type
should not outputDisposableVM
. This is whatqubesdb-read /qubes-vm-persistence
is for, which outputs eitherfull
(TemplateVM or Standalone),rw-only
(TemplateBasedVM) ornone
(DispVM).qubes-vm-type
is being overloaded. There could be in future a disposable ProxyVM. At that point, there would be two ways to find out it's a disposable VM, but no way (usingqubesdb-read
) to find out it's a ProxyVM.The text was updated successfully, but these errors were encountered: