Hi Philippe,
sorry for the late reply.
> FYI, this is the kind of wart this issue is forcing down on me and all my
> users:
> https://github.com/nexB/extractcode/blob/aa5da29014ce4fbffca53c09689a2623e2b78196/src/extractcode/vmimage.py#L82
>
>> def check_linux_kernel_is_readable():
>>"""
>>
I created this set of instructions in
https://raw.githubusercontent.com/nexB/extractcode/main/README.rst
I would appreciate if someone could minimally validate if this is the
correct way:
Adding support for VM images extraction
---
Adding support for VM
FYI, this is the kind of wart this issue is forcing down on me and all my users:
https://github.com/nexB/extractcode/blob/aa5da29014ce4fbffca53c09689a2623e2b78196/src/extractcode/vmimage.py#L82
> def check_linux_kernel_is_readable():
>"""
>Return True if the kernel executable file can be
Quoting my message from more than 2 years ago:
> The Ubuntu community puts little effort into libguestfs package
> maintenance except for copying whatever version from Debian and appliyng
> what looks like mechanically applied patches. Which is fine, but I don't
> expect anything to change.
>
>
Hiya, I was kindly wondering if there is an update on this?
I have naive suggestion:
what about creating a small optional package that has the dpkg-
statoverride script and let users be responsible to install it or not
install it?
That way, Ubuntu kernel maintainers wishes are respected, and
I'm creating a file:
/etc/kernel/postinst.d/fix-damn-bug-759725 with:
---
#/bin/sh
# https://bugs.launchpad.net/ubuntu/+source/linux/+bug/759725
set -e
version="$1"
if [ -z "$version" ]; then
exit 0
fi
exec dpkg-statoverride --update --add root root 0644 "/boot/vmlinuz-${version}"
---
As
BUG https://bugs.launchpad.net/ubuntu/+source/linux/+bug/759725 is
super, ultra annoying and useless!
:-@
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813662
Title:
Cannot build VM
To manage
Hilko, you probably know this but it looks like in the original thread
here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/759725
...that this could be fixed thusly:
To have this automatically happen with each new kernel, create
/etc/kernel/postinst.d/statoverride:
#!/bin/sh
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libguestfs (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813662
Title:
* Jarl:
>> how about providing that patch with the workaround we suggested?
>
> I may take a look at working on a patch. I have cloned libguestfs, but
> can you point me in the right direction libguestfs package? When I open
> https://packages.ubuntu.com/source/trusty/libguestfs
> and follow the
@Hilko:
> > @Hilko. First of all thank you very much for putting your time into
> > maintaining packages. This is highly appreciated.
> I was not fishing for thank-yous, I'm offering to get an Ubuntu-specific
> problem worked around. Take it or leave it.
I am sorry. I didn't mean to offend you.
* Jarl:
> @Hilko. First of all thank you very much for putting your time into
> maintaining packages. This is highly appreciated.
I was not fishing for thank-yous, I'm offering to get an Ubuntu-specific
problem worked around. Take it or leave it.
Instead of insisting that you know all there is
Launchpad has imported 3 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1670790.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
@Hilko. First of all thank you very much for putting your time into maintaining
packages. This is highly appreciated.
Secondly, I don't consider this issue a packaging issue (neither on the linux
nor the libguestfs package). Even though it is an issue that has emerged from
the ubuntu/debian
** Bug watch added: Red Hat Bugzilla #1670790
https://bugzilla.redhat.com/show_bug.cgi?id=1670790
** Also affects: libguestfs via
https://bugzilla.redhat.com/show_bug.cgi?id=1670790
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
* Jarl:
> @Richard Jones: I don't quite agree. It is not reported on the same
> package. This bug is not about requesting read-permission on the
> kernel (that may be one solution though). This bug is about
> virt-builder not working on ubuntu (where kernels are not readable by
> non-root users).
You can choose arbitrary kernels by setting the SUPERMIN_* environment
variables. See:
http://libguestfs.org/supermin.1.html#ENVIRONMENT-VARIABLES
http://libguestfs.org/guestfs-faq.1.html#how-can-i-compile-and-install-libguestfs-if-my-distro-doesnt-have-new-enough-qemu-supermin-kernel
There's
OK. Thanks for the link and explanation. So it doesn't have to be the
exact image of the kernel that is running? just a reasonable image?
If it is not strictly necessary ot be the image of the running kernel, I see a
better solution to this bug, which I also consider a better design of
It's how it works: http://libguestfs.org/guestfs-
internals.1.html#architecture
It doesn't need access to the running kernel (nor to live kernel memory),
but to a kernel image, and the kernel image in /boot is convenient for
that purpose. Anyway this works fine on every other Linux distro except
I tend to agree with you and the discussion on the other bug that I
don't see that preventing read-access to the running kernel gives any
security at all.
On the other hand I don't see any reason that specifically virt-bulider
need that read-access and should/could be designed to work without
The problem is that the kernel isn't readable by non-root for
voodoo reasons. (I don't agree this is a sane configuration)
This affects several programs and needs to be fixed either by
making the kernels readable, or by having Ubuntu developers
change the libguestfs packaging so it triggers
@Richard Jones: I don't quite agree. It is not reported on the same
package. This bug is not about requesting read-permission on the kernel
(that may be one solution though). This bug is about virt-builder not
working on ubuntu (where kernels are not readable by non-root users).
I agree though
This looks like an instance of our old favourite:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/759725
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813662
Title:
Cannot build VM
To manage
23 matches
Mail list logo
