general high-level discussion about spectrum
 help / color / mirror / Atom feed
From: Alyssa Ross <hi@alyssa.is>
To: discuss@spectrum-os.org
Cc: Demi Marie Obenour <demiobenour@gmail.com>, Yureka <yuka@yuka.dev>
Subject: This Week in Spectrum, 2025-W29
Date: Mon, 21 Jul 2025 09:41:50 +0200	[thread overview]
Message-ID: <87ikjmt2gx.fsf@alyssa.is> (raw)

[-- Attachment #1: Type: text/plain, Size: 2409 bytes --]

The main thing that's been happening this week is a lot of back and
forth between Demi and me on PipeWire in VMs.  The series is now in its
fifth iteration[1], and is shaping up well.  I'm happy that we're
discussing it on the list so much, because it will make it easy to refer
back to in future for context of why decisions were made.

For my part, I've been mostly trying to find solutions to problems Demi
has been encountering as she gets set up to work on Spectrum.  To that
end, I fixed a couple of build issues that occurred when KVM wasn't
available[2][3], removed the need to remember to run "make clean" after
modifying the list of installed packages to avoid ending up with a
broken build[4], and spent some time trying to debug why QEMU's
virtio-gpu implementation doesn't seem to work nearly as well as
crosvm's, despite them being built on the same code.  (I haven't made
much progress with the latter though — I have a gut feeling it's a
memory safety problem, but running Valgrind on QEMU has so far been
painful.)  I also figured out and fixed the Cloud Hypervisor bug[5] I
mentioned last week, so once we update Cloud Hypervisor, the file
chooser portal no longer intermittently fails to configure itself, and I
did the usual server updates and Nixpkgs maintenance.

Yureka has been making progress with forwarding packets out of a network
driver VM to host userspace, where we plan to do routing with the aim to
later move it into a VM as well.  She's also started working on
implementing a vhost-user backend, which is how the host userspace
router will get packets to and from the application VMs.  Sounds like
it's still very much in the experimental phase, so there's no public
code to link to for any of this as yet.

[1]: https://spectrum-os.org/lists/archives/spectrum-devel/a7325ee5-eb7f-458c-9be6-404db676dd81@gmail.com/
[2]: https://spectrum-os.org/git/spectrum/commit/?id=1b33fcabdad8e4b76587848ad294bc056ca997f1
[3]: https://spectrum-os.org/git/spectrum/commit/?id=89b80752a275a4ca1818a49d86f27cca9e323389
[4]: https://spectrum-os.org/git/spectrum/commit/?id=c1e1449b2173913f08828bafc62dc112b2534acc
[5]: https://github.com/cloud-hypervisor/cloud-hypervisor/commit/ec8fceb4a6a537c4d838287d47edc2c156379b4e

Until next week!  I'll be at BornHack until Wednesday morning, so if you
are too and want to talk about Spectrum, get in touch. :)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

                 reply	other threads:[~2025-07-21  7:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87ikjmt2gx.fsf@alyssa.is \
    --to=hi@alyssa.is \
    --cc=demiobenour@gmail.com \
    --cc=discuss@spectrum-os.org \
    --cc=yuka@yuka.dev \
    /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).