Bug#648208: os-prober: blockdev --setro affects running kvm instances
Package: os-prober
Version: <= 1.65
> Since version 1.45, os-prober instead uses grub-mount when it's
available
> -- and if grub is installed to use os-prober, it will pull it in.
>
> So unless another bootloader is also using os-prober, or someone
> installs and uses it by hand, this won't happen in unstable/testing.
It's not really the case:
Using grub-2.02_beta2 and os-prober-1.65 If there is a KVM virtual
machine using an ext4 FS on LVM and writing on it, a simple
grub-mkconfig on, the server(hypervisor) create disk I/O errors on the
virtual machine.
So this problem is a real one.
You can reproduce it easily:
- Inside a KVM virtual machine:
- execute a dd that write on disk
- display with tail -f the kernel log (/var/log/messages)
- On the hypervisor/server:
- execute a grub-mkconfig with os-prober activated
=> You got bunches of I/O error in the virtual machine.
Inactivate os-prober is not a realistic solution because there is
situation where you need OS prober: automatic grub configuration file
creation that take in consideration an emergency system on another
partition that need os-prober to be detect for example. Another example
is cluster of servers using different partitions as system upgrade path
for easy roll-back.
Jean-François Maeyhieux (zentoo)
Reply to: