- Spectrum Development - spectrum-os.org

This Week in Spectrum, 2021-W10
by Alyssa Ross 14 Mar '21

14 Mar '21

Surprise! I sent the last This Week in Spectrum in August. Since then, it's been pretty quiet. What happened? Towards then end of last year, I was aggressively pushing to achieve a funding milestone, but was starting to struggle to keep myself going. After that last TWiS, I decided to stop posting them for a while to fully concentrate on the push. I continued like that for two more months, before getting to the point where I was so burned out I just couldn't keep going, with the milestone still not done, the work I had done so far on it unpublished (and not in a good state to be published), and time running out. Fortunately, I was able to talk to NLnet, and they agreed to extend my funding deadlines and renegotiate the milestones. With that sorted out, in late November I began a hiatus from Spectrum to allow myself to recover from the burnout. I'm very grateful to my GitHub Sponsors, thanks to whom I was able to take this time to recover. I tried to come back at the end of January, but after a single day of Spectrum work I was feeling much the same as I had been in November. This week, though, something changed! I've been working on Spectrum again for the last week, and I've been feeling great about it! Now, there were three months of work between the last TWiS in August, and the start of my hiatus. That's a lot of work I haven't written about. But I think the only way this is really going to work is if I leave that largely unwritten about for now, because TWiS tends to be thousands of words long even when it's covering a single week of work. So I'm just going to talk about what I've done in the last week, explaining context from previous work as necessary. With all that in mind, here we go! "Qubes-lite with KVM and Wayland"[1] ------------------------------------ First up is something somebody else did, which is always nice! Thomas has been doing his own great work replacing his Qubes system with a system built on NixOS, using KVM and Wayland. Thomas got in touch on the Spectrum discuss mailing list in January[2] asking some questions about how some things were implemented, and we went back and forth a bit then (although not as much as I'd have liked, due to my burnout :/). Since then, he's come up with some awesome stuff, like an OCaml implementation of a virtio-wayland proxy (equivalent to Sommelier in Chromium OS). In our further conversation prompted by Thomas's article, Thomas raised a further interesting idea[3] -- what if we had a Sommelier-like Wayland proxy, but that ran in the same security domain as the compositor. That way, we could filter to allow only the protocol extensions we want to. We could implement our own permissions when the compositor doesn't. This code would be responsible for securely handling Wayland messages from an untrusted guest, which would be beneficial because it would be a lot less code to audit, and because it could be written in a memory-safe language. This would avoid the need to write or find a secure Wayland compositor, and would in fact allow us to use virtually any compositor without having to worry nearly as much about its security credentials. I'm very excited by that idea, and I've been asking myself for the past few days why I didn't think of it before! I've thought several times "it's quite nice that Sommelier gives us a known subset of Wayland, but it's a shame we can't rely on it since it runs inside a application guest". But for some reason it just never occurred to me to follow that idea one step further, to "what if we had a similar program that run in the compositor's security domain". [1]: https://roscidus.com/blog/blog/2021/03/07/qubes-lite-with-kvm-and-wayland/ [2]: https://spectrum-os.org/lists/archives/spectrum-discuss/CAG4opy_hz_ESEpY0Tq… [3]: https://spectrum-os.org/lists/archives/spectrum-discuss/CAG4opy_JztAH3tD+ZU… uscpi-vsock ----------- ucspi-vsock[4] is a program I started writing in September. VSOCK[5] is a special Linux socket type that allows for communication between VMs, and I'm using it to allow services running in VMs (a USBIP daemon, for example), to notify the host (and by extension other VMs), when the service in the VM becomes ready to accept connections. USCPI[6] is a standard command interface for making it easy to do socket communication using standard IO primitives, without having to teach programs how to do socket connections for every kind of socket. There are several UCSPI implementations for common socket types like Internet and Unix domain sockets, but until now there was not one for VSOCK. So, for example, in a VM we can do: vsockclient 2 $port sh -c 'echo >&7' Which will connect to the host over VSOCK (in VSOCK the host is always address 2), write a newline, and close the connection. UCSPI lets us implement this with standard shell tools. There's an equivalent "vsockserver" program for the other end, that will run a command whenever a connection is received. Anyway, this week I went back to ucspi-vsock to fix some bugs[7][8][9][10]. As usual, (although I'm happy to realise this is still the case after all these months!) Cole was kind enough to review my patches. [4]: https://spectrum-os.org/git/ucspi-vsock/ [5]: https://man7.org/linux/man-pages/man7/vsock.7.html [6]: https://cr.yp.to/proto/ucspi.txt [7]: https://spectrum-os.org/lists/archives/spectrum-devel/20210309154048.14474-… [8]: https://spectrum-os.org/lists/archives/spectrum-devel/20210309171816.8589-1… [9]: https://spectrum-os.org/lists/archives/spectrum-devel/20210310204516.20041-… [10]: https://spectrum-os.org/lists/archives/spectrum-devel/20210310204555.20725-… Interguest networking --------------------- The bulk of my work this week has been in Spectrum's Nixpkgs, which is where (for now, at least) all the VM definitions and stuff live. Mostly, I've been trying to clean up months of frantic work into something I can actually publish as a series of patches, so it's out there instead of just on my computer! My focus at the moment is on doing this with the interguest networking implementation I wrote last year. The plan for this remains the same as last year: have a VM that manages all network hardware access and acts as a router for other VMs that need to talk to the outside world. Eventually, this will hopefully use virtio-vhost-user[11], which will allow us to avoid going through a networking stack on the host at all (or even having one), but until virtio-vhost-user is further along, we'll use bridge devices on the host to connect client VMs to the router. A very basic version of the latter is implemented and working for me locally -- I can run an application VM, and have it connect to another VM which runs the drivers for my ethernet port using VFIO (PCI passthrough). This code was a big ball of mud, and I'd also subtly broken it when I moved on from interguest networking last year to try to get a proof of concept going for another form of interguest communication. So I spent this week trying to page all the context I'd lost in the last few months back into my brain, making lots of partial git commits, writing commit messages, and fixing it up so that it works again. I think what I have is about ready to publish -- hopefully you'll see some patches next week. But what exists at the moment is still very limited -- the biggest limitation is that the router VM doesn't support hotplugging, so a VM that wants to connect to it actually has to be started first, before the router VM. Not good for something that should be run as a system service and likely started on boot! To overcome this limitation, I'll probably have to add support in crosvm for adding network devices at runtime using the control socket. I think this should be easy enough, and I haven't looked at what's happened in crosvm + rust-vmm since I've been away, so it's even possible somebody else will have done this already. [11]: https://wiki.qemu.org/Features/VirtioVhostUser So, the todo list for next week is getting the initial interguest networking PoC patchset posted. That'll come with a nice little demo other people will be able to try out if they want to. And then, I'll work on improving it further to the point where it's actually practical. I don't want to spend /too/ much time on this, since ultimately I do want to be using a virtio-vhost-user stack, which is quite different, but it's important to have an implementation of this so there's something to test further development (that doesn't care about the implementation details) against. My biggest worry at the moment is burning out again. Working in moderation isn't easy for me (I tend to get very sucked into things), but it's important for the project that I find a way to keep my work sustainable, so we don't lose time like this again. I'm still a little hesitant to say "this is it, I'm back for real". But the signs are looking good. Thank you for sticking with me through this.

1 0

[PATCH ucspi-vsock] vsockserver: use fclose instead of close
by Alyssa Ross 10 Mar '21

10 Mar '21

stdio can buffer output, so if we close stdout without going through stdio, there might be buffered output that is never written. --- vsockserver.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/vsockserver.c b/vsockserver.c index dd9a74a..196056a 100644 --- a/vsockserver.c +++ b/vsockserver.c @@ -90,7 +90,7 @@ int main(int argc, char *argv[]) if (notify) { printf("%" PRIu32 "\n", lport); - close(STDOUT_FILENO); + fclose(stdout); } setenvf("VSOCKLOCALCID", 1, "%" PRIu32, lcid); -- 2.30.0

2 2

[PATCH ucspi-vsock] Makefile: link object files instead of source files
by Alyssa Ross 10 Mar '21

10 Mar '21

Previously this would (I assume) needlessly recompile vsockserver.c and vsockclient.c when Make has already automatically compiled those. GNU Make has an automatic variable, $+, that we could use here, but currently the Makefile is portable, and it would be a shame to require GNU Make just for that. --- Makefile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Makefile b/Makefile index b931c89..4f11b64 100644 --- a/Makefile +++ b/Makefile @@ -19,9 +19,9 @@ install: vsockclient vsockserver .PHONY: install vsockclient: vsockclient.o env.o log.o util.o vsock.o - $(CC) $(LDFLAGS) -o vsockclient vsockclient.c env.o log.o util.o vsock.o $(LDLIBS) + $(CC) $(LDFLAGS) -o vsockclient vsockclient.o env.o log.o util.o vsock.o $(LDLIBS) vsockserver: vsockserver.o env.o log.o util.o vsock.o - $(CC) $(LDFLAGS) -o vsockserver vsockserver.c env.o log.o util.o vsock.o $(LDLIBS) + $(CC) $(LDFLAGS) -o vsockserver vsockserver.o env.o log.o util.o vsock.o $(LDLIBS) vsockclient.o: env.h log.h util.h vsock.h vsockserver.o: env.h log.h util.h vsock.h -- 2.30.0

2 1

[PATCH ucspi-vsock] vsock_accept: return fd instead of 0 on success
by Alyssa Ross 10 Mar '21

10 Mar '21

This would result in the spawned process being hooked up to stdin, instead of the vsock. Then stdin would be closed, so subsequent processes would be connected to nothing. Oops. --- I am... a bit embarassed that I didn't notice this after already fixing the exact same problem in vsock_connect[1]. Maybe I can write an integration test that runs vsockserver and vsockclient and checks they actually do the right thing... [1]: https://spectrum-os.org/lists/archives/spectrum-devel/20210309171816.8589-1… vsock.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/vsock.c b/vsock.c index d9ff3b6..e6a173c 100644 --- a/vsock.c +++ b/vsock.c @@ -32,14 +32,15 @@ int vsock_accept(int sockfd, uint32_t *cid, uint32_t *port) { struct sockaddr_vm addr = { 0 }; socklen_t addr_size = sizeof addr; + int fd; - if (accept(sockfd, (struct sockaddr *)&addr, &addr_size) == -1) + if ((fd = accept(sockfd, (struct sockaddr *)&addr, &addr_size)) == -1) return -1; *cid = addr.svm_cid; *port = addr.svm_port; - return 0; + return fd; } int vsock_connect(int fd, uint32_t cid, uint32_t port) -- 2.30.0

2 1

[PATCH ucspi-vsock] vsock_open: return fd instead of 0 on success
by Alyssa Ross 10 Mar '21

10 Mar '21

Previously, this returned the return value of connect(2), which is 0 on success. So stdin would be assigned to descriptors 6 and 7 in vsockclient instead of the socket. Oops. --- vsock.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/vsock.c b/vsock.c index 3bcd8b3..d9ff3b6 100644 --- a/vsock.c +++ b/vsock.c @@ -55,7 +55,10 @@ int vsock_open(uint32_t cid, uint32_t port) if (fd == -1) return -1; - return vsock_connect(fd, cid, port); + if (vsock_connect(fd, cid, port) == -1) + return -1; + + return fd; } int vsock_get_port(int fd, uint32_t *port) -- 2.30.0

