Bug#949456: vmdb2: grub failure with mklabel gpt
close 949456 thanks The bug was answered with documentation from upstream three years ago, and no further action was requested by the submitter. Please reopen if needed!
Bug#949456: vmdb2: grub failure with mklabel gpt
On Mon, Jan 20, 2020 at 05:54:03PM -0800, Matt Taggart wrote: > When I use the example yaml config at > > https://vmdb2-manual.liw.fi/#getting-started Note that in the mean while the manual has changed and uses an msdos partition table now. The code does have a working example, which gets tested automatically: https://gitlab.com/larswirzenius/vmdb2/-/blob/master/uefi.vmdb > If I change the mklabel step to use msdos instead of gpt then it works. The following is a working version. You need to use UEFI for grub, and add an EFI partition. I don't know of a way to use gpt with BIOS booting, but I may just be ignorant about that. ~~~yaml steps: - mkimg: "{{ output }}" size: 4G - mklabel: gpt device: "{{ output }}" - mkpart: primary device: "{{ output }}" start: 0% end: 100M tag: efi - mkpart: primary device: "{{ output }}" start: 100M end: 100% tag: / - kpartx: "{{ output }}" - mkfs: vfat partition: efi - mkfs: ext4 partition: / - mount: / - debootstrap: buster mirror: http://deb.debian.org/debian target: / - apt: install packages: - linux-image-amd64 tag: / - fstab: / - grub: uefi tag: / efi: efi ~~~ I hope that helps. -- I want to build worthwhile things that might last. --joeyh signature.asc Description: PGP signature
Bug#949456: vmdb2: grub failure with mklabel gpt
I'm currently working on a project that needs images generated via vmdb but i want to leave msdos partition table. Any news on resolution of this bug? Thanks, ATB Marco Marinello
Bug#949456: vmdb2: grub failure with mklabel gpt
Package: vmdb2 Version: 0.13.2+git20191220-1 When I use the example yaml config at https://vmdb2-manual.liw.fi/#getting-started I get the following error: Exec: ['chroot', '/tmp/tmpyacmp7io', 'grub-install', '--target=i386-pc', '--no-nvram', '--force-extra-removable', '--no-floppy', '--modules=part_msdos part_gpt', '--grub-mkdevicemap=/boot/grub/device.map', '/dev/loop0'] ERROR: Command failed: chroot /tmp/tmpyacmp7io grub-install --target=i386-pc --no-nvram --force-extra-removable --no-floppy --modules=part_msdos part_gpt --grub-mkdevicemap=/boot/grub/device.map /dev/loop0 b'' b"Installing for i386-pc platform.\ngrub-install: warning: this GPT partition label contains no BIOS Boot Partition; embedding won't be possible.\ngrub-install: warning: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged..\ngrub-install: error: will not proceed with blocklists.\n" Something went wrong, cleaning up! If I change the mklabel step to use msdos instead of gpt then it works. From IRC: ...It is, of course, missing a magic number in the device... But, yes, it makes sense that the generated image is not listed in /boot/grub/device.map Thanks, -- Matt Taggart tagg...@debian.org