diff options
| author | Niklas Hambüchen <mail@nh2.me> | 2020-07-03 01:35:36 +0200 |
|---|---|---|
| committer | Niklas Hambüchen <mail@nh2.me> | 2020-07-04 14:47:36 +0200 |
| commit | 5b16d4c9ce16acffc944c01ff95ea97a807d8f4a (patch) | |
| tree | 60412e61441b6bc331646d5dd32660bb2aa82d7e /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | 2fa351b6a51449942bcf1f95c575d2d5e50090c2 (diff) | |
qemu-vm.nix: Fix device name hardcodes on `useBootLoader`.
boot.loader.grub.device` was hardcoded to `bootDevice`, which is
wrong, because that's the device for `/`, and with `useBootLoader`
the boot loader is not on that device.
This bug probably came into existence because of bad naming;
`virtualisation.bootDevice` has description
"The disk to be used for the root filesystem", which is very confusing;
it should be `.rootDevice` then!
Unfortunately, the description is right and the attribute name is wrong,
so it is not easy to change this without deprecation.
This commit ensures that even if you use `useBootLoader` and
`diskInterface == "scsi"`, the created VM can boot through, and can run
`nixos-rebuild afterwards.
It also adds extra commentary to explain what's going on in this module
in general in relation to `useBootLoader`.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions