September 2024 - Spectrum Development

[PATCH v2] crosvm: Rename `--vhost-user-{fs,gpu}` args
by Dom Rodriguez 11 Nov '24

11 Nov '24

crosvm was producing warnings when using `--vhost-user-gpu` and `--vhost-user-fs`. In this commit, I have adjusted the `crosvm` invocations to look something like `--vhost-user $DEVICE,socket=$PATH`, where `$DEVICE` is, in this case, `gpu` or `fs`, and `$PATH` is the path to the Unix socket. Signed-off-by: Dom Rodriguez <shymega(a)shymega.org.uk> --- img/app/Makefile | 4 ++-- release/checks/wayland/default.nix | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/img/app/Makefile b/img/app/Makefile index 3adf8c4..11ef6e1 100644 --- a/img/app/Makefile +++ b/img/app/Makefile @@ -152,8 +152,8 @@ run-crosvm: $(imgdir)/appvm/blk/root.img start-vhost-user-gpu start-virtiofsd --disk $(RUN_IMG) \ -p "console=ttyS0 root=PARTLABEL=root" \ --net tap-name=tap0 \ - --vhost-user-fs build/virtiofsd.sock:virtiofs0 \ - --vhost-user-gpu build/vhost-user-gpu.sock \ + --vhost-user fs,socket=build/virtiofsd.sock:virtiofs0 \ + --vhost-user gpu,socket=build/vhost-user-gpu.sock \ --vsock cid=3 \ --serial type=file,hardware=serial,path=build/serial.log \ --serial type=stdout,hardware=virtio-console,stdin=true \ diff --git a/release/checks/wayland/default.nix b/release/checks/wayland/default.nix index d05aa88..a36dbab 100644 --- a/release/checks/wayland/default.nix +++ b/release/checks/wayland/default.nix @@ -29,7 +29,7 @@ nixosTest ({ lib, pkgs, ... }: { systemd.services.crosvm = { after = [ "crosvm-gpu.service" "weston.service" ]; requires = [ "crosvm-gpu.service" "weston.service" ]; - serviceConfig.ExecStart = "${lib.getExe pkgs.crosvm} run -s /run/crosvm --disk ${appvm}/img/appvm/blk/root.img --disk ${run}/blk/run.img -p \"console=ttyS0 root=PARTLABEL=root\" --vhost-user-gpu /run/crosvm-gpu.sock --vsock cid=3 --serial type=stdout,hardware=virtio-console,stdin=true ${appvm}/img/appvm/vmlinux"; + serviceConfig.ExecStart = "${lib.getExe pkgs.crosvm} run -s /run/crosvm --disk ${appvm}/img/appvm/blk/root.img --disk ${run}/blk/run.img -p \"console=ttyS0 root=PARTLABEL=root\" --vhost-user gpu,socket=/run/crosvm-gpu.sock --vsock cid=3 --serial type=stdout,hardware=virtio-console,stdin=true ${appvm}/img/appvm/vmlinux"; serviceConfig.ExecStop = "${lib.getExe pkgs.crosvm} stop /run/crosvm"; }; -- 2.44.1

3 10

[PATCH] Documentation: explain Nix using too many cores
by Alyssa Ross 29 Sep '24

29 Sep '24

This is confusing to people, and will be especially so if Spectrum is the first big Nix build they've done, which is not unlikely. Signed-off-by: Alyssa Ross <hi(a)alyssa.is> --- Documentation/installation/getting-spectrum.adoc | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/Documentation/installation/getting-spectrum.adoc b/Documentation/installation/getting-spectrum.adoc index 3620c79..29803aa 100644 --- a/Documentation/installation/getting-spectrum.adoc +++ b/Documentation/installation/getting-spectrum.adoc @@ -2,7 +2,7 @@ :page-parent: Build and Run :page-nav_order: 2 -// SPDX-FileCopyrightText: 2022-2023 Alyssa Ross <hi(a)alyssa.is> +// SPDX-FileCopyrightText: 2022-2024 Alyssa Ross <hi(a)alyssa.is> // SPDX-License-Identifier: GFDL-1.3-no-invariants-or-later OR CC-BY-SA-4.0 To get Spectrum, you need to build it from source. As long as you're @@ -16,6 +16,13 @@ TIP: Before you start, consider setting up the xref:binary-cache.adoc[Spectrum binary cache], which will save you a lot of time waiting for builds. +TIP: If you encounter build failures, especially timeouts or +out-of-memory (OOM) kills, Nix might be configured to run too many +builds at once, with too many cores per build. See Nix's +documentation for +https://nix.dev/manual/nix/2.24/advanced-topics/cores-vs-jobs.html[tuning +cores and jobs]. + == Trying Spectrum If you want to try Spectrum out to get a feel for it, without base-commit: 6e9c1f7967a44206e8f70d1d20e0f4e71987bed8 -- 2.45.2

1 0

[PATCH] lib/common.mk: move .POSIX out
by Alyssa Ross 21 Sep '24

21 Sep '24

The standard says the following, so I don't think it's specified that it's allowed to be in an include file: > If it appears as the first non-comment line in the makefile, make > shall process the makefile as specified by this section; otherwise, > the behavior of make is unspecified. Link: https://pubs.opengroup.org/onlinepubs/9799919799/utilities/make.html#tag_20… Fixes: c3fbeca ("lib/common.mk: init") Signed-off-by: Alyssa Ross <hi(a)alyssa.is> --- host/initramfs/Makefile | 2 ++ host/rootfs/Makefile | 2 ++ img/app/Makefile | 2 ++ lib/common.mk | 2 -- release/live/Makefile | 2 ++ vm/sys/net/Makefile | 2 ++ 6 files changed, 10 insertions(+), 2 deletions(-) diff --git a/host/initramfs/Makefile b/host/initramfs/Makefile index 06f69b3..8382296 100644 --- a/host/initramfs/Makefile +++ b/host/initramfs/Makefile @@ -1,6 +1,8 @@ # SPDX-License-Identifier: EUPL-1.2+ # SPDX-FileCopyrightText: 2021-2023 Alyssa Ross <hi(a)alyssa.is> +.POSIX: + include ../../lib/common.mk dest = build/initramfs diff --git a/host/rootfs/Makefile b/host/rootfs/Makefile index f4fb7a4..2f4445d 100644 --- a/host/rootfs/Makefile +++ b/host/rootfs/Makefile @@ -1,6 +1,8 @@ # SPDX-License-Identifier: EUPL-1.2+ # SPDX-FileCopyrightText: 2021-2024 Alyssa Ross <hi(a)alyssa.is> +.POSIX: + include ../../lib/common.mk dest = build/rootfs.erofs diff --git a/img/app/Makefile b/img/app/Makefile index 3adf8c4..79dd22e 100644 --- a/img/app/Makefile +++ b/img/app/Makefile @@ -2,6 +2,8 @@ # SPDX-FileCopyrightText: 2021-2024 Alyssa Ross <hi(a)alyssa.is> # SPDX-FileCopyrightText: 2022 Unikie +.POSIX: + include ../../lib/common.mk prefix = build/host diff --git a/lib/common.mk b/lib/common.mk index 8f11ecc..7733878 100644 --- a/lib/common.mk +++ b/lib/common.mk @@ -1,8 +1,6 @@ # SPDX-License-Identifier: EUPL-1.2+ # SPDX-FileCopyrightText: 2021, 2023 Alyssa Ross <hi(a)alyssa.is> -.POSIX: - # qemu-kvm is non-standard, but is present in at least Fedora and # Nixpkgs. If you don't have qemu-kvm, you'll need to set e.g. # QEMU_KVM = qemu-system-x86_64 -enable-kvm. diff --git a/release/live/Makefile b/release/live/Makefile index f45870d..a8c81c3 100644 --- a/release/live/Makefile +++ b/release/live/Makefile @@ -1,6 +1,8 @@ # SPDX-License-Identifier: EUPL-1.2+ # SPDX-FileCopyrightText: 2021-2023 Alyssa Ross <hi(a)alyssa.is> +.POSIX: + include ../../lib/common.mk dest = build/live.img diff --git a/vm/sys/net/Makefile b/vm/sys/net/Makefile index 00757db..2c2f084 100644 --- a/vm/sys/net/Makefile +++ b/vm/sys/net/Makefile @@ -1,6 +1,8 @@ # SPDX-License-Identifier: EUPL-1.2+ # SPDX-FileCopyrightText: 2021-2024 Alyssa Ross <hi(a)alyssa.is> +.POSIX: + include ../../../lib/common.mk prefix = build/svc base-commit: 0f5cfe23285d31c3f7ea1d0fbca967fa8bae8d59 -- 2.45.2

2 1

[PATCH] crosvm: Rename `--vhost-user-{fs,gpu}` args
by Dom Rodriguez 21 Sep '24

21 Sep '24

crosvm was producing warnings when using `--vhost-user-gpu` and `--vhost-user-fs`. In this commit, I have adjusted the `crosvm` invocations to look something like `--vhost-user $DEVICE`, where `$DEVICE` is, in this case, `gpu` or `fs`. I have run unit tests, but would appreciate testing. Signed-off-by: Dom Rodriguez <shymega(a)shymega.org.uk> --- img/app/Makefile | 4 ++-- release/checks/wayland/default.nix | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/img/app/Makefile b/img/app/Makefile index 3adf8c4..fd8befe 100644 --- a/img/app/Makefile +++ b/img/app/Makefile @@ -152,8 +152,8 @@ run-crosvm: $(imgdir)/appvm/blk/root.img start-vhost-user-gpu start-virtiofsd --disk $(RUN_IMG) \ -p "console=ttyS0 root=PARTLABEL=root" \ --net tap-name=tap0 \ - --vhost-user-fs build/virtiofsd.sock:virtiofs0 \ - --vhost-user-gpu build/vhost-user-gpu.sock \ + --vhost-user fs build/virtiofsd.sock:virtiofs0 \ + --vhost-user gpu build/vhost-user-gpu.sock \ --vsock cid=3 \ --serial type=file,hardware=serial,path=build/serial.log \ --serial type=stdout,hardware=virtio-console,stdin=true \ diff --git a/release/checks/wayland/default.nix b/release/checks/wayland/default.nix index d05aa88..774c9b9 100644 --- a/release/checks/wayland/default.nix +++ b/release/checks/wayland/default.nix @@ -29,7 +29,7 @@ nixosTest ({ lib, pkgs, ... }: { systemd.services.crosvm = { after = [ "crosvm-gpu.service" "weston.service" ]; requires = [ "crosvm-gpu.service" "weston.service" ]; - serviceConfig.ExecStart = "${lib.getExe pkgs.crosvm} run -s /run/crosvm --disk ${appvm}/img/appvm/blk/root.img --disk ${run}/blk/run.img -p \"console=ttyS0 root=PARTLABEL=root\" --vhost-user-gpu /run/crosvm-gpu.sock --vsock cid=3 --serial type=stdout,hardware=virtio-console,stdin=true ${appvm}/img/appvm/vmlinux"; + serviceConfig.ExecStart = "${lib.getExe pkgs.crosvm} run -s /run/crosvm --disk ${appvm}/img/appvm/blk/root.img --disk ${run}/blk/run.img -p \"console=ttyS0 root=PARTLABEL=root\" --vhost-user gpu /run/crosvm-gpu.sock --vsock cid=3 --serial type=stdout,hardware=virtio-console,stdin=true ${appvm}/img/appvm/vmlinux"; serviceConfig.ExecStop = "${lib.getExe pkgs.crosvm} stop /run/crosvm"; }; -- 2.44.1

2 4

Flake support - what are your thoughts?
by Dom (shymega) Rodriguez 09 Sep '24

09 Sep '24

Hello all! I'm picking up the Flake patch previously posted on this list, and want to get some input from developers & users alike. Do you prefer `nix-shell`/`nix-build` or Flakes? Would you be satisfied if we had compatibility shims for these tools? How do you feel about impure Flakes? Would you mind passing `--impure` to `nix $CMD` invocations? Any thoughts are welcome - feel free to DM me on Matrix/IRC if you don't want to reply to the list. My Matrix ID is: @dom:rodriguez, and my IRC nick is 'shymega[i]'. Thanks! Best wishes, -- Dom Rodriguez GPG Fingerprint: EB0D 45E6 D0DC 1BA1 A2B5 FC24 72DC F123 1E54 BD43

2 1