2 1

[PATCH www] index.html: add alt text to logo
by Alyssa Ross 19 Dec '20

19 Dec '20

The empty alt text would make the image basically invisible if the user agent didn't display the image for whatever reason. This would have been fine if the image was entirely decorative, but since it's also the only way to navigate to the logo page it's important it has some fallback content so there's still something to select. --- index.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/index.html b/index.html index 10dcdeb..4345121 100644 --- a/index.html +++ b/index.html @@ -17,8 +17,8 @@ <body> <a href="logo" style="float: left; margin: 0 1em 0.5em 0"> - <img class="logo" src="logo/logo_html.svg" width="70" height="70" alt=""> - <img class="no-logo" srcset="logo/logo140.png 140w" src="logo/logo70.png" width="70" height="70" alt="" hidden loading="lazy"> + <img class="logo" src="logo/logo_html.svg" width="70" height="70" alt="Spectrum logo"> + <img class="no-logo" srcset="logo/logo140.png 140w" src="logo/logo70.png" width="70" height="70" alt="Spectrum logo" hidden loading="lazy"> </a> <h1>Spectrum — a step towards <em>usable</em> secure computing</h1> -- 2.27.0

1 0

[PATCH www] design.html: backpedal a bit on POWER9
by Alyssa Ross 29 Nov '20

