4 ms·
I have QubesOS with a VM for work and another one for personal things. The nice thing with Qubes is that I can share all the screen in the work VM and people wi
by shaky-carrousel 4y ago
I have QubesOS with a VM for work and another one for personal things. The nice thing with Qubes is that I can share all the screen in the work VM and people will only see work-related windows.
So it doesn't matter what I am browsing in my personal browser, nobody from the work VM can ever see it.
- kevingadd 4y agoI should warn you that it's quite possible for GPU memory to leak into/out of VMs, the safety model is different. So the parent's horror story could absolutely happen to you.
- minimalist 4y agoI think that you are mistaken. In Qubes, none of the VMs have access to the GPU by default[0]. May you elaborate or provide some evidence to support your claim? [0]: Unless you do something "exotic" like pass the GPU through to a particular VM which is not supported and explicitly not recommended for the security reasons that you are thinking about.
- ncmncm 4y agoThe sharing VM has no access to any GPU. The GPU is wholly owned by the dom0 process that copies pixels to screen memory from pages mapped to VMs.
- xvilka 4y agoI hoped they would adopt ReactOS for their Windows containers[1]. [1] https://github.com/QubesOS/qubes-issues/issues/2809 https://github.com/QubesOS/qubes-issues/issues/2809
- heavyset_go 4y agoIn my experience, Wine has better support and is much more stable than ReactOS, especially when using Proton builds.