From: Demi Marie Obenour <demiobenour@gmail.com>
To: Spectrum OS Development <devel@spectrum-os.org>
Subject: Cannot build release.nix without KVM
Date: Mon, 14 Jul 2025 01:38:26 -0400 [thread overview]
Message-ID: <b6ecd777-b93c-4f2b-b0ef-a92f3b38b66c@gmail.com> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 1179 bytes --]
On a Qubes OS VM (which doesn't have nested virtualization), building
release.nix fails because start-vmm-test (rightly) errors out. Having
KVM be a *build*-time dependency of Spectrum OS seems rather strict,
especially because I can always copy the generated files over to another
machine and run them there. In particular, I can copy the resulting image
and run it in QEMU.
Ideally I could use Nix's remote build support for this. However, that
is designed for the case where I am offloading work to a powerful and
trusted server, whereas in my case the remote machine is for testing
purposes only. Therefore, to save money, it is cheap, and it is also
generally treated as untrusted because I don't hold it to the same
standards I hold my highly trusted main laptop to. For instance, it
doesn't have credentials to send emails.
Is it possible to copy what I need for the tests (using 'nix copy'
or 'nix-copy-closure' perhaps?) and skip them locally? Can I run
the tests that do not need KVM while still running the rest? This
is probably simple for anyone familiar with Nix, but that is not
me.
--
Sincerely,
Demi Marie Obenour (she/her/hers)
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 7253 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2025-07-14 5:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 5:38 Demi Marie Obenour [this message]
2025-07-14 10:30 ` Cannot build release.nix without KVM Alyssa Ross
2025-07-15 15:36 ` Alyssa Ross
2025-07-17 14:40 ` Alyssa Ross
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=b6ecd777-b93c-4f2b-b0ef-a92f3b38b66c@gmail.com \
--to=demiobenour@gmail.com \
--cc=devel@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.
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).