29 Nov '20

Supporting POWER9 isn't going to be as easy as I'd initially hoped. This patch aims to explain that there are blockers that I'd need help overcoming to be able to support it, even though I'd still like to. I don't want to be promising anything I can't deliver on, and I now know that it's very unlikely I'll be able to deliver on this without help. Reported-by: Molly Miller <mm(a)m-squa.red> --- design.html | 32 ++++++++++++++++++++------------ 1 file changed, 20 insertions(+), 12 deletions(-) diff --git a/design.html b/design.html index 181c15c..f683ed4 100644 --- a/design.html +++ b/design.html @@ -127,18 +127,26 @@ Management Engine</a> / <a href="https://en.wikipedia.org/wiki/AMD_Platform_Security_Processor">AMD Platform Security Processor</a>. -<p>So, Spectrum will additionally have -first class support for at least ppc64le. This architecture has been -chosen because it is the only other architecture that can come close -to the sheer performance x86_64 can offer at the high end, and -because, in stark contrast to x86_64, it is possible to buy a new -ppc64le (POWER9) system that does not require any proprietary firmware -that cannot be inspected and audited. It is a goal of the project to -build all packages, x86_64 and ppc64le, on POWER9 hardware. Even if a -user has to trust the x86_64 computer available to them, anti-freedom -firmware, undocumented backdoors and all, it would be a disservice to -them to force them to use packages built on other such untrustworthy -hardware. +<p> +I would like Spectrum to additionally have first class support for at +least ppc64le. This is the only other architecture that can come +close to the sheer performance x86_64 can offer at the high end, and +in stark contrast to x86_64, it is possible to buy a new ppc64le +(POWER9) system that does not require any proprietary firmware that +cannot be inspected and audited. A blocker for POWER9 support is an +support in crosvm for virtualizing that architecture, which is outside +the expertise of anybody currently working on Spectrum but would be a +very welcome contribution. + +<p> +Ideally, all Spectrum packages, x86_64 and ppc64le, would be built on +POWER9 hardware. Even if a user has to trust the x86_64 computer +available to them, anti-freedom firmware, undocumented backdoors and +all, they would be able to benefit from binary packages that were +built on trustworthy hardware without these limitations. +Unfortunately, preliminary research has shown that x86_64 +virtualization on POWER9 is not currently sufficiantly performant for +this to be feasible. <p> <small>Permission is granted to copy, distribute and/or modify this -- 2.27.0

2 6

[PATCH www 1/2] Add Spectrum logo!
by Alyssa Ross 22 Nov '20

22 Nov '20

