New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
crosvm: 104.0 -> 107.1 #193746
crosvm: 104.0 -> 107.1 #193746
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works but only if I keep passing --seccomp-log-failures
. Without it fails on x86_64:
[2022-10-03T18:36:28.237798106+02:00 INFO devices::acpi] Listening on acpi_mc_group of acpi_event family
[2022-10-03T18:36:28.380173248+02:00 ERROR crosvm::crosvm::sys::unix] child xhci controller (pid 1889588) died: signo 17, status 31, code 3
[2022-10-03T18:36:28.380920135+02:00 ERROR devices::proxy] failed write to child device process xhci controller: failed to send packet: Broken pipe (os error 32)
[2022-10-03T18:36:28.381030180+02:00 ERROR devices::proxy] failed to read result of Shutdown from child device process xhci controller: tube was disconnected
[2022-10-03T18:36:28.446001964+02:00 INFO crosvm] crosvm has exited normally
[2022-10-03T18:36:28.446516208+02:00 INFO crosvm] exiting with success
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: NixOS/nixpkgs#193746 Signed-off-by: Alyssa Ross <alyssa.ross@unikie.com>
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: NixOS/nixpkgs#193746 Signed-off-by: Alyssa Ross <alyssa.ross@unikie.com>
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: NixOS/nixpkgs#193746 Signed-off-by: Alyssa Ross <alyssa.ross@unikie.com>
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: NixOS/nixpkgs#193746 Signed-off-by: Alyssa Ross <alyssa.ross@unikie.com> Message-Id: <20220930210906.1696349-2-alyssa.ross@unikie.com>
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: NixOS#193746 Signed-off-by: Alyssa Ross <alyssa.ross@unikie.com> Message-Id: <20220930210906.1696349-2-alyssa.ross@unikie.com>
I've updated this to the latest crosvm, and backported a patch that fixes the sandboxing issue, but there's a new problem, which is that it doesn't build for aarch64. |
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: NixOS#193746
For R106 and onwards, upstream has gone back to not having a separation between chromeos and not.
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.
This is no longer required as crosvm now includes a Cargo.lock in-tree again.
aarch64 build is fixed, both cross and native. @astro can you check everything looks okay for you? |
Nice! Works for me on x86_64. |
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: #193746
Description of changes
Things done
sandbox = true
set innix.conf
? (See Nix manual)nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)nixos/doc/manual/md-to-db.sh
to update generated release notes