From: Alyssa Ross <hi@alyssa.is>
To: Adam Joseph <adam@westernsemico.com>
Cc: devel@spectrum-os.org, Ville Ilvonen <ville.ilvonen@unikie.com>
Subject: Re: [PATCH] Documentation: Architecture Decision Record
Date: Fri, 6 Jan 2023 13:27:47 +0000 [thread overview]
Message-ID: <20230106132747.kad4pfyne5pgxopj@x220> (raw)
In-Reply-To: <167272942335.19302.1324067862019435223@localhost>
[-- Attachment #1: Type: text/plain, Size: 1863 bytes --]
On Mon, Jan 02, 2023 at 11:03:43PM -0800, Adam Joseph wrote:
> Quoting Ville Ilvonen (2022-07-08 04:02:15)
> > +++ b/Documentation/decisions/006-drivers-on-host.adoc
> > ...
> > +## Consequences
> > +No networking on the host. Responsibilities of the host are expected to get
> > +smaller over time.
>
> I know you're probably a long, long way from worrying about wifi, but when you
> get to that point, I suggest taking a look at running `eiwd` in the netvm:
>
> https://github.com/illiliti/eiwd/
> https://github.com/NixOS/nixpkgs/pull/208844
>
> - It is way more robust than wpa_supplicant.
> - (unlike iwd) it does not require plumbing a dbus connection from the hostvm to
> the netvm (nor all the attack surface that would entail).
> - You control it by simply editing its state files, which it watches with
> `inotify()`.
> - It has zero runtime dependencies!
> - `pkgsStatic.eiwd` builds (caveat: I have not tested it)
> - You should be able to boot a VM with `init=/nix/store/...-eiwd/bin/eiwd`
> and run it as PID 1 (note: I have not tried this).
>
> I've been running this on my daily driver laptop for the last few weeks and am
> extremely happy with it.
Thanks for the recommendation!
IMO, we're not too far away from worrying about Wi-Fi — it would just
involve setting up Wi-Fi modaliases to pass through to the appropriate
VM, and setting up the VM to do the right thing if any Wi-Fi devices
were connected to it.
For embedded use cases, where you could just bake the network
configuration in to a custom netvm, that'd be it. But for e.g. a
laptop, for Wi-Fi to be useful we'd really need a way to have persistent
storage for on-the-fly network configuration. That's the main reason I
haven't looked at Wi-Fi yet. It's a very pressing problem, though, so
hopefully won't be too long...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-01-06 13:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 11:02 [PATCH] Documentation: Architecture Decision Record Ville Ilvonen
2022-07-12 18:11 ` Alyssa Ross
2022-07-13 9:35 ` Ville Ilvonen
2022-07-13 9:53 ` Alyssa Ross
2022-07-13 11:04 ` Ville Ilvonen
2022-07-22 11:32 ` Alyssa Ross
2022-07-22 11:37 ` Alyssa Ross
2022-07-13 10:04 ` Alyssa Ross
2023-01-03 7:03 ` Adam Joseph
2023-01-06 13:27 ` Alyssa Ross [this message]
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=20230106132747.kad4pfyne5pgxopj@x220 \
--to=hi@alyssa.is \
--cc=adam@westernsemico.com \
--cc=devel@spectrum-os.org \
--cc=ville.ilvonen@unikie.com \
/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.
Code repositories for project(s) associated with this public inbox
https://spectrum-os.org/git/crosvm
https://spectrum-os.org/git/doc
https://spectrum-os.org/git/mktuntap
https://spectrum-os.org/git/nixpkgs
https://spectrum-os.org/git/spectrum
https://spectrum-os.org/git/ucspi-vsock
https://spectrum-os.org/git/www
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).