This lovely logo was designed for us by hazelnot. The browser-compatible SVG is incompatible with Firefox, except for the version (83.0) that just came out a couple of days ago, because it uses CSS conic gradients. So for a little while we'll need an annoying PNG fallback. --- I haven't included the PNG files in this patch, since they take up a lot of space (compared to text!) and can easily be generated from the SVG like this if you want to test the fallback: inkscape -w 70 -h 70 -e logo/logo70.png logo/logo_mesh.svg inkscape -w 140 -h 140 -e logo/logo140.png logo/logo_mesh.svg inkscape -w 200 -h 200 -e logo/logo200.png logo/logo_mesh.svg inkscape -w 400 -h 400 -e logo/logo400.png logo/logo_mesh.svg index.html | 5 ++++ logo/index.html | 60 +++++++++++++++++++++++++++++++++++++++ logo/logo140.png | Bin 0 -> 21544 bytes logo/logo140.png.license | 4 +++ logo/logo200.png | Bin 0 -> 36741 bytes logo/logo200.png.license | 4 +++ logo/logo400.png | Bin 0 -> 98542 bytes logo/logo400.png.license | 4 +++ logo/logo70.png | Bin 0 -> 7285 bytes logo/logo70.png.license | 4 +++ logo/logo_html.svg | 33 +++++++++++++++++++++ logo/logo_mesh.svg | 59 ++++++++++++++++++++++++++++++++++++++ style.css | 13 +++++++++ 13 files changed, 186 insertions(+) create mode 100644 logo/index.html create mode 100644 logo/logo140.png create mode 100644 logo/logo140.png.license create mode 100644 logo/logo200.png create mode 100644 logo/logo200.png.license create mode 100644 logo/logo400.png create mode 100644 logo/logo400.png.license create mode 100644 logo/logo70.png create mode 100644 logo/logo70.png.license create mode 100644 logo/logo_html.svg create mode 100644 logo/logo_mesh.svg diff --git a/index.html b/index.html index cbea331..1a3f18e 100644 --- a/index.html +++ b/index.html @@ -15,6 +15,11 @@ <body> +<a href="logo" style="float: left; margin: 0 1em 0.5em 0"> + <img class="logo" src="logo/logo_html.svg" width="70" height="70" alt=""> + <img class="no-logo" srcset="logo/logo140.png 140w" src="logo/logo70.png" width="70" height="70" alt="" hidden loading="lazy"> +</a> + <h1>Spectrum — a step towards <em>usable</em> secure computing</h1> <p> diff --git a/logo/index.html b/logo/index.html new file mode 100644 index 0000000..93727b7 --- /dev/null +++ b/logo/index.html @@ -0,0 +1,60 @@ +<!doctype html> + + + +<html lang="en"> + +<head> + +<meta charset="utf-8"> +<meta name="viewport" content="width=device-width,initial-scale=1"> + +<link rel="stylesheet" href="../style.css"> + +<title>Spectrum logo</title> + +<body> + +<nav> + <a href="..">Spectrum</a> +</nav> + +<h1>Logo</h1> + +<p> +<img class="logo" src="logo_html.svg" width="200" height="200" alt="" style="margin: 0 auto"> +<img class="no-logo" srcset="logo400.png 400w" src="logo200.png" alt="" width="200" height="200" style="margin: 0 auto" loading="lazy" hidden> + +<p> +The Spectrum logo was designed by hazelnot, and is released under +the <a href="https://creativecommons.org/publicdomain/zero/1.0/">Creative +Commons Zero</a> license. + +<p> +Two versions of the logo are available. The first is an SVG file +suitable for web browsers, and the second is an SVG file suitable for +<a href="https://inkscape.org/">Inkscape</a>. The difference between +the versions is in how the colored ring is implemented, since standard +SVG has no way of drawing conic gradients. The browser version uses +an embedded HTML element with a CSS conic gradient, and the Inkscape +version uses the +not-yet-standard <a href="https://wiki.inkscape.org/wiki/index.php/Mesh_Gradients">SVG +Mesh Gradients</a>. + +<ul> + + <li><a href="logo_html.svg" download>logo_html.svg</a> (for web browsers) + <li><a href="logo_mesh.svg" download>logo_mesh.svg</a> (for Inkscape) + +</ul> + +<p> +<small>Permission is granted to copy, distribute and/or modify this +document under either the terms of the +<a href="https://creativecommons.org/licenses/by-sa/4.0/">Creative +Commons Attribution-ShareAlike 4.0 International License</a>, or the +<a href="https://www.gnu.org/licenses/fdl-1.3.html">GNU Free +Documentation License, Version 1.3</a> or any later version published +by the Free Software Foundation; with no Invariant Sections, no +Front-Cover Texts, and no Back-Cover Texts.</small> + diff --git a/logo/logo140.png b/logo/logo140.png new file mode 100644 index 0000000..5978eb9 Binary files /dev/null and b/logo/logo140.png differ diff --git a/logo/logo140.png.license b/logo/logo140.png.license new file mode 100644 index 0000000..817f6ad --- /dev/null +++ b/logo/logo140.png.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2020 hazelnot +SPDX-FileCopyrightText: 2020 Alyssa Ross <hi(a)alyssa.is> + +SPDX-License-Identifier: CC0-1.0 diff --git a/logo/logo200.png b/logo/logo200.png new file mode 100644 index 0000000..0cd4f1e Binary files /dev/null and b/logo/logo200.png differ diff --git a/logo/logo200.png.license b/logo/logo200.png.license new file mode 100644 index 0000000..817f6ad --- /dev/null +++ b/logo/logo200.png.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2020 hazelnot +SPDX-FileCopyrightText: 2020 Alyssa Ross <hi(a)alyssa.is> + +SPDX-License-Identifier: CC0-1.0 diff --git a/logo/logo400.png b/logo/logo400.png new file mode 100644 index 0000000..2cf9ecc Binary files /dev/null and b/logo/logo400.png differ diff --git a/logo/logo400.png.license b/logo/logo400.png.license new file mode 100644 index 0000000..817f6ad --- /dev/null +++ b/logo/logo400.png.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2020 hazelnot +SPDX-FileCopyrightText: 2020 Alyssa Ross <hi(a)alyssa.is> + +SPDX-License-Identifier: CC0-1.0 diff --git a/logo/logo70.png b/logo/logo70.png new file mode 100644 index 0000000..664aba4 Binary files /dev/null and b/logo/logo70.png differ diff --git a/logo/logo70.png.license b/logo/logo70.png.license new file mode 100644 index 0000000..817f6ad --- /dev/null +++ b/logo/logo70.png.license @@ -0,0 +1,4 @@ +SPDX-FileCopyrightText: 2020 hazelnot +SPDX-FileCopyrightText: 2020 Alyssa Ross <hi(a)alyssa.is> + +SPDX-License-Identifier: CC0-1.0 diff --git a/logo/logo_html.svg b/logo/logo_html.svg new file mode 100644 index 0000000..199c3ca --- /dev/null +++ b/logo/logo_html.svg @@ -0,0 +1,33 @@ + + + + +<svg xmlns="http://www.w3.org/2000/svg" version="1.1" viewBox="0 0 100 100"> + <defs> + <filter id="ring-shadow" x="-10" y="-10" width="120" height="120" color-interpolation-filters="sRGB"> + <feGaussianBlur in="SourceGraphic" stdDeviation="5" result="blur" /> + <feComposite in="SourceGraphic" in2="offset" operator="over" /> + </filter> + + <filter id="center-shadow" x="-10" y="-10" width="120" height="120"> + <feDropShadow dx="0" dy="0" stdDeviation="6" flood-color="#DDD" /> + </filter> + + <mask id="ring-mask"> + <circle stroke="white" stroke-width="5" cx="50" cy="50" r="36" fill="none" /> + </mask> + </defs> + +  + <g filter="url(#ring-shadow)"> + <foreignObject width="100" height="100" mask="url(#ring-mask)"> + <div xmlns="http://www.w3.org/1999/xhtml" style="width: 100%; height: 100%; background: conic-gradient(from 0.25turn, red, magenta, blue, aqua, lime, yellow, red)" /> + </foreignObject> + </g> + + <circle cx="50" cy="50" r="27" fill="white" filter="url(#center-shadow)" /> +</svg> diff --git a/logo/logo_mesh.svg b/logo/logo_mesh.svg new file mode 100644 index 0000000..ccd6583 --- /dev/null +++ b/logo/logo_mesh.svg @@ -0,0 +1,59 @@ + + + + +<svg xmlns="http://www.w3.org/2000/svg" version="1.1" viewBox="0 0 100 100"> + <defs> + <filter id="ring-shadow" x="-10" y="-10" width="120" height="120" color-interpolation-filters="sRGB"> + <feGaussianBlur in="SourceGraphic" stdDeviation="5" result="blur" /> + <feComposite in="SourceGraphic" in2="offset" operator="over" /> + </filter> + + <filter id="center-shadow" x="-10" y="-10" width="120" height="120" color-interpolation-filters="sRGB"> + <feFlood flood-opacity="1" flood-color="#DDD" result="flood" /> + <feComposite in="flood" in2="SourceGraphic" operator="in" result="composite1" /> + <feGaussianBlur in="composite1" stdDeviation="6" result="blur" /> + <feComposite in="SourceGraphic" in2="blur" operator="over" result="composite2" /> + </filter> + + <meshgradient id="ring-gradient" x="1.5" y="0.5"> + <meshrow> + <meshpatch> + <stop path="L 1 -0.36603" stop-color="red" /> + <stop path="L 0.5 0.5" stop-color="yellow" /> + <stop path="L 0.5 0.5" stop-color="yellow" /> + <stop path="L 1 0.5" stop-color="red" /> + </meshpatch> + <meshpatch> + <stop path="L 0 -0.36603" /> + <stop path="L 0.5 0.5" stop-color="lime" /> + <stop path="L 0.5 0.5" stop-color="lime" /> + </meshpatch> + <meshpatch> + <stop path="L -0.5 0.5" /> + <stop path="L 0.5 0.5" stop-color="cyan" /> + <stop path="L 0.5 0.5" stop-color="cyan" /> + </meshpatch> + <meshpatch> + <stop path="L 0 1.36603" /> + <stop path="L 0.5 0.5" stop-color="blue" /> + <stop path="L 0.5 0.5" stop-color="blue" /> + </meshpatch> + <meshpatch> + <stop path="L 1 1.36603" /> + <stop path="L 0.5 0.5" stop-color="magenta" /> + <stop path="L 0.5 0.5" stop-color="magenta" /> + </meshpatch> + <meshpatch> + <stop path="L 1.5 0.5" /> + <stop path="L 0.5 0.5" stop-color="red" /> + <stop path="L 0.5 0.5" stop-color="red" /> + </meshpatch> + </meshrow> + </meshgradient> + </defs> + + <circle cx="50" cy="50" r="36" fill="none" stroke="url(#ring-gradient)" stroke-width="5" filter="url(#ring-shadow)" /> + + <circle cx="50" cy="50" r="27" fill="white" filter="url(#center-shadow)" /> +</svg> diff --git a/style.css b/style.css index e9fd751..6463f24 100644 --- a/style.css +++ b/style.css @@ -20,3 +20,16 @@ h1, h2, h3, h4 { var { font-family: serif; } + +/* +Firefox only supports conic gradients as of 83.0, so for the time +being, we need to provide a fallback for the logo. +*/ + +.logo { display: none; } +.no-logo { display: block; } + +@supports (background: conic-gradient(from 0.25turn, red, magenta, blue, aqua, lime, yellow, red)) { + .logo { display: block; } + .no-logo { display: none; } +} -- 2.27.0

2 4

[DRAFT PATCH nixpkgs] smaller kernel
by Philipp Steinpaß 26 Aug '20

26 Aug '20

minimize spectrum-vm kernel --- pkgs/os-specific/linux/spectrum/linux/vm.nix | 449 +++++++++++++++++++ 1 file changed, 449 insertions(+) diff --git a/pkgs/os-specific/linux/spectrum/linux/vm.nix b/pkgs/os-specific/linux/spectrum/linux/vm.nix index 9c9ba78b691..c313697eeb2 100644 --- a/pkgs/os-specific/linux/spectrum/linux/vm.nix +++ b/pkgs/os-specific/linux/spectrum/linux/vm.nix @@ -4,6 +4,7 @@ with lib.kernel; linux.override { structuredExtraConfig = { + VIRTIO_CONSOLE = yes; VIRTIO_PCI = yes; VIRTIO_BLK = yes; VIRTIO_WL = yes; @@ -21,5 +22,453 @@ linux.override { NET_9P = yes; NET_9P_VIRTIO = yes; "9P_FS" = yes; + + ACPI = no; + AD525X_DPOT = no; + ADIN_PHY = no; + AF_KCM = no; + ALTERA_STAPL = no; + ALTERA_TSE = no; + AMD_PHY = no; + APDS9802ALS = no; + AQUANTIA_PHY = no; + AT803X_PHY = no; + ATA = no; + ATA_OVER_ETH = no; + ATM_DRIVERS = no; + AX88796B_PHY = no; + B53 = no; + BCM87XX_PHY = no; + BCMA = no; + BCM_KONA_USB2_PHY = no; + BLK_DEV_DRBD = no; + BLK_DEV_FD = no; + BLK_DEV_LOOP = no; + BLK_DEV_NULL_BLK = no; + BLK_DEV_RBD = no; + BROADCOM_PHY = no; + BT = no; + C2PORT = no; + CAIF = no; + CAN = no; + CDROM_PKTCDVD = no; + CHROME_PLATFORMS = no; + CICADA_PHY = no; + CMA = no; + COMEDI = no; + CORTINA_PHY = no; + COUNTER = no; + DAVICOM_PHY = no; + DEV_DAX = no; + DMADEVICES = no; + DNET = no; + DP83822_PHY = no; + DP83848_PHY = no; + DP83867_PHY = no; + DP83TC811_PHY = no; + DRM_ETNAVIV = no; + DRM_PANEL_ORIENTATION_QUIRKS = module; + DS1682 = no; + DUMMY_IRQ = no; + ECHO = no; + ENCLOSURE_SERVICES = no; + ETHOC = no; + EXT2_FS = no; + EXT4_USE_FOR_EXT2 = yes; + EXTCON = no; + FIELDBUS_DEV = no; + FPGA = no; + FW_LOADER_USER_HELPER = no; + GENERIC_PHY = no; + GNSS = no; + GREYBUS = no; + GS_FPGABOOT = no; + HAMRADIO = no; + HMC6352 = no; + HSI = no; + HVC_XEN = no; + HW_RANDOM_TIMERIOMEM = no; + HW_RANDOM_VIA = no; + I2C_ALGOPCF = no; + I2C_CHARDEV = no; + I2C_COMPAT = no; + I2C_HELPER_AUTO = no; + I2C_SLAVE_EEPROM = no; + I2C_STUB = no; + I3C = no; + I8K = no; + ICPLUS_PHY = no; + ICS932S401 = no; + IEEE802154_DRIVERS = no; + IIO = no; + INFINIBAND = no; + INPUT_JOYSTICK = no; + INPUT_KEYBOARD = no; + INPUT_MISC = no; + INPUT_MOUSE = no; + INPUT_TABLET = no; + INPUT_TOUCHSCREEN = no; + INTEL_TH = no; + INTEL_XWAY_PHY = no; + INTERCONNECT = no; + IOMMU_IOVA = module; + IOSF_MBI = module; + IPACK_BUS = no; + IPMB_DEVICE_INTERFACE = no; + IPMI_HANDLER = no; + ISL29003 = no; + ISL29020 = no; + LEDS_APU = no; + LEDS_BD2802 = no; + LEDS_BLINKM = no; + LEDS_CLASS_FLASH = no; + LEDS_CLEVO_MAIL = no; + LEDS_GPIO = no; + LEDS_LM3530 = no; + LEDS_LM3532 = no; + LEDS_LM3533 = no; + LEDS_LM355x = no; + LEDS_LM3642 = no; + LEDS_LP3944 = no; + LEDS_LP3952 = no; + LEDS_LP5521 = no; + LEDS_LP5523 = no; + LEDS_LP5562 = no; + LEDS_LP8501 = no; + LEDS_MC13783 = no; + LEDS_MENF21BMC = no; + LEDS_MLXCPLD = no; + LEDS_MLXREG = no; + LEDS_MT6323 = no; + LEDS_PCA9532 = no; + LEDS_PCA955X = no; + LEDS_PCA963X = no; + LEDS_REGULATOR = no; + LEDS_TCA6507 = no; + LEDS_TI_LMU_COMMON = no; + LEDS_TLC591XX = no; + LEDS_TRIGGER_ACTIVITY = no; + LEDS_TRIGGER_BACKLIGHT = no; + LEDS_TRIGGER_CAMERA = no; + LEDS_TRIGGER_DEFAULT_ON = no; + LEDS_TRIGGER_GPIO = no; + LEDS_TRIGGER_HEARTBEAT = no; + LEDS_TRIGGER_NETDEV = no; + LEDS_TRIGGER_ONESHOT = no; + LEDS_TRIGGER_PATTERN = no; + LEDS_TRIGGER_TIMER = no; + LEDS_TRIGGER_TRANSIENT = no; + LEDS_USER = no; + LSI_ET1011C_PHY = no; + LXT_PHY = no; + MACINTOSH_DRIVERS = no; + MAILBOX = no; + MARVELL_10G_PHY = no; + MARVELL_PHY = no; + MCB = no; + MDIO_BITBANG = no; + MDIO_MSCC_MIIM = no; + MEDIA_SUPPORT = no; + MEMSTICK = no; + MFD_CROS_EC = no; + MICREL_PHY = no; + MICROCHIP_PHY = no; + MICROCHIP_T1_PHY = no; + MICROSEMI_PHY = no; + MMC = no; + MOST = no; + MTD = no; + MWAVE = no; + NATIONAL_PHY = no; + NET_DSA_BCM_SF2 = no; + NET_DSA_LANTIQ_GSWIP = no; + NET_DSA_LOOP = no; + NET_DSA_MICROCHIP_KSZ8795 = no; + NET_DSA_MICROCHIP_KSZ9477 = no; + NET_DSA_MT7530 = no; + NET_DSA_MV88E6060 = no; + NET_DSA_MV88E6XXX = no; + NET_DSA_QCA8K = no; + NET_DSA_REALTEK_SMI = no; + NET_DSA_SMSC_LAN9303_I2C = no; + NET_DSA_SMSC_LAN9303_MDIO = no; + NET_VENDOR_ALACRITECH = no; + NET_VENDOR_AMAZON = no; + NET_VENDOR_AQUANTIA = no; + NET_VENDOR_ARC = no; + NET_VENDOR_AURORA = no; + NET_VENDOR_CADENCE = no; + NET_VENDOR_CAVIUM = no; + NET_VENDOR_CORTINA = no; + NET_VENDOR_EZCHIP = no; + NET_VENDOR_GOOGLE = no; + NET_VENDOR_HUAWEI = no; + NET_VENDOR_INTEL = no; + NET_VENDOR_MARVELL = no; + NET_VENDOR_MELLANOX = no; + NET_VENDOR_MICREL = no; + NET_VENDOR_MICROCHIP = no; + NET_VENDOR_MICROSEMI = no; + NET_VENDOR_NATSEMI = no; + NET_VENDOR_NETRONOME = no; + NET_VENDOR_NI = no; + NET_VENDOR_PENSANDO = no; + NET_VENDOR_QUALCOMM = no; + NET_VENDOR_RENESAS = no; + NET_VENDOR_ROCKER = no; + NET_VENDOR_SAMSUNG = no; + NET_VENDOR_SEEQ = no; + NET_VENDOR_SOCIONEXT = no; + NET_VENDOR_SOLARFLARE = no; + NET_VENDOR_STMICRO = no; + NET_VENDOR_SYNOPSYS = no; + NET_VENDOR_VIA = no; + NET_VENDOR_WIZNET = no; + NET_VENDOR_XILINX = no; + NFC = no; + NULL_TTY = no; + NVME_FC = no; + NVME_TARGET = no; + N_GSM = no; + PARPORT = no; + PCCARD = no; + PHY_PXA_28NM_HSIC = no; + PHY_PXA_28NM_USB2 = no; + PMBUS = no; + PM_DEBUG = no; + QSEMI_PHY = no; + RAVE_SP_EEPROM = no; + RC_CORE = no; + RD_BZIP2 = no; + RD_LZ4 = no; + RD_LZMA = no; + RD_LZO = no; + RD_XZ = no; + RENESAS_PHY = no; + RESET_CONTROLLER = no; + RFKILL = no; + RMI4_I2C = no; + RMI4_SMB = no; + ROCKCHIP_PHY = no; + RTC_DRV_88PM80X = no; + RTC_DRV_ABB5ZES3 = no; + RTC_DRV_ABEOZ9 = no; + RTC_DRV_ABX80X = no; + RTC_DRV_BQ32K = no; + RTC_DRV_BQ4802 = no; + RTC_DRV_CMOS = no; + RTC_DRV_DA9063 = no; + RTC_DRV_DS1286 = no; + RTC_DRV_DS1307 = no; + RTC_DRV_DS1374 = no; + RTC_DRV_DS1511 = no; + RTC_DRV_DS1553 = no; + RTC_DRV_DS1672 = no; + RTC_DRV_DS1685_FAMILY = no; + RTC_DRV_DS1742 = no; + RTC_DRV_DS2404 = no; + RTC_DRV_DS3232 = no; + RTC_DRV_EM3027 = no; + RTC_DRV_FM3130 = no; + RTC_DRV_FTRTC010 = no; + RTC_DRV_ISL12022 = no; + RTC_DRV_ISL1208 = no; + RTC_DRV_M41T80 = no; + RTC_DRV_M48T35 = no; + RTC_DRV_M48T59 = no; + RTC_DRV_M48T86 = no; + RTC_DRV_MAX6900 = no; + RTC_DRV_MAX8907 = no; + RTC_DRV_MC13XXX = no; + RTC_DRV_MSM6242 = no; + RTC_DRV_MT6397 = no; + RTC_DRV_PCF2127 = no; + RTC_DRV_PCF50633 = no; + RTC_DRV_PCF85063 = no; + RTC_DRV_PCF8523 = no; + RTC_DRV_PCF85363 = no; + RTC_DRV_PCF8563 = no; + RTC_DRV_PCF8583 = no; + RTC_DRV_RP5C01 = no; + RTC_DRV_RS5C372 = no; + RTC_DRV_RV3028 = no; + RTC_DRV_RV3029C2 = no; + RTC_DRV_RV8803 = no; + RTC_DRV_RX8010 = no; + RTC_DRV_RX8025 = no; + RTC_DRV_RX8581 = no; + RTC_DRV_S35390A = no; + RTC_DRV_SD3078 = no; + RTC_DRV_STK17TA8 = no; + RTC_DRV_V3020 = no; + RTC_DRV_X1205 = no; + SENSORS_ABITUGURU = no; + SENSORS_ABITUGURU3 = no; + SENSORS_AD7414 = no; + SENSORS_AD7418 = no; + SENSORS_ADC128D818 = no; + SENSORS_ADM1021 = no; + SENSORS_ADM1025 = no; + SENSORS_ADM1026 = no; + SENSORS_ADM1029 = no; + SENSORS_ADM1031 = no; + SENSORS_ADM9240 = no; + SENSORS_ADS7828 = no; + SENSORS_ADT7410 = no; + SENSORS_ADT7411 = no; + SENSORS_ADT7462 = no; + SENSORS_ADT7470 = no; + SENSORS_ADT7475 = no; + SENSORS_AMC6821 = no; + SENSORS_APDS990X = no; + SENSORS_APPLESMC = no; + SENSORS_AS370 = no; + SENSORS_ASB100 = no; + SENSORS_ASC7621 = no; + SENSORS_ASPEED = no; + SENSORS_ATXP1 = no; + SENSORS_BH1770 = no; + SENSORS_CORETEMP = no; + SENSORS_DME1737 = no; + SENSORS_DS1621 = no; + SENSORS_DS620 = no; + SENSORS_EMC1403 = no; + SENSORS_EMC2103 = no; + SENSORS_EMC6W201 = no; + SENSORS_F71805F = no; + SENSORS_F71882FG = no; + SENSORS_F75375S = no; + SENSORS_FSCHMD = no; + SENSORS_G760A = no; + SENSORS_G762 = no; + SENSORS_GL518SM = no; + SENSORS_GL520SM = no; + SENSORS_HIH6130 = no; + SENSORS_INA209 = no; + SENSORS_INA2XX = no; + SENSORS_INA3221 = no; + SENSORS_IT87 = no; + SENSORS_JC42 = no; + SENSORS_LINEAGE = no; + SENSORS_LIS3_I2C = no; + SENSORS_LIS3_SPI = module; + SENSORS_LM63 = no; + SENSORS_LM73 = no; + SENSORS_LM75 = no; + SENSORS_LM77 = no; + SENSORS_LM78 = no; + SENSORS_LM80 = no; + SENSORS_LM83 = no; + SENSORS_LM85 = no; + SENSORS_LM87 = no; + SENSORS_LM90 = no; + SENSORS_LM92 = no; + SENSORS_LM93 = no; + SENSORS_LM95234 = no; + SENSORS_LM95241 = no; + SENSORS_LM95245 = no; + SENSORS_LTC2945 = no; + SENSORS_LTC2990 = no; + SENSORS_LTC4151 = no; + SENSORS_LTC4215 = no; + SENSORS_LTC4222 = no; + SENSORS_LTC4245 = no; + SENSORS_LTC4260 = no; + SENSORS_LTC4261 = no; + SENSORS_MAX16065 = no; + SENSORS_MAX1619 = no; + SENSORS_MAX1668 = no; + SENSORS_MAX197 = no; + SENSORS_MAX31790 = no; + SENSORS_MAX6621 = no; + SENSORS_MAX6639 = no; + SENSORS_MAX6642 = no; + SENSORS_MAX6650 = no; + SENSORS_MAX6697 = no; + SENSORS_MC13783_ADC = no; + SENSORS_MCP3021 = no; + SENSORS_MENF21BMC_HWMON = no; + SENSORS_NCT6683 = no; + SENSORS_NCT6775 = no; + SENSORS_NCT7802 = no; + SENSORS_NCT7904 = no; + SENSORS_NPCM7XX = no; + SENSORS_NTC_THERMISTOR = no; + SENSORS_PC87360 = no; + SENSORS_PC87427 = no; + SENSORS_PCF8591 = no; + SENSORS_POWR1220 = no; + SENSORS_SHT15 = no; + SENSORS_SHT21 = no; + SENSORS_SHT3x = no; + SENSORS_SHTC1 = no; + SENSORS_SMM665 = no; + SENSORS_SMSC47B397 = no; + SENSORS_SMSC47M1 = no; + SENSORS_SMSC47M192 = no; + SENSORS_STTS751 = no; + SENSORS_TC654 = no; + SENSORS_TC74 = no; + SENSORS_THMC50 = no; + SENSORS_TMP102 = no; + SENSORS_TMP103 = no; + SENSORS_TMP108 = no; + SENSORS_TMP401 = no; + SENSORS_TMP421 = no; + SENSORS_TSL2550 = no; + SENSORS_VIA_CPUTEMP = no; + SENSORS_VT1211 = no; + SENSORS_W83627EHF = no; + SENSORS_W83627HF = no; + SENSORS_W83773G = no; + SENSORS_W83781D = no; + SENSORS_W83791D = no; + SENSORS_W83792D = no; + SENSORS_W83793 = no; + SENSORS_W83795 = no; + SENSORS_W83L785TS = no; + SENSORS_W83L786NG = no; + SERIAL_NONSTANDARD = no; + SFP = no; + SIOX = no; + SLIMBUS = no; + SLIP = no; + SND_HDA_INTEL_DETECT_DMIC = no; + SND_SOC = no; + SND_X86 = no; + SND_XEN_FRONTEND = no; + SPI_MEM = no; + SPMI = no; + STE10XP = no; + STM = no; + TARGET_CORE = no; + TCG_ATMEL = no; + TCG_NSC = no; + TCG_TIS_ST33ZP24_I2C = no; + TCG_VTPM_PROXY = no; + TCG_XEN = no; + TELCLOCK = no; + TERANETICS_PHY = no; + THERMAL = no; + THUNDERBOLT = no; + TRACE_SINK = no; + UIO_PRUSS = no; + USB_SUPPORT = no; + UWB = no; + VIRTUALIZATION = no; + VITESSE_PHY = no; + WATCHDOG = no; + WIMAX = no; + WIRELESS = no; + WLAN = no; + X86_EXTENDED_PLATFORM = no; + X86_INTEL_MEMORY_PROTECTION_KEYS = no; + X86_PLATFORM_DEVICES = no; + XEN_BACKEND = no; + XEN_BLKDEV_FRONTEND = no; + XEN_NETDEV_FRONTEND = no; + XEN_XENBUS_FRONTEND = module; + XILINX_GMII2RGMII = no; + XILINX_SDFEC = no; }; } -- So here is a first draft for a more minimal kernel. It brings down the kernel build time from around 40 minutes to around 10 minutes on my machine (while watching videos on the side, so ymmv). What I did was taking the kernel .config from a running spectrum vm and worked with menuconfig and diffconfig from the kernel source tree. I tried to remove as much support for physical devices as possible, on top of that I removed support for virtual hosting and virtual guest for everything that isn't kvm/virtio. I tested the kernel by booting it up succesfully and confirming that video acceleration still works. I'm not satisfied with the missing documentation right now, but I'm not sure how to practically improve on that, the sheer number of needed changes seems to make that pretty hard, so I'd be happy for any suggestions. Cheers, Philipp

1 0

This (and Last) Week in Spectrum, 2020-W34 & 2020-W35
by Alyssa Ross 26 Aug '20

26 Aug '20

Last week I wasn't feeling well, so there was no This Week in Spectrum. crosvm ------ Where we left off, I had been attempting to port vhost-user-net support from cloud-hypervisor to crosvm. I'd been trying to port the first incarnation of the code in cloud-hypervisor to the contemporary version of crosvm from when it was added, thinking that that would be easier because the two codebases together. But I ran into the problem that this earliest incarnation of the vhost-user-net code from cloud-hypervisor didn't actually work (at least with the backend I was attempting to test it with). I'd been attempting to figure out exactly which changes were required to make it work, but hadn't been successful with that yet, and I thought I'd probably need to start the port over, from the latest cloud-hypervisor and crosvm code. The next day, I decided to give my previous strategy one more try, though, and an hour or two later, I found the required cloud-hypervisor change, applied it to crosvm, and it worked! So I now have a crosvm tree capable of vhost-user-net[1]. This means that it's looking good for my plans for inter-guest networking, and network hardware isolation. With that in place, I decided to start thinking about other kinds of hardware isolation and inter-VM communication, and that's what I did for most of the last two weeks. Let's go through them: Files will be shared between VMs using virtio-fs. This has the unique feature of (soon) being able to bypass guest page caches, and have only a single shared cache between VMs. This brings a performance improvement, but as I understand it, should also reduce memory consumption because each VM won't have to maintain its own copy of a disk-backed page. Of course, this feature (DAX) is also a big side channel, so it won't be appropriate for all use cases. But I think for some things people want to do with Spectrum, this will be very important. The problem with this is that, because it uses the page cache of the host kernel, the host has to know about the filesystem that's being shared -- there's no running virtiofsd in a VM if we want DAX. But I'd really like it if a (non-boot) block device could be used as a filesystem without the host having to actually talk to the device. I was stuck here, but edef pointed out to me that we could use the kernel's 9P support to attach the block device to a VM, and then mounting the filesystem in the host over 9P, either over a network connection or (ideally) vsock. It looks like the kernel should be able to handle 9P over vsock, but I haven't tested yet. We can use existing virtiofsd and 9P software (there are promising Rust implementations of each), and harden them against potential vulnerabilites like directory traversals using kernel features like RESOLVE_BENEATH and RESOLVE_NO_XDEV. For the boot device, maybe there's no reason not to just mount it using the host kernel, or maybe there's something to be gained by just reading a small bootstrap payload into memory from the start of the disk once, and then making all future communication go via a VM. I'm not really sure yet. But the important thing is we'll have mechanisms for all this in place. Maybe we'll decide that non-boot devices should just go over inter-VM 9P, but in any case, we'll still need all these pieces. GPU isolation should be possible by forwarding the GPU to a VM, but there are a few problems here. The first is that it would mean rendered surfaces have to be copied via shared memory to the VM with the GPU, before being sent to the GPU. Additionally, sharing the GPU between VMs for rendering at all would require significantly more work. The result of this is that graphics performance using an isolated GPU will probably be poor, at least for now. The final problem is that passthrough of integrated GPUs seems to be very difficult to get right. I will probably need to acquire some hardware that I've sene a report of this working on, so I can figure out what I've been doing wrong on the two computers I've tried it on so far. I suspect that I will get GPU isolation working, but I'm not sure how reliable or performant it will be. For generic USB devices, I expect to be able to take an approach similar to Qubes[2], having a VM to handle interactions with the hardware USB controller, and exposing individual USB devices over USB/IP to other VMs. It would be nice if I could use vsock for this too. [1]: https://spectrum-os.org/git/crosvm/?h=vhost-user-net [2]: https://www.qubes-os.org/doc/usb-devices/ spectrum-os.org --------------- Philipp registered a Matrix room and bridged it to the #spectrum IRC channel. I'm told that this should make it easier for Matrix users to join the room, since some bug in Matrix's IRC bridge prevents people from joining from Matrix the usual way. Philipp also sent a patch[3] to improve the instructions for Matrix users joining the channel on the website. Thanks Philipp! [3]: https://spectrum-os.org/lists/archives/spectrum-devel/87wo247zu7.fsf@alyssa… QEMU ---- I sent the previously requested patch[4] to resolve ambiguities in the vhost-user spec. No response yet, though. I'll probably resend it some time soon. [4]: https://lore.kernel.org/qemu-devel/20200813094847.4288-1-hi@alyssa.is/ I'm finding it hard to keep going at the moment. The stuff I'm doing now is probably the hardest part of implementing Spectrum, and it's frustrating to realise that not everything I want to do is going to be possible. So much of the KVM ecosystem assumes that things will be host<->guest, and there's not always an easy solution. But, whatever we end up with, it's going to be a lot better than what I'm using today, and what lots of other people are using today. I think I'm going to be able to deliver a good experience with a fairly high degree of protection against malicious hardware. But it's not going to be perfect. I'm pushing quite hard to make it over the line with my hardware isolation funding milestone. I'm so close, and I'm about to need the money. But once I've hit that, I think I'm going to need a break. This stuff is gruelling.

2 1