On Fri, Feb 12, 2021 at 06:55:35PM +0100, Emmanuel Kasper wrote: > Le 12/02/2021 à 12:36, Evgeni Golov a écrit : > > On Fri, Feb 12, 2021 at 10:03:08AM +0100, Thomas Lange wrote: > >> This behaviour was also reported as #982182 > > > > Interesting, thanks! > > > > To me the GRUB change seems reasonable, even if a tad unexpected in a > > point release. > > > > You change to FAI [1] looks pretty much how I would envision a correct > > fix in the Vagrant box too, just executed at a different time. > > > > Thanks! > > > > [1] > > https://github.com/faiproject/fai-config/commit/bf90f3048f552f2dc1a0f50766646dff9f67aef9 > > > > Thanks Thomas for the pointer to #982182. > The bug on the Vagrant box is similar but the root cause is different. > On the latest buster box: > > vagrant ssh -- sudo debconf-show grub-pc | grep grub-pc/install_devices: > * grub-pc/install_devices: /dev/vda > > This is because the box is built with packer which uses virtio-blk from > qemy by default and create such devices. > > So for the vagrant side of this, at least for buster we should switch > the default disk driver to virtio-scsi, which creates during the install > a /dev/sda debconf entry, which is the same device name grub sees on > VirtualBox and its sata controller.
This would break here, as my Vagrant uses virtio-blk too (and I think that's the default these days in libvirt). However here (albeit on 10.4, see #982592), debconf-show grub-pc | grep grub-pc/install_devices yields empty, and this is also probably the reason why it fails to upgrade to 10.8.
