-
-
Notifications
You must be signed in to change notification settings - Fork 16.6k
libkrun-efi: init at 1.15.1, krunkit: init at 0.2.2 (Supersedes #416870) #417062
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
base: master
Are you sure you want to change the base?
Conversation
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/prs-ready-for-review/3032/5606 |
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/prs-ready-for-review/3032/5633 |
6a82cfd
to
0097281
Compare
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.
Thanks for the work. I can confirm it works with podman libkrun backend to serve models through ramalama
. See some comments about library linkage and GPU support flag.
Oh and one more thing: please avoid adding commits like "Apply suggestions from code review" or "Delete pkgs/by-name/li/libkrun-efi/virglrenderer-override.nix" Instead, please squash these where they belong logically. |
Will do, thank you for the feedback. |
776652b
to
b8ad818
Compare
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.
Overall this looks good to me. The number of patches is a bit high for my taste, but it's subjective and whoever will actually merge the PR could clarify if it's ok as-is.
One question I have is why we do withGpu = false
by default, and whether perhaps it should be the other way around - default to support GPU emulation. Otherwise all consumers (e.g. podman) will have to explicitly request it, and I'm not sure it's worth a burden. What's the drawback of enabling GPU=1 by default?
None that I'm aware of. I honestly don't know why I decided to default to |
c1e9694
to
97d6736
Compare
|
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.
Tested with podman+ramalama, and it still works as expected.
|
Apart from the spurious test case and commit messages not complying with guidelines, this PR looks ok to me. (For commits, I'd prefer if this PR has just three: 1) add to maintainers; 2) add libkrun-efi; 3) add krunkit.) |
|
3b0757e
to
02d2f1a
Compare
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.
Please also update the title of the PR to reflect the versions.
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.
see the contributing guide for the ordering of meta and passthru
02d2f1a
to
55a2a63
Compare
Things done
quinneden
tomaintainers/maintainers-list.nix
libkrun-efi
, the EFI variant oflibkrun
foraarch64-darwin
.krunkit
, a CLI tool for running linux VMs onaarch64-darwin
usinglibkrun-efi
.nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.