Closed deejayem closed 1 year ago
It seems vmw_pvscsi is missing in linux-5.15.77. I pinned the kernel to 5.10.x and it started working. This is not a real solution, but a step in the right direction. I added the followin line to my configuration.nix:
boot.kernelPackages = pkgs.linuxPackages_5_10;
And added pkgs
into the arguments list on line 1, replacing: { ... }: {
with { pkgs, ... }: {
.
Follow up. After rebooting I was able to remove the added lines and I could rebuild nixos with linux-5.15.77 without issues.. I will test some more to see if I bump into any issues. (I need to resize my boot partition first, it seems Oracle defaults it to 100mb)
I realised I made a mistake in my initial investigations - when I tried different versions of nixos-infect, it was just re-using the version of hardware-configuration.nix
created the first time. After I added that, I was able to successfully run a modified version nixos-infect.
@johan-adriaans is that on aarch64? I'm currently working on the assumption that vmw_pvscsi
is working on at least some architectures.
@deejayem Yes, I started out with the following image: Canonical-Ubuntu-20.04-aarch64-2022.08.15-0
I have reinstalled my instances to double check, and it seems I too was confused with the /etc/nixos persistance. I did the same thing again and now it does not work as before. I did try some other things before that, so I will retrace what I did and report back later.
I am confused. I could swear I had the vmw_pvscsi module in my /etc config. But, after some research my previous fix does not work, but pulling in your pull request 118 worked for me! So thanks! :)
Running nixos-infect on an Ampere instance on Oracle Cloud (Ubuntu 22.04), I get this error:
~Initially I thought it was caused by https://github.com/elitak/nixos-infect/pull/115 but I got the same error using an older version of nixos-infect, and also when manually removing the reference to vmw_pvscsi from the latest version.~ This is caused by the mentioned issue - I was still using the hardware configuration generated by the first run.
I tried nixos-unstable, nixos-22.05 and nixos-22.11 channels, and get the same error one all three.