From: "Michał \"rysiek\" Woźniak" <rysiek@hackerspace.pl>
To: discuss@spectrum-os.org
Subject: Re: Comparison to Qubes OS
Date: Fri, 12 Jun 2020 12:02:38 +0000 [thread overview]
Message-ID: <6017c296-7bcf-3f11-8410-9380ad4ee2a6@hackerspace.pl> (raw)
In-Reply-To: <159196284966.15924.16876974660333010445@localhost>
[-- Attachment #1.1: Type: text/plain, Size: 1217 bytes --]
Hey,
On 6/12/20 11:54 AM, infokiller wrote:
> Michał "rysiek" Woźniak wrote:
>> Running virtual machines is extremely resource-intensive, there's no way around it.
>
> But if the issues stem from running VMs (and not switching from Xen), they won't be resolved with Spectrum's current design, right?
Right you are about the performance issues *I think*. I would however expect
hardware compatibility to improve with kvm.
But I'd love somebody more knowledgeable to shed some light here.
>> I feel one needs to be an expert to use QubesOS, but a regular user (with some
>> basic training) can use a Mint or Ubuntu-based system. And I think it makes a
>> lot of sense to offer a middle ground.
>
> Agreed, but I think the current design of Spectrum may improve Qubes' hardware issues, but not the other issues the doc mentions. Possibly switching to containers (which something like gVisor) may solve some of the other issues of Qubes, though that would further degrade security.
Fun fact, containers were in fact initially considered. :-)
Here's a good blogpost from Alyssa on why move to kvm, and the advantages of it
over Xen: https://alyssa.is/back-from-cccamp-2019/
--
Best
r
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 963 bytes --]
next prev parent reply other threads:[~2020-06-12 12:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 11:06 joweill
2020-06-12 11:28 ` Michał "rysiek" Woźniak
2020-06-12 11:54 ` infokiller
2020-06-12 12:02 ` Michał "rysiek" Woźniak [this message]
2020-06-13 11:19 ` Alyssa Ross
2020-06-13 11:38 ` Alyssa Ross
2020-06-14 20:19 ` infokiller
2020-06-14 21:27 ` Alyssa Ross
2020-06-14 22:19 ` Michał "rysiek" Woźniak
2020-06-15 1:59 ` infokiller
2020-06-15 1:54 ` infokiller
2020-06-14 21:13 ` Michael Raskin
2020-06-15 1:33 ` infokiller
2020-06-15 11:38 ` Michael Raskin
2020-06-15 13:44 ` infokiller
2020-06-15 14:06 ` Michał "rysiek" Woźniak
2020-06-15 15:07 ` infokiller
2020-06-15 14:42 ` Michael Raskin
2020-06-15 15:29 ` infokiller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6017c296-7bcf-3f11-8410-9380ad4ee2a6@hackerspace.pl \
--to=rysiek@hackerspace.pl \
--cc=discuss@spectrum-os.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).