VirtIO SCSI kernel module not detected by nixos-generate-config

[r-vdp]

Describe the bug
When installing NixOS in a VirtualBox VM using a VirtIO disk device, nixos-generate-config does not include the virtio_scsi kernel module in the boot.initrd.availableKernelModules setting, rendering the resulting system unbootable.
In the live system, this kernel module is loaded (verified with lsmod | grep virtio).

The module is also not detected when running nixos-generate-config from the resulting VM, meaning that the system would be rendered unbootable when the hardware config is regenerated (e.g. to detect newly added hardware).

To Reproduce
Steps to reproduce the behavior:

1. Configure a new VM with an empty disk connected via a VirtIO interface
2. Install using the latest NixOS installation ISO, using nixos-generate-config to generate the initial config.
3. Try to reboot into the installed system, stage 1 will hang because the root filesystem cannot be found.

Or, easier:

1. Run nixos-generate-config --show-hardware-config --no-filesystems from within a VirtualBox VM with the root filesystem on a VirtIO disk.
2. Observe that the virtio_scsi kernel module is not included in the boot.initrd.availableKernelModules setting.

Expected behavior
The virtio_scsi kernel module should be added to the boot.initrd.availableKernelModules setting by nixos-generate-config.

Metadata

• system: "x86_64-linux"
• host os: Linux 4.19.90, NixOS, 19.09.1629.ce54d9601ea (Loris)
• multi-user?: yes
• sandbox: yes
• version: nix-env (Nix) 2.3
• nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

[stale]

Hello, I'm a bot and I thank you in the name of the community for opening this issue.

To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human.

The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it.

If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use Git blame or GitHub's web interface on the relevant files to find them.

Lastly, you can always ask for help at our Discourse Forum or at #nixos' IRC channel.

[jbenden]

I ran across this issue, too.

For the file

nixpkgs/nixos/modules/installer/tools/nixos-generate-config.pl

Line 187 in 7b2982e

if ($vendor eq "0x1af4" && $device eq "0x1004") {

, the vendor ID is still correct but the device ID is 0x1048.

[stale]

I marked this as stale due to inactivity. → More info