Control: tag -1 + moreinfo On 2025-04-01 00:11, Francesco Poli (wintermute) wrote: > After: > > $ mkdir -p ~/.cache/sbuild/build > $ cd /dev/shm > $ TMPDIR=/dev/shm mmdebstrap-autopkgtest-build-qemu \ > --size=25G --boot=efi sid unstable-autopkgtest-amd64.img > $ mv -i unstable-autopkgtest-amd64.img ~/.cache/sbuild/ > > I can run 'sbuild-qemu-boot': > > $ sbuild-qemu-boot --boot=efi --shared-dir $(pwd) > unstable-autopkgtest-amd64.img
> But, as soon as I update the image with: > > $ sbuild-qemu-update --boot=efi unstable-autopkgtest-amd64.img > > I can no longer run 'sbuild-qemu-boot': > > $ sbuild-qemu-boot --boot=efi --shared-dir $(pwd) > unstable-autopkgtest-amd64.img I cannot reproduce this at the momemt, could you try it again? Note that from experience, it is quite possible that sbuild-qemu-update just happened to update in a moment where a GRUB toolchain update within the VM encountered an issue. This is what I'd suspect here. Note that you can use pass the --snapshot option to sbuild-qemu-update and it will create a snapshot of the original image within QCOW2. You can have multiple of those, and delete them or rollback using qemu-img. Best, Christian
