You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've enabled libvirtd, got OVMF firmware in /run/libvirt/nix-ovmf/OVMF_CODE.fd, symlinked to /nix/store/5bgi298wvmbgkz95s61ifwaihz68b0wb-OVMF-2017-12-05-fd/FV/OVMF_CODE.fd. However, VM using it can't boot from MBR-partitioned disk with MBR bootloader or floppy image, it just drops to EFI shell. I guess OVMF is built without SeaBIOS CSM which is required to boot from pre-EFI media. I see there is OVMF-CSM defined in nixpkgs; installing nixpkgs.OVMF-CSM, as well as nixpkgs.OVMF with or without --arg seabios true, only installs same "out" output of the same expression which produces that "fd" output which contains actual image used by qemu.
I see that both OVMF-CSM is defined in https://github.com/NixOS/nixpkgs/blob/master/pkgs/top-level/all-packages.nix#L14235 which looks suspicious to me, does it really revert seabios = null which is set in preceding one? How can I check which arguments the expression which produced store path had been given? And how can I install CSM-enabled OVMF? Anyway, nix-env -iA nixos.OVMF and nix-env -iA nixos.OVMF-CSM producing same result looks like a bug.
Steps to reproduce
Add following to your configuration.nix:
virtualisation.libvirtd.enable = true; environment.systemPackages = with pkgs; [ OVMF-CSM ];
or run nix-env -iA nixos.OVMF-CSM. Try to locate CSM-enabled OVMF image.
Technical details
system: "x86_64-linux"
host os: Linux 4.19.34, NixOS, 19.03.172231.7b36963e7a7 (Koi)
:b OVMF.override { seabios = seabios; } in nix-repl produces new "fd" and "out" outputs with new build hashes, but I can't confirm there's an image with CSM, I couldn't get it to boot from a floppy image.
This has been automatically marked as stale because it has had no activity for 180 days.
If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.
Here are suggestions that might help resolve this more quickly:
Search for maintainers and people that previously touched the related code and @ mention them in a comment.
Issue description
I've enabled libvirtd, got OVMF firmware in
/run/libvirt/nix-ovmf/OVMF_CODE.fd
, symlinked to/nix/store/5bgi298wvmbgkz95s61ifwaihz68b0wb-OVMF-2017-12-05-fd/FV/OVMF_CODE.fd
. However, VM using it can't boot from MBR-partitioned disk with MBR bootloader or floppy image, it just drops to EFI shell. I guess OVMF is built without SeaBIOS CSM which is required to boot from pre-EFI media. I see there is OVMF-CSM defined in nixpkgs; installingnixpkgs.OVMF-CSM
, as well asnixpkgs.OVMF
with or without--arg seabios true
, only installs same "out" output of the same expression which produces that "fd" output which contains actual image used by qemu.I see that both OVMF-CSM is defined in https://github.com/NixOS/nixpkgs/blob/master/pkgs/top-level/all-packages.nix#L14235 which looks suspicious to me, does it really revert
seabios = null
which is set in preceding one? How can I check which arguments the expression which produced store path had been given? And how can I install CSM-enabled OVMF? Anyway,nix-env -iA nixos.OVMF
andnix-env -iA nixos.OVMF-CSM
producing same result looks like a bug.Steps to reproduce
Add following to your configuration.nix:
virtualisation.libvirtd.enable = true;
environment.systemPackages = with pkgs; [ OVMF-CSM ];
or run
nix-env -iA nixos.OVMF-CSM
. Try to locate CSM-enabled OVMF image.Technical details
"x86_64-linux"
Linux 4.19.34, NixOS, 19.03.172231.7b36963e7a7 (Koi)
yes
yes
nix-env (Nix) 2.2.2
"nixos-unstable-19.09pre175916.1fc591f9a5b"
"nixos-19.03.172231.7b36963e7a7"
"nixpkgs-19.03pre153206.f753852e11d"
/nix/var/nix/profiles/per-user/root/channels/nixos
The text was updated successfully, but these errors were encountered: