On 6/9/19 2:01 PM, 'kht-lists' via qubes-users wrote:
After watching Matthew Wilson's excellent video and reviewing various
FAQs and documents on the qubes-os web site I find myself with a basic
philosophical question. Currently I run CentOS 7 on a workstation and
have installed the VMWare Workstation/Player environment. I have a
number of Virtual Machines created (CentOS, Ubuntu, Linux Mint etc.)
which I run for various purposes. They are SOMEWHAT isolated from each
other but not as well isolated as they would be in qubes-os. The video
and the screenshots on the qubes-os web site seem to show only single
applications running in separate security domains. If it is desired to
run two applications in the same security domain it is necessary to
launch them separately from the dom0 menu. I think this invokes two
copies of the VM OS template, one for each application
That's wrong. Qubes uses the same VM instance for multiple applications
(when they are invoked for that VM).
- although I
might be wrong. My question is...
Can qubes-os invoke a complete OS with Desktop, menu etc. within a
security domain? This would be similar to what I do in VMWare. I tend
to run a given VM on one workspace and the second on a different
workspace so that I can change between them and make good use of the
monitor Real Estate. Does qubes-os have the concept of workspaces?
If you run KDE in dom0, you can use its window rules to bind particular
VMs to particular desktops (what you call workspaces). This is easy
since each window title begins with its VM name.
You can also resort to using HVMs instead of the usual template-based
PVH VMs. This is like installing a VM in VMWare, and you lose some of
the benefits of Qubes integration (IIRC its also theoretically less
secure). But it will give you a full, separate desktop for each HVM.
Note that Qubes currently does not have advanced BIOS support for HVMs,
so you may have trouble installing certain operating systems (although
there are many that work fine, such as Windows and Ubuntu).
There may be a third option in the form of using a regular
template-based appVM with full-screen mode enabled, in addition to
running its full desktop environment. The full-screen part is simple,
but I have no experience attempting the desktop environment and I don't
recall other users configuring their appVMs in this way. Perhaps someone
else can chime in about this possibility.
--
Chris Laprise, tas...@posteo.net
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/58097573-bb82-d677-0ba6-e2f31a3585f6%40posteo.net.
For more options, visit https://groups.google.com/d/optout.
