[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: failure to create disk-image
From: |
Ludovic Courtès |
Subject: |
Re: failure to create disk-image |
Date: |
Thu, 23 Apr 2020 22:21:16 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) |
Hi Roy,
Roy Lemmon <address@hidden> skribis:
> installing bootloader...
> Backtrace:
> 1 (primitive-load "/gnu/store/abqhniaagz11v7w8kz83ha1s6fc…")
> In ./gnu/build/vm.scm:
> 590:6 0 (initialize-hard-disk "/dev/vda" #:bootloader-package _ …)
>
> ./gnu/build/vm.scm:590:6: In procedure initialize-hard-disk:
> Throw to key `srfi-34' with args `(#<condition &message [message:
> "'/gnu/store/xlcbi7dc89n4wvyz4jk6j0g4590ymi6q-grub-efi-2.04/sbin/grub-install
> --boot-directory /fs/boot --bootloader-id=Guix --efi-directory /fs/dev/vda'
> exited with status 1; output follows:\n\n
> /gnu/store/xlcbi7dc89n4wvyz4jk6j0g4590ymi6q-grub-efi-2.04/sbin/grub-install:
> error:
> /gnu/store/xlcbi7dc89n4wvyz4jk6j0g4590ymi6q-grub-efi-2.04/lib/grub/i386-pc/modinfo.sh
> doesn't exist. Please specify --target or --directory.\n"] 7fe479410240>)'.
I think the key issue here was GRUB failing to install itself.
Did you eventually find out wha was going wrong?
It looks like ‘grub-efi’ was chosen whereas the VM is actually “legacy
BIOS”, not EFI.
Thanks,
Ludo’.