Bug#982182: (no subject)

[Emmanuel Kasper]

Hi

This behaviour causes a number of problem when building disk images for 
hypervisors / cloud providers where you don't know beforehand the device 
name of the grub device on which grub will re install.
(see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982591 )

For instance I can build a disk-image setting grub-pc to install on 
/dev/sda, but the disk image will run on libvirt and the device name 
will be then be /dev/vda

We can hack around when creating the disk image with post creation steps 
calling

echo 'grub-pc grub-pc/install_devices multiselect /dev/vda' | sudo
debconf-set-selections

depending on the expected target, but maybe you can advise on a better 
approach ?