On Mon, Jun 25, 2018 at 12:57:28PM +0200, Lennart Poettering wrote:
On Mo, 25.06.18 11:54, Daniel P. Berrangé (berrange(a)redhat.com)
wrote:
> On Mon, Jun 25, 2018 at 12:47:35PM +0200, Lennart Poettering wrote:
> > On Mo, 25.06.18 11:23, Daniel P. Berrangé (berrange(a)redhat.com) wrote:
> >
> > > That would break applications like libguestfs which run as non-root and
> > > have valid need to access /boot/vmlinuz*
> >
> > Hmm, can you elaborate on that? What precisely do they need there?
>
> libguestfs boots a KVM guest to do its work inside and uses the installed
> kernel image from /boot/vmlinuz-$UNAME_R for this purpose, together with
> a custom initrd image with specific modules + specialized init binary.
>
> > If it's just the kernel image itself then they shouldn't really use
> > /boot anyway I figure, but instead the kernel in
> > /usr/lib/modules/`uname -r`/vmlinux. It's the same thing really.
>
> I wasn't aware of that duplicate vmlinuz file, I wonder how portable
> that is across distros.
I figure it should check /usr/lib/modules/`uname -r`/vmlinux first,
and then fall back to /boot/vmlinuz-$UNAME_R only if that didn't
exist.
libguestfs has been preferring the /lib/modules/... path for a while
now, although it will fall back to using /boot if it can't find the
kernel in /lib/modules.
Rich.
--
Richard Jones, Virtualization Group, Red Hat
http://people.redhat.com/~rjones
Read my programming and virtualization blog:
http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html