summary refs log tree commit diff
path: root/pkgs/applications/virtualization/crosvm
AgeCommit message (Collapse)AuthorFilesLines
2023-11-15crosvm: update homepageAlyssa Ross1-1/+1
There's now a website in addition to the repo, so we should use that.
2023-11-11crosvm: backport page size fix for testsAlyssa Ross1-1/+12
The version of crosvm we have packaged only passes its tests with 4K pages. The whole patch doesn't apply, but that's okay, because we don't run most of the affected tests.
2023-09-25crosvm.meta.mainProgram: initAlyssa Ross1-0/+1
2023-09-24crosvm: 116.1 -> 117.0Alyssa Ross1-4/+4
2023-08-25crosvm: 115.2 -> 116.1Alyssa Ross1-15/+5
2023-08-18crosvm: 114.1 -> 115.2Alyssa Ross1-7/+9
2023-08-18crosvm: remove obsolete pkg-config hackAlyssa Ross1-6/+0
This is fixed now, I think by e2f7c0c24 ("crosvm: Fix cross-compile in dev container").
2023-07-02pkgsMusl.crosvm: fix buildAlyssa Ross1-1/+11
2023-06-17crosvm: 113.0 -> 114.1Alyssa Ross1-4/+4
2023-05-14crosvm: 112.0 -> 113.0Alyssa Ross1-4/+4
2023-04-09crosvm: 111.1 -> 112.0Alyssa Ross2-4/+6
2023-03-16crosvm: 107.1 -> 111.1Alyssa Ross1-22/+8
I'm aware of a nasty bug in this crosvm version[1], which didn't affect me on earlier versions (although from the code it looks like the bug was already present). But it only affects vhost-user-gpu, which is probably a fairly obscure feature, so I guess it shouldn't hold us back? [1]: https://groups.google.com/a/chromium.org/g/crosvm-dev/c/v_7Gie37NCI
2022-11-18crosvm.updateScript: don't vendor Cargo.lockAlyssa Ross2-20/+0
This is no longer required as crosvm now includes a Cargo.lock in-tree again.
2022-11-18crosvm: 104.0 -> 107.1Alyssa Ross3-2258/+25
crosvm now includes a Cargo.lock again, so we don't need to vendor it into Nixpkgs. Its build system now compiles the seccomp policies into the binary, so we don't need to build and install those ourselves any more.
2022-11-18crosvm.updateScript: update release branch formatAlyssa Ross1-1/+1
For R106 and onwards, upstream has gone back to not having a separation between chromeos and not.
2022-11-18crosvm: switch back to old git repo URLAlyssa Ross1-1/+1
Despite having moved the main repo to crosvm/crosvm, release branches are still only being created on chromiumos/platform/crosvm. So we should have crosvm/crosvm as the homepage, but fetch from chromiumos/platform/crosvm. Link: https://github.com/NixOS/nixpkgs/pull/193746
2022-09-04crosvm: switch back to upstream virglrendererAlyssa Ross1-14/+5
We now have virglrenderer 0.10.0, which includes everything crosvm needs that wasn't in 0.9.1.
2022-08-17crosvm: install both .policy and .bpf filesAstro1-1/+4
`crosvm --seccomp-log-failures` requires the .policy files. see: https://crosvm.dev/book/building_crosvm.html#known-issues
2022-08-14crosvm: 103.3 -> 104.0Astro2-88/+456
2022-08-12crosvm: don't repeat the path to Cargo.lockAlyssa Ross1-1/+1
This makes it slightly more convenient to test a local crosvm, by not having to change the path to Cargo.lock twice. It's also just cleaner.
2022-08-12crosvm: get rid of upstream-info.jsonAlyssa Ross3-38/+19
This was important when building crosvm required assembling our own build tree from lots of different repositories, but now that they've moved to submodules, it's overly complicated and needlessly inconsistent with the rest of Nixpkgs.
2022-08-12crosvm: drop code for running integration testsAlyssa Ross1-5/+0
These are no longer by default as they have been extracted into their own crate, so this code wasn't doing anything. If we did want to run the integration tests again, we'd have to download kernel and rootfs binaries from Google, and that's more trouble than it's worth.
2022-08-12crosvm: use cpu arch name to find seccomp filesAlyssa Ross1-11/+6
This matches for both supported platforms, and the package is already marked incompatible with other processes, so we can simplify here.
2022-08-12crosvm: reindentAlyssa Ross1-42/+42
This style is more common across Nixpkgs.
2022-08-02crosvm: precompile seccomp policy filesAlyssa Ross1-5/+10
This saves crosvm having to compile them at runtime, and allows us to catch more errors at build time.
2022-07-23crosvm: add support for virgl_renderer{,_next}Alyssa Ross1-2/+7
2022-07-21crosvm.updateScript: update repo URLAlyssa Ross2-5/+2
https://chromium.googlesource.com/chromiumos/platform/crosvm/+/ed7d455a4364671d8dfaf2d3e65d25128861f650
2022-07-21crosvm: 100.14526.0.0-rc1 -> 103.3Alyssa Ross3-149/+504
This is the first update using the new versioning scheme in introduced in the previous commit.
2022-07-21crosvm.updateScript: stop trying manifest-versionsAlyssa Ross2-30/+11
manifest-versions never seems to contain the release build any more, so we can't use it to find the version of crosvm being served to CrOS devices. Instead, I've changed the update script to take the latest version of the appropriate crosvm Chrome OS release branch. This is the branch that gets served. Every release, it is branched off from the "chromeos" branch (which is the one that passes Chrome OS QA), and then collects any critical fixes over the lifetime of the release. With this change, I've introduced a new, simplified versioning scheme, e.g. 100.0. The tip build is always 1:1 with the Chrome version, so having both of those is redundant. The other number is the number of commits that have been added to the release branch after branching from the chromeos branch, so that the number will go up if we update to include a new commit from the same release.
2022-07-21crosvm.updateScript: update for new serving dashAlyssa Ross1-14/+16
The old dashboard no longer exists. Currently, the platform version being served doesn't exist in manifest versions, but that was also a problem we had before sometimes.
2022-07-21crosvm.updateScript: check for . in buildspec nameAlyssa Ross1-1/+1
Otherwise, we might only match a prefix of the version. (Although it's not likely to be a problem in practice — I doubt we'll end up in a situation where there's a buildspec number 10x the one we're looking for.)
2022-07-21crosvm.updateScript: remove unused importAlyssa Ross1-1/+0
2022-07-17crosvm: fix seccomp directory on aarch64Alyssa Ross1-1/+1
"arm" is for 32-bit ARM. (Which I don't think is even still supported, but it's still present.)
2022-07-16crosvm: enable debug infoAlyssa Ross1-0/+2
2022-04-13crosvm: 99.14468.0.0-rc1 -> 100.14526.0.0-rc1Alyssa Ross2-27/+36
2022-04-13crosvm.updateScript: generate Cargo.lockAlyssa Ross2-2/+17
2022-03-21crosvm: 81.12871.0.0-rc1 -> 99.14468.0.0-rc1Alyssa Ross4-81/+1524
crosvm now uses submodules for all of its dependencies to ease out-of-tree builds, so we no longer need to try to reconstruct a partial Chromium OS source tree ourselves. Yay! But, it no longer comes with a Cargo.lock, so we have to bundle that.
2021-05-08treewide: fix cargoSha256/cargoHashDaniël de Kok1-1/+1
Rust 1.50.0 incorporated a Cargo change (rust-lang/cargo#8937) in which cargo vendor erroneously changed permissions of vendored crates. This was fixed in Rust 1.51.0 (rust-lang/cargo#9131). Unfortunately, this means that all cargoSha256/cargoHashes produced during the Rust 1.50.0 cycle are potentially broken. This change updates cargoSha256/cargoHash tree-wide. Fixes #121994.
2021-01-23lib: Clean up how linux and gcc config is specifiedJohn Ericson1-1/+1
Second attempt of 8929989614589ee3acd070a6409b2b9700c92d65; see that commit for details. This reverts commit 0bc275e63423456d6deb650e146120c39c1e0723.
2021-01-22Revert "lib: Clean up how linux and gcc config is specified"Jonathan Ringer1-1/+1
This is a stdenv-rebuild, and should not be merged into master This reverts commit 8929989614589ee3acd070a6409b2b9700c92d65.
2021-01-21lib: Clean up how linux and gcc config is specifiedJohn Ericson1-1/+1
The `platform` field is pointless nesting: it's just stuff that happens to be defined together, and that should be an implementation detail. This instead makes `linux-kernel` and `gcc` top level fields in platform configs. They join `rustc` there [all are optional], which was put there and not in `platform` in anticipation of a change like this. `linux-kernel.arch` in particular also becomes `linuxArch`, to match the other `*Arch`es. The next step after is this to combine the *specific* machines from `lib.systems.platforms` with `lib.systems.examples`, keeping just the "multiplatform" ones for defaulting.
2021-01-16pkgs/applications: pkgconfig -> pkg-configBen Siraphob1-2/+2
2020-04-23crosvm: 79.12607.0.0-rc4 -> 81.12871.0.0-rc1Alyssa Ross2-13/+21
2020-04-23chromiumOSPackages.updateScript: fix buildspec urlAlyssa Ross1-1/+1
"paladin" doesn't seem to be up to date, whereas "full" seems to match what cros-updates-serving.appspot.com reports is currently being shipped to Chromebooks.
2020-02-28rustPlatform.fetchCargo: handle custom Cargo.lock patchfiles with validationBenjamin Hipple1-4/+1
Previously, we would asssert that the lockfiles are consistent during the unpackPhase, but if the pkg has a patch for the lockfile itself then we must wait until the patchPhase is complete to check. This also removes an implicity dependency on the src attribute coming from `fetchzip` / `fetchFromGitHub`, which happens to name the source directory "source". Now we glob for it, so different fetchers will work consistently.
2020-02-13treewide: change fetchCargoTarball default to opt-outBenjamin Hipple1-0/+3
Changes the default fetcher in the Rust Platform to be the newer `fetchCargoTarball`, and changes every application using the current default to instead opt out. This commit does not change any hashes or cause any rebuilds. Once integrated, we will start deleting the opt-outs and recomputing hashes. See #79975 for details.
2019-12-24crosvm: 77.12371.0.0-rc1 -> 79.12607.0.0-rc4Alyssa Ross3-44/+49
Replaced src munging with a custom unpackPhase because the previous approach couldn't handle a newly introduced path with a space, and this is cleaner anyway (but was impossible at the time due to unpackPhase not being forwarded to fetchcargo).
2019-12-24crosvm: add myself as maintainerAlyssa Ross1-0/+1
2019-12-24crosvm.updateScript: use more stable update sourceAlyssa Ross1-12/+18
It has been explained to me that cros-omahaproxy reports which versions are available to users, while cros-updates-serving reports the latest builds available for each channel. The latter is probably better for our use case anyway, and apparently, while both aren't officially supported, is less likely to randomly break. So let's use that instead, even if it is much more annoying to parse.
2019-11-06crosvm: init at 77.12371.0.0-rc1Alyssa Ross4-0/+202
Co-Authored-By: hyperfekt <git@hyperfekt.net>
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-07-05 19:48:50 +0000