-
-
Notifications
You must be signed in to change notification settings - Fork 88
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
Reuse NixOS initrd #82
Conversation
95030f2
to
b29607b
Compare
This looks like an interesting work, I'll need to find time to test this out. I have only one wish, could we retain the functionality that we can build our custom kernel, eg. behind an option? We actually have usecases where we would like to run different custom kernels, meaning different versions, with different kernel configurations and patches in different microvms I've been already doing some work to enable custom kernels in microvms, but have not yet done any PR |
With this you will be able to use normal NixOS configuration mechanisms, no more extra hoops to jump through.
You should stop doing any kernel configuration that is specific to microvm.nix. Please test this. I want to merge it once the nixos-23.05 branch is born. |
I get a build failure trying to run this:
|
Yes, |
Worked correctly with my simple |
a9e8630
to
78ee2f4
Compare
too cumbersome even on the only two hypervisors that supported it
Flake lock file updates: • Updated input 'nixpkgs': 'github:nixos/nixpkgs/db24d86dd8a4769c50d6b7295e81aa280cd93f35' (2023-04-10) → 'github:nixos/nixpkgs/d30264c2691128adc261d7c9388033645f0e742b' (2023-05-23)
With nixos-23.05 having branched off, rust-hypervisor-firmware is now available to Flake users who want to stay on a stable branch. I hope this work makes life easier for everyone. |
No longer requires a custom kernel build
build-vm.nix
Call for users who run on nixos-unstable: please test and leave emojis here!