Hi Bernd, On 05/03/21 at 15:14 +0100, Bernd Schatz wrote: > > Hi, > > I create vagrant-boxes (libvirt and virtualbox) from debian/testing64 > > For avoiding the interactive menu in the case of a grub-pc update, > i added this line to my provisioning-shell script: > > > sudo debconf-communicate <<< "set grub-pc/install_devices /dev/sda" > > > Now i switched to the new debian/bullseye64 box, > and there it fails for libvirt. > The reason is that the libvirt-box uses another filesystem: > > > $ vagrant box list | grep bullseye > debian/bullseye64 (libvirt, 11.20210228.1) > $ vagrant ssh > vagrant@bullseye:~$ df -kh / > Filesystem Size Used Avail Use% Mounted on > /dev/vda1 20G 4.1G 15G 22% / > > > > on virtualbox: > > $ vagrant box list | grep bullseye > debian/bullseye64 (virtualbox, 11.20210228.1) > $ vagrant ssh > vagrant@bullseye:~$ df -khT / > Filesystem Type Size Used Avail Use% Mounted on > /dev/sda1 ext4 20G 4.4G 15G 24% / > > > is it possible to > > 1) use the same filesystem > > and/or > > 2) add this line to the basebox: > sudo debconf-communicate <<< "set grub-pc/install_devices /dev/sda"
This should no longer be needed. In the version of the boxes you are using, there's a systemd service running at first boot that does the same thing. See https://salsa.debian.org/cloud-team/debian-vagrant-images/-/commit/ac1f9d47d26148b8615866fbeec3c0ee9f35c1ab - Lucas
