Bug#982591: grub-pc can't be updated non-interactively on debian/buster64
On 2/14/21 8:48 AM, Evgeni Golov wrote:
> On Sat, Feb 13, 2021 at 11:57:52PM +0100, Thomas Lange wrote:
>> IMO we cannot know which device name is used by the users virtualisation environment.
>> So, what is the be setting without knowing the device name?
>>
>> Or is /dev/sda used in most enviroments?
>
> For VirtualBox sda is a pretty safe bet, for libvirt it'd be either sda
> or vda (and I think we could set both in debconf, as that's a
> multiselect)
If you select multiple devices, it's going to fail on all the devices
which aren't present.
> AWS has another one, vxda I think? But this explicit bug
> is about vagrant (so virtualbox and libvirt) only anyways.
No, this but isn't specifically about vagrant. On top of this, libvirt
or AWS aren't virtualization environment, and even more, this depends on
the *driver*, not on the virtualization environment. Indeed, for a
single virtualization environment (for example KVM), you may have more
than one driver available (for example with kvm: virtio-blk or virtio-scsi).
> The only thing to consider with this approach: it should only be done
> when preparing images, not installing "real" systems. So in the
> cloud.d.o context that's safe, but probably not as a generic default in
> FAI and other tools.
Unfortunately, the image *must* be able to work with multiple drivers
(see my example with virtio-blk and virtio-scsi). The safest approach
was to have no default device set, though now it fails...
Cheers,
Thomas Goirand (zigo)
Reply to: