severity 1108745 important
tags 1108745 + upstream
thanks

Hello Daniel,

Daniel Leidert dijo [Fri, Jul 04, 2025 at 04:25:25PM +0200]:
Recently, images ćreated for UEFI systems fail to boot. I can reproduce the
problem with the base.vmdb2 file from tje vmb2 source. If I change that file to
create an image for Bookworm and boot it with QEMU, I end up in the Grub shell.
If I create an image for Ubuntu, I do not even get there. I can boot into a
live system, mount all necessary devices and run 'dpkg-reconfigure
grub-efi-amd64', and then it usually boots. vmdb2 shows no errors during its
operation.

Interestingly, the same appears to happen with vmdb2 in Bookworm. Given that
vmdb2 also hasn't seen any recent uploads, a third-party might be the culprit
here.

Images built for BIOS are not affected.

I am sorry I could not reply (not even _look at_ this bug) until now that
our dear friend Elbrus pulled my attention to it; I was preparing with the
family for the trip to Europe, and am now dedicating most of my attention
to DebConf.

I do not have my regular systems with me, and cannot really check this with
me. I will forward this bug report to the upstream developer; Lars, I hope
you can take a look at this. Otherwise, I'll be able to devote some time to
this once I'm back home, approx. a week from today.

Daniel, given you say that "images built for BIOS are not affected", I hope
you agree this bug does not break this package for all use cases, and will
degrade its severity to "important".

Thanks!

Attachment: signature.asc
Description: PGP signature

Reply via email to