[gentoo-user] virtualbox: no x-server after kernel upgrade to 4.12.12-gentoo

[Alexander Puchmayr]

Hi there,

I'm using a gentoo-guest inside a virtual box on a Win10 host. The last 
somewhat working combination was kernel 4.4.39/virtualbox-5.1.24.

When I update to kernel 4.12.12, the X-Server does not work anymore (I've also 
tried with 4.9.xx, same result -- no X)

I used genkernel to compile the kernel, copied the previous 4.4.39-config from 
/proc/config.gz to /usr/src/linux-4.12.12-gentoo via zcat, and did no further 
changes; so nothing relevant should be changed, at least to my knowledge.

After compilation of the kernel, required packages have been re-emerged:
- app-emulation/virtualbox-guest-additions
- x11-drivers/xf86-video-virtualbox

Booting with 4.12.12:
- sddm crashes with segfaults
- Starting X from the command line: X complains missing EGL_MESA_drm 
EGL_MESA_drm_image required.
: CommandLine Error: Option 'asan-instrument-assembly' registered more than 
once!
LLVM ERROR: inconsistency in registered CommandLine options
[??? No idea where this comes from :-( ]


cat /var/log/Xorg.0.log
[   793.159] (II) LoadModule: "vboxvideo"
[   793.159] (II) Loading /usr/lib64/xorg/modules/drivers/vboxvideo_drv.so
[   793.159] (II) Module vboxvideo: vendor="Oracle Corporation"
[   793.159]compiled for 1.19.3, module version = 1.0.1
[   793.159]Module class: X.Org Video Driver
[   793.159]ABI class: X.Org Video Driver, version 23.0
[   793.159] (**) Load address of symbol "VBOXVIDEO" is 0x7f3840a24380
[   793.160] (II) VBoxVideo: guest driver for VirtualBox: vbox
[   793.160] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[   793.160] (II) FBDEV: driver for framebuffer: fbdev
[   793.160] (II) VESA: driver for VESA chipsets: vesa
[   793.160] (II) vboxvideo: kernel driver found, not loading.  <-- 
!!
[   793.160] (II) vboxvideo: kernel driver found, not loading.
[   793.160] (II) modeset(0): using drv /dev/dri/card0
[   793.160] (II) Loading sub module "glamoregl"
[   793.160] (II) LoadModule: "glamoregl"
[   793.160] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
[   793.163] (II) Module glamoregl: vendor="X.Org Foundation"
[   793.163]compiled for 1.19.3, module version = 1.0.0
[   793.163]ABI class: X.Org ANSI C Emulation, version 0.4
[   793.163] (II) glamor: OpenGL accelerated X.org driver based.
[   793.217] (II) glamor: EGL version 1.4 (DRI2):
[   793.217] EGL_MESA_drm_image required.
[   793.218] (EE) modeset(0): glamor initialization failed

dmesg shows:
5.269630] VBoxService 5.1.24 r117012 (verbosity: 0) linux.amd64 (Sep 15 2017 
16:09:26) release log
  00:00:00.46 main Log opened 
2017-09-15T15:23:25.22099Z
[5.269691] 00:00:00.000133 main OS Product: Linux
[5.269717] 00:00:00.000165 main OS Release: 4.12.12-gentoo
[5.269740] 00:00:00.000191 main OS Version: #1 SMP Fri Sep 15 15:33:45 
CEST 2017
[5.269772] 00:00:00.000213 main Executable: /usr/sbin/vboxguest-
service
   00:00:00.000214 main Process ID: 4275
   00:00:00.000215 main Package type: LINUX_64BITS_GENERIC 
(OSE)
[5.272160] 00:00:00.002532 main 5.1.24 r117012 started. Verbose level 
= 0
[7.780006] vboxvideo :00:02.0: fb0: vboxdrmfb frame buffer device

Booting old 4.4.39 kernel[Just select old kernel in grub]
- sddm shows login screen
- /var/log/Xorg.0.log shows lots of lines regarding VBoxVideo driver.
- dmesg does not show the  vboxvideo line from above

Obviously, something is going terribly wrong here, and I'm getting stuck as I 
do not have any Idea where to start. The only thing that changed is a kernel 
upgrade and a rebuild of the virtual box modules. 

Any ideas?

Thanks in advance,
Alex

Re: [gentoo-user] virtualbox: no x-server after kernel upgrade to 4.12.12-gentoo

[R0b0t1]

On Fri, Sep 15, 2017 at 9:47 AM, Alexander Puchmayr
 wrote:
> Hi there,
>
> I'm using a gentoo-guest inside a virtual box on a Win10 host. The last
> somewhat working combination was kernel 4.4.39/virtualbox-5.1.24.
>
> When I update to kernel 4.12.12, the X-Server does not work anymore (I've also
> tried with 4.9.xx, same result -- no X)
>
> I used genkernel to compile the kernel, copied the previous 4.4.39-config from
> /proc/config.gz to /usr/src/linux-4.12.12-gentoo via zcat, and did no further
> changes; so nothing relevant should be changed, at least to my knowledge.
>
> After compilation of the kernel, required packages have been re-emerged:
> - app-emulation/virtualbox-guest-additions
> - x11-drivers/xf86-video-virtualbox
>
> Booting with 4.12.12:
> - sddm crashes with segfaults
> - Starting X from the command line: X complains missing EGL_MESA_drm
> EGL_MESA_drm_image required.
> : CommandLine Error: Option 'asan-instrument-assembly' registered more than
> once!
> LLVM ERROR: inconsistency in registered CommandLine options
> [??? No idea where this comes from :-( ]
>
>
> cat /var/log/Xorg.0.log
> [   793.159] (II) LoadModule: "vboxvideo"
> [   793.159] (II) Loading /usr/lib64/xorg/modules/drivers/vboxvideo_drv.so
> [   793.159] (II) Module vboxvideo: vendor="Oracle Corporation"
> [   793.159]compiled for 1.19.3, module version = 1.0.1
> [   793.159]Module class: X.Org Video Driver
> [   793.159]ABI class: X.Org Video Driver, version 23.0
> [   793.159] (**) Load address of symbol "VBOXVIDEO" is 0x7f3840a24380
> [   793.160] (II) VBoxVideo: guest driver for VirtualBox: vbox
> [   793.160] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
> [   793.160] (II) FBDEV: driver for framebuffer: fbdev
> [   793.160] (II) VESA: driver for VESA chipsets: vesa
> [   793.160] (II) vboxvideo: kernel driver found, not loading.  <-- 
> !!
> [   793.160] (II) vboxvideo: kernel driver found, not loading.
> [   793.160] (II) modeset(0): using drv /dev/dri/card0
> [   793.160] (II) Loading sub module "glamoregl"
> [   793.160] (II) LoadModule: "glamoregl"
> [   793.160] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
> [   793.163] (II) Module glamoregl: vendor="X.Org Foundation"
> [   793.163]compiled for 1.19.3, module version = 1.0.0
> [   793.163]ABI class: X.Org ANSI C Emulation, version 0.4
> [   793.163] (II) glamor: OpenGL accelerated X.org driver based.
> [   793.217] (II) glamor: EGL version 1.4 (DRI2):
> [   793.217] EGL_MESA_drm_image required.
> [   793.218] (EE) modeset(0): glamor initialization failed
>
> dmesg shows:
> 5.269630] VBoxService 5.1.24 r117012 (verbosity: 0) linux.amd64 (Sep 15 2017
> 16:09:26) release log
>   00:00:00.46 main Log opened
> 2017-09-15T15:23:25.22099Z
> [5.269691] 00:00:00.000133 main OS Product: Linux
> [5.269717] 00:00:00.000165 main OS Release: 4.12.12-gentoo
> [5.269740] 00:00:00.000191 main OS Version: #1 SMP Fri Sep 15 15:33:45
> CEST 2017
> [5.269772] 00:00:00.000213 main Executable: /usr/sbin/vboxguest-
> service
>00:00:00.000214 main Process ID: 4275
>00:00:00.000215 main Package type: LINUX_64BITS_GENERIC
> (OSE)
> [5.272160] 00:00:00.002532 main 5.1.24 r117012 started. Verbose level
> = 0
> [7.780006] vboxvideo :00:02.0: fb0: vboxdrmfb frame buffer device
>
> Booting old 4.4.39 kernel[Just select old kernel in grub]
> - sddm shows login screen
> - /var/log/Xorg.0.log shows lots of lines regarding VBoxVideo driver.
> - dmesg does not show the  vboxvideo line from above
>
> Obviously, something is going terribly wrong here, and I'm getting stuck as I
> do not have any Idea where to start. The only thing that changed is a kernel
> upgrade and a rebuild of the virtual box modules.
>
> Any ideas?
>

Details on this are sparse but you need to run @x11-modules-rebuild
after a kernel upgrade. You may also want to run @module-rebuild
depending on how you rebuilt your kernel.

https://wiki.gentoo.org/wiki/X_server/upgrade
https://forums.gentoo.org/viewtopic-p-6633091.html

Cheers,
 R0b0t1

Re: [gentoo-user] Re: [offtopic] Copy-On-Write ?

[Rich Freeman]

On Fri, Sep 8, 2017 at 3:16 PM, Kai Krakow  wrote:
>
> At least in btrfs there's also a caveat that the original extents may
> not actually be split and the split extents share parts of the
> original extent. That means, if you delete the original later, the copy
> will occupy more space than expected until you defragment the file:
>

True, but keep in mind that this applies in general in btrfs to any
kind of modification to a file.  If you modify 1MB in the middle of a
10GB file on ext4 you end up it taking up 10GB of space.  If you do
the same thing in btrfs you'll probably end up with the file taking up
10.001GB.  Since btrfs doesn't overwrite files in-place it will
typically allocate a new extent for the additional 1MB, and the
original content at that position within the file is still on disk in
the original extent.  It works a bit like a log-based filesystem in
this regard (which is also effectively copy on write).


-- 
Rich

Re: [gentoo-user] virtualbox: no x-server after kernel upgrade to 4.12.12-gentoo

[Alexander Puchmayr]

Am Freitag, 15. September 2017, 10:43:52 schrieb R0b0t1:
> On Fri, Sep 15, 2017 at 9:47 AM, Alexander Puchmayr
> 
>  wrote:
> > Hi there,
> > 
> > I'm using a gentoo-guest inside a virtual box on a Win10 host. The last
> > somewhat working combination was kernel 4.4.39/virtualbox-5.1.24.
> > 
> > When I update to kernel 4.12.12, the X-Server does not work anymore (I've
> > also tried with 4.9.xx, same result -- no X)
> > 
> > I used genkernel to compile the kernel, copied the previous 4.4.39-config
> > from /proc/config.gz to /usr/src/linux-4.12.12-gentoo via zcat, and did
> > no further changes; so nothing relevant should be changed, at least to my
> > knowledge.
> > 
> > After compilation of the kernel, required packages have been re-emerged:
> > - app-emulation/virtualbox-guest-additions
> > - x11-drivers/xf86-video-virtualbox
> > 
> > Booting with 4.12.12:
> > - sddm crashes with segfaults
> > - Starting X from the command line: X complains missing EGL_MESA_drm
> > EGL_MESA_drm_image required.
> > 
> > : CommandLine Error: Option 'asan-instrument-assembly' registered more
> > : than
> > 
> > once!
> > LLVM ERROR: inconsistency in registered CommandLine options
> > [??? No idea where this comes from :-( ]
> > 
> > 
> > cat /var/log/Xorg.0.log
> > [   793.159] (II) LoadModule: "vboxvideo"
> > [   793.159] (II) Loading /usr/lib64/xorg/modules/drivers/vboxvideo_drv.so
> > [   793.159] (II) Module vboxvideo: vendor="Oracle Corporation"
> > [   793.159]compiled for 1.19.3, module version = 1.0.1
> > [   793.159]Module class: X.Org Video Driver
> > [   793.159]ABI class: X.Org Video Driver, version 23.0
> > [   793.159] (**) Load address of symbol "VBOXVIDEO" is 0x7f3840a24380
> > [   793.160] (II) VBoxVideo: guest driver for VirtualBox: vbox
> > [   793.160] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
> > [   793.160] (II) FBDEV: driver for framebuffer: fbdev
> > [   793.160] (II) VESA: driver for VESA chipsets: vesa
> > [   793.160] (II) vboxvideo: kernel driver found, not loading. 
> > <-- !! [   793.160] (II) vboxvideo: kernel driver found, not loading.
> > [   793.160] (II) modeset(0): using drv /dev/dri/card0
> > [   793.160] (II) Loading sub module "glamoregl"
> > [   793.160] (II) LoadModule: "glamoregl"
> > [   793.160] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
> > [   793.163] (II) Module glamoregl: vendor="X.Org Foundation"
> > [   793.163]compiled for 1.19.3, module version = 1.0.0
> > [   793.163]ABI class: X.Org ANSI C Emulation, version 0.4
> > [   793.163] (II) glamor: OpenGL accelerated X.org driver based.
> > [   793.217] (II) glamor: EGL version 1.4 (DRI2):
> > [   793.217] EGL_MESA_drm_image required.
> > [   793.218] (EE) modeset(0): glamor initialization failed
> > 
> > dmesg shows:
> > 5.269630] VBoxService 5.1.24 r117012 (verbosity: 0) linux.amd64 (Sep 15
> > 2017 16:09:26) release log
> > 
> >   00:00:00.46 main Log opened
> > 
> > 2017-09-15T15:23:25.22099Z
> > [5.269691] 00:00:00.000133 main OS Product: Linux
> > [5.269717] 00:00:00.000165 main OS Release: 4.12.12-gentoo
> > [5.269740] 00:00:00.000191 main OS Version: #1 SMP Fri Sep 15
> > 15:33:45 CEST 2017
> > [5.269772] 00:00:00.000213 main Executable: /usr/sbin/vboxguest-
> > service
> > 
> >00:00:00.000214 main Process ID: 4275
> >00:00:00.000215 main Package type: LINUX_64BITS_GENERIC
> > 
> > (OSE)
> > [5.272160] 00:00:00.002532 main 5.1.24 r117012 started. Verbose
> > level = 0
> > [7.780006] vboxvideo :00:02.0: fb0: vboxdrmfb frame buffer device
> > 
> > Booting old 4.4.39 kernel[Just select old kernel in grub]
> > - sddm shows login screen
> > - /var/log/Xorg.0.log shows lots of lines regarding VBoxVideo driver.
> > - dmesg does not show the  vboxvideo line from above
> > 
> > Obviously, something is going terribly wrong here, and I'm getting stuck
> > as I do not have any Idea where to start. The only thing that changed is
> > a kernel upgrade and a rebuild of the virtual box modules.
> > 
> > Any ideas?
> 
> Details on this are sparse but you need to run @x11-modules-rebuild
> after a kernel upgrade. You may also want to run @module-rebuild
> depending on how you rebuilt your kernel.
> 
> https://wiki.gentoo.org/wiki/X_server/upgrade
> https://forums.gentoo.org/viewtopic-p-6633091.html
> 
Thanks for the answer!

I re-emerged both @x11-modules-rebuild and @module-rebuild, but it did not 
help a bit. Still the same problem.

I assume that the key is the vboxvideo line from dmesg. It registers a 
framebuffer device fb0, which may cause the Xorg-driver to fail. But I do not 
know how to disable this, since it comes from the vbox driver module itself.

Regards
Alex

Re: [gentoo-user] virtualbox: no x-server after kernel upgrade to 4.12.12-gentoo

[Alexander Kapshuk]

On Fri, Sep 15, 2017 at 5:47 PM, Alexander Puchmayr <
alexander.puchm...@linznet.at> wrote:

> Hi there,
>
> I'm using a gentoo-guest inside a virtual box on a Win10 host. The last
> somewhat working combination was kernel 4.4.39/virtualbox-5.1.24.
>
> When I update to kernel 4.12.12, the X-Server does not work anymore (I've
> also
> tried with 4.9.xx, same result -- no X)
>
> I used genkernel to compile the kernel, copied the previous 4.4.39-config
> from
> /proc/config.gz to /usr/src/linux-4.12.12-gentoo via zcat, and did no
> further
> changes; so nothing relevant should be changed, at least to my knowledge.
>
> After compilation of the kernel, required packages have been re-emerged:
> - app-emulation/virtualbox-guest-additions
> - x11-drivers/xf86-video-virtualbox
>
> Booting with 4.12.12:
> - sddm crashes with segfaults
> - Starting X from the command line: X complains missing EGL_MESA_drm
> EGL_MESA_drm_image required.
> : CommandLine Error: Option 'asan-instrument-assembly' registered more than
> once!
> LLVM ERROR: inconsistency in registered CommandLine options
> [??? No idea where this comes from :-( ]
>
>
> cat /var/log/Xorg.0.log
> [   793.159] (II) LoadModule: "vboxvideo"
> [   793.159] (II) Loading /usr/lib64/xorg/modules/drivers/vboxvideo_drv.so
> [   793.159] (II) Module vboxvideo: vendor="Oracle Corporation"
> [   793.159]compiled for 1.19.3, module version = 1.0.1
> [   793.159]Module class: X.Org Video Driver
> [   793.159]ABI class: X.Org Video Driver, version 23.0
> [   793.159] (**) Load address of symbol "VBOXVIDEO" is 0x7f3840a24380
> [   793.160] (II) VBoxVideo: guest driver for VirtualBox: vbox
> [   793.160] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
> [   793.160] (II) FBDEV: driver for framebuffer: fbdev
> [   793.160] (II) VESA: driver for VESA chipsets: vesa
> [   793.160] (II) vboxvideo: kernel driver found, not loading.
> <-- !!
> [   793.160] (II) vboxvideo: kernel driver found, not loading.
> [   793.160] (II) modeset(0): using drv /dev/dri/card0
> [   793.160] (II) Loading sub module "glamoregl"
> [   793.160] (II) LoadModule: "glamoregl"
> [   793.160] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
> [   793.163] (II) Module glamoregl: vendor="X.Org Foundation"
> [   793.163]compiled for 1.19.3, module version = 1.0.0
> [   793.163]ABI class: X.Org ANSI C Emulation, version 0.4
> [   793.163] (II) glamor: OpenGL accelerated X.org driver based.
> [   793.217] (II) glamor: EGL version 1.4 (DRI2):
> [   793.217] EGL_MESA_drm_image required.
> [   793.218] (EE) modeset(0): glamor initialization failed
>
> dmesg shows:
> 5.269630] VBoxService 5.1.24 r117012 (verbosity: 0) linux.amd64 (Sep 15
> 2017
> 16:09:26) release log
>   00:00:00.46 main Log opened
> 2017-09-15T15:23:25.22099Z
> [5.269691] 00:00:00.000133 main OS Product: Linux
> [5.269717] 00:00:00.000165 main OS Release: 4.12.12-gentoo
> [5.269740] 00:00:00.000191 main OS Version: #1 SMP Fri Sep 15
> 15:33:45
> CEST 2017
> [5.269772] 00:00:00.000213 main Executable: /usr/sbin/vboxguest-
> service
>00:00:00.000214 main Process ID: 4275
>00:00:00.000215 main Package type: LINUX_64BITS_GENERIC
> (OSE)
> [5.272160] 00:00:00.002532 main 5.1.24 r117012 started. Verbose
> level
> = 0
> [7.780006] vboxvideo :00:02.0: fb0: vboxdrmfb frame buffer device
>
> Booting old 4.4.39 kernel[Just select old kernel in grub]
> - sddm shows login screen
> - /var/log/Xorg.0.log shows lots of lines regarding VBoxVideo driver.
> - dmesg does not show the  vboxvideo line from above
>
> Obviously, something is going terribly wrong here, and I'm getting stuck
> as I
> do not have any Idea where to start. The only thing that changed is a
> kernel
> upgrade and a rebuild of the virtual box modules.
>
> Any ideas?
>
> Thanks in advance,
> Alex
>
>
>
>
>
>
>
>
The Gentoo wiki article referenced below emphasizes the fact that certain
kernel config options need enabling in order to have proper hardware
emulation. So you want to make sure you have those enabled in your kernel
config. Then take it from there.

https://wiki.gentoo.org/wiki/VirtualBox

[gentoo-user] thin-provisioning-tools - but I don't provision anything!!!!!

[Andrew Lowe]

Hi all,
I posted about a nasty infection my machine had with three versions of
Ruby a few days ago. In the process of trying to fix that I noticed a
thingy called "thin-provisioning-tools". I don't have anything thin and
I don't provision anything so why I ask?

From what I've been able to understand, it's something to do with
Device Mapper, snapshots and "many virtual devices to be stored on the
same data volume". This is all just jibberish to me and I have no idea
as to why this has suddenly appeared in my world update. I haven't asked
for it. I don't use any of the "more advanced" thingies such as lvm2 etc
so does anyone have any idea as to why I've now go this to install?

Back to Ruby killing now,
Andrew

Re: [gentoo-user] Dual booting with Windows 10

[Radoje Stojisic]

Hi all,

I am interested in doing something too. Do you talk about GPU 
Pass-through? Few months ago I wanted to try it myself but I own a Ryzen 
1800x and just one GPU. Is there a way with only one GPU?



Or do I really need 2GPUs and 2 Keyboard/Mouse?


Thanks

-Radi


On 15.09.2017 06:04, R0b0t1 wrote:

On Thu, Sep 14, 2017 at 8:16 PM, taii...@gmx.com  wrote:

Install it in a VM!


Yes, this is a very good option. I can verify everything  "works" but
sometimes you will experience sporadic errors with new hardware. You
won't waste time on this if it does happen; in every case I have seen
it shows up immediately.

Unfortunately you may have to go off the beaten path some and avoid
libvirtd or manually edit the same's configuration files. I can
provide summaries of the manuals and wikis available if you want.

Cheers,
  R0b0t1

Re: [gentoo-user] Dual booting with Windows 10

[R0b0t1]

On Fri, Sep 15, 2017 at 4:03 AM, Radoje Stojisic
 wrote:
> Hi all,
>
> I am interested in doing something too. Do you talk about GPU Pass-through?
> Few months ago I wanted to try it myself but I own a Ryzen 1800x and just
> one GPU. Is there a way with only one GPU?
>

That depends what you want to do. I'm going to assume what you
actually want is a 3D capable OpenGL provider in your VM.

If you have an Intel GPU, you can use VT-g to share it with virtual
machines. On Linux this is fairly recent development and I personally
have not had time to experiment with it. This functionality has,
surprisingly, been available on Windows for some time. Also available
on Windows is the ability to pool GPUs and allow virtual machines
computation time on them.

However, that doesn't work on Linux (yet), so the only alternative to
VT-g is VGA passthrough which requires another GPU.

> Or do I really need 2GPUs and 2 Keyboard/Mouse?
>

You don't need two keyboards and mice.

However, in the typical setup, when you pass your keyboard and mouse
to the virtual machine, you will be unable to interact with your host
machine. For a lot of users this might be fine. If QEMU crashes the
devices should be released to the host, but if the machine becomes
unresponsive you will have to wait or perform a hard reset.

Another option is to view your machine (Linux or Windows) with remote
desktop software. I personally prefer this one because it doesn't
require you to have a duplicate set of hardware. With Windows, RDP
provides better host/guest integration than anything else.


Taiidan recommended a separate USB controller for the guest. This can
be very helpful but also isn't necessary. You can pass specific USB
ports to a guest. (I have to test this with hotplugging but it looks
like it should work.)

Cheers,
 R0b0t1

Re: [gentoo-user] virtualbox: no x-server after kernel upgrade to 4.12.12-gentoo

[R0b0t1]

On Fri, Sep 15, 2017 at 3:36 PM, Marc Joliet  wrote:
> Am Freitag, 15. September 2017, 17:43:52 CEST schrieb R0b0t1:
>> Details on this are sparse but you need to run @x11-modules-rebuild
>> after a kernel upgrade.
>
> Since when has that been the case?  AIUI X11 modules live 100% in userspace,
> the kernel component is its own thing (unless you use nvidia, I suppose).
> @x11-modules-rebuild is for xorg-server upgrades, and even then, strictly
> speaking only when there is an ABI change (see the first of your links).
>
> But even so, the way Xorg stabilisations are handled in Gentoo (i.e.,
> everything is stabilised simultaneously) you shouldn't really need it in the
> first place; at least, I can't remember the last time I needed to use it.
>


Starting around a decade ago, I think. When I was originally given
this advice there was no detailed explanation available as to why it
was needed. However, I rebuilt my kernel a few times and was forced to
merge that package to get X11 working again, so causation was
established.

Recently I can verify that I haven't been doing it manually between
kernel upgrades.

R0b0t1

Re: [gentoo-user] thin-provisioning-tools - but I don't provision anything!!!!!

[Marc Joliet]

Am Freitag, 15. September 2017, 23:15:05 CEST schrieb Alan Mackenzie:
> Yes, but do I want it to go away?  What is it, what does it do?
> 
> OK, let's try emerge -s thin-provisioning-tools.  We get back only
> patronising garbage, namely "A suite of tools for thin provisioning on
> Linux" - well, duh!  Who write's this stuff?
> 
> So, WTF is thin provisioning?

I'm tempted to ask whether google is down or something, but I'm tired and 
waiting for 7z to finish so here you go anyway:

https://en.wikipedia.org/wiki/Thin_provisioning

I would say you probably don't need to care about it.

HTH
-- 
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup


signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] thin-provisioning-tools - but I don't provision anything!!!!!

[Neil Bothwick]

On Sat, 16 Sep 2017 01:56:54 +0800, Andrew Lowe wrote:

>   I posted about a nasty infection my machine had with three
> versions of Ruby a few days ago. In the process of trying to fix that I
> noticed a thingy called "thin-provisioning-tools". I don't have
> anything thin and I don't provision anything so why I ask?
> 
>   From what I've been able to understand, it's something to do
> with Device Mapper, snapshots and "many virtual devices to be stored on
> the same data volume". This is all just jibberish to me and I have no
> idea as to why this has suddenly appeared in my world update. I haven't
> asked for it. I don't use any of the "more advanced" thingies such as
> lvm2 etc so does anyone have any idea as to why I've now go this to
> install?

If you add -t to emerge @world you will probably see that it is lvm2 that
pulls this in, specifically the thin USE flag, which is on by default.

Add ":sys-fs/lvm2 -thin" to /etc/portage/package.use and it will go away.


-- 
Neil Bothwick

Too many clicks spoil the browse.


pgpwTXaWDGg4X.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] virtualbox: no x-server after kernel upgrade to 4.12.12-gentoo

[Marc Joliet]

Am Freitag, 15. September 2017, 17:43:52 CEST schrieb R0b0t1:
> Details on this are sparse but you need to run @x11-modules-rebuild
> after a kernel upgrade.

Since when has that been the case?  AIUI X11 modules live 100% in userspace, 
the kernel component is its own thing (unless you use nvidia, I suppose).  
@x11-modules-rebuild is for xorg-server upgrades, and even then, strictly 
speaking only when there is an ABI change (see the first of your links).

But even so, the way Xorg stabilisations are handled in Gentoo (i.e., 
everything is stabilised simultaneously) you shouldn't really need it in the 
first place; at least, I can't remember the last time I needed to use it.

HTH
-- 
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup


signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] thin-provisioning-tools - but I don't provision anything!!!!!

[Alan Mackenzie]

On Fri, Sep 15, 2017 at 23:38:21 +0200, Marc Joliet wrote:
> Am Freitag, 15. September 2017, 23:15:05 CEST schrieb Alan Mackenzie:
> > Yes, but do I want it to go away?  What is it, what does it do?

> > OK, let's try emerge -s thin-provisioning-tools.  We get back only
> > patronising garbage, namely "A suite of tools for thin provisioning on
> > Linux" - well, duh!  Who write's this stuff?

> > So, WTF is thin provisioning?

> I'm tempted to ask whether google is down or something, but I'm tired and 
> waiting for 7z to finish so here you go anyway:

For me, google is permanently down.

> https://en.wikipedia.org/wiki/Thin_provisioning

Yes, I've read it, thanks.  My question above was somewhat rhetorical.

> I would say you probably don't need to care about it.

I do.  I need to spend time and effort removing it.  It sounds like
something only useful in servers, yet I have a desktop profile installed.

There's something not quite right, here.

> HTH
> -- 
> Marc Joliet
> --
> "People who think they know everything really annoy those of us who know we
> don't" - Bjarne Stroustrup

-- 
Alan Mackenzie (Nuremberg, Germany).

Re: [gentoo-user] thin-provisioning-tools - but I don't provision anything!!!!!

[Alan Mackenzie]

Hello, Neil.

On Fri, Sep 15, 2017 at 21:47:01 +0100, Neil Bothwick wrote:
> On Sat, 16 Sep 2017 01:56:54 +0800, Andrew Lowe wrote:

> > I posted about a nasty infection my machine had with three
> > versions of Ruby a few days ago. In the process of trying to fix that I
> > noticed a thingy called "thin-provisioning-tools". I don't have
> > anything thin and I don't provision anything so why I ask?
> > 
> > From what I've been able to understand, it's something to do
> > with Device Mapper, snapshots and "many virtual devices to be stored on
> > the same data volume". This is all just jibberish to me and I have no
> > idea as to why this has suddenly appeared in my world update. I haven't
> > asked for it. I don't use any of the "more advanced" thingies such as
> > lvm2 etc so does anyone have any idea as to why I've now go this to
> > install?

> If you add -t to emerge @world you will probably see that it is lvm2 that
> pulls this in, specifically the thin USE flag, which is on by default.

> Add ":sys-fs/lvm2 -thin" to /etc/portage/package.use and it will go away.

Yes, but do I want it to go away?  What is it, what does it do?

OK, let's try emerge -s thin-provisioning-tools.  We get back only
patronising garbage, namely "A suite of tools for thin provisioning on
Linux" - well, duh!  Who write's this stuff?

So, WTF is thin provisioning?

> -- 
> Neil Bothwick

-- 
Alan Mackenzie (Nuremberg, Germany).

Re: [gentoo-user] thin-provisioning-tools - but I don't provision anything!!!!!

[Neil Bothwick]

Tbe time and effort is minimal, one line in package.use. Profiles have nothing 
to with it, the flag is turned on in the ebuild. It's not a server vs. desktop 
issue either. 

On 15 September 2017 22:43:15 BST, Alan Mackenzie  wrote:
>On Fri, Sep 15, 2017 at 23:38:21 +0200, Marc Joliet wrote:
>> Am Freitag, 15. September 2017, 23:15:05 CEST schrieb Alan Mackenzie:
>> > Yes, but do I want it to go away?  What is it, what does it do?
>
>> > OK, let's try emerge -s thin-provisioning-tools.  We get back only
>> > patronising garbage, namely "A suite of tools for thin provisioning
>on
>> > Linux" - well, duh!  Who write's this stuff?
>
>> > So, WTF is thin provisioning?
>
>> I'm tempted to ask whether google is down or something, but I'm tired
>and 
>> waiting for 7z to finish so here you go anyway:
>
>For me, google is permanently down.
>
>> https://en.wikipedia.org/wiki/Thin_provisioning
>
>Yes, I've read it, thanks.  My question above was somewhat rhetorical.
>
>> I would say you probably don't need to care about it.
>
>I do.  I need to spend time and effort removing it.  It sounds like
>something only useful in servers, yet I have a desktop profile
>installed.
>
>There's something not quite right, here.
>
>> HTH
>> -- 
>> Marc Joliet
>> --
>> "People who think they know everything really annoy those of us who
>know we
>> don't" - Bjarne Stroustrup

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [gentoo-user] thin-provisioning-tools - but I don't provision anything!!!!!

[Alan McKinnon]

On 15/09/2017 23:43, Alan Mackenzie wrote:
> On Fri, Sep 15, 2017 at 23:38:21 +0200, Marc Joliet wrote:
>> Am Freitag, 15. September 2017, 23:15:05 CEST schrieb Alan Mackenzie:
>>> Yes, but do I want it to go away?  What is it, what does it do?
> 
>>> OK, let's try emerge -s thin-provisioning-tools.  We get back only
>>> patronising garbage, namely "A suite of tools for thin provisioning on
>>> Linux" - well, duh!  Who write's this stuff?
> 
>>> So, WTF is thin provisioning?
> 
>> I'm tempted to ask whether google is down or something, but I'm tired and 
>> waiting for 7z to finish so here you go anyway:
> 
> For me, google is permanently down.
> 
>> https://en.wikipedia.org/wiki/Thin_provisioning
> 
> Yes, I've read it, thanks.  My question above was somewhat rhetorical.
> 
>> I would say you probably don't need to care about it.
> 
> I do.  I need to spend time and effort removing it.  It sounds like
> something only useful in servers, yet I have a desktop profile installed.
> 
> There's something not quite right, here.


Reign in the paranoia there friend. This is Gentoo and you have choices.
You are getting lvm because you elected to get it, it's set somewhere in
your USE.

What is LVM? A tool for managing disk volumes. If you don't know what it
is, you probably don't need it.

What is thin-provisioning? A way to allocate space on your disks without
actually using it until you put real data in. So a say 50G volume that
is empty will consume no disk space (or maybe a few K in overhead). Sort
of like sparse files for entire volumes.




-- 
Alan McKinnon
alan.mckin...@gmail.com

Re: [gentoo-user] thin-provisioning-tools - but I don't provision anything!!!!!

[Daniel Campbell]

On 09/15/2017 02:43 PM, Alan Mackenzie wrote:
> On Fri, Sep 15, 2017 at 23:38:21 +0200, Marc Joliet wrote:
>> Am Freitag, 15. September 2017, 23:15:05 CEST schrieb Alan Mackenzie:
>>> Yes, but do I want it to go away?  What is it, what does it do?
> 
>>> OK, let's try emerge -s thin-provisioning-tools.  We get back only
>>> patronising garbage, namely "A suite of tools for thin provisioning on
>>> Linux" - well, duh!  Who write's this stuff?
> 
>>> So, WTF is thin provisioning?
> 
>> I'm tempted to ask whether google is down or something, but I'm tired and 
>> waiting for 7z to finish so here you go anyway:
> 
> For me, google is permanently down.
> 
>> https://en.wikipedia.org/wiki/Thin_provisioning
> 
> Yes, I've read it, thanks.  My question above was somewhat rhetorical.
> 
>> I would say you probably don't need to care about it.
> 
> I do.  I need to spend time and effort removing it.  It sounds like
> something only useful in servers, yet I have a desktop profile installed.
> 
> There's something not quite right, here.
> 
>> HTH
>> -- 
>> Marc Joliet
>> --
>> "People who think they know everything really annoy those of us who know we
>> don't" - Bjarne Stroustrup
> 
The USE flag is likely enabled by default so users won't have to rebuild
all of lvm2 in order to get one small feature that may be useful in
self-hosting or experimental/learning scenarios. That is, the feature
seems useful enough to add as a default. But the default is in
sys-fs/lvm2, not in a profile:

'''
# Assume gentoolkit is present
$ grep "+thin" $(equery w sys-fs/lvm2)
IUSE="readline static static-libs systemd clvm cman corosync lvm1
lvm2create_initrd openais sanlock selinux +udev +thin device-mapper-only"
'''

If you have app-portage/gentoolkit (I highly recommend it) you can run
`equery d sys-block/thin-provisioning-tools` to find what's pulling it
in. It's probably lvm2, which is expected if you use LVM for anything.
If you don't have any need for it:

* Add `USE="-lvm"` to make.conf to ensure you don't get LVM through IUSE
* Add `sys-fs/lvm2` to package.mask, but realize you may lose partial
functionality with some things, like net-fs/nfs-utils NFS v4.1 support.
* emerge --changed-use --ask @world
* emerge --ask --depclean

or

* Put `sys-fs/lvm2 -thin` in package.use, run `emerge --changed-use
--ask @world`, and go about your day.

If you want to learn what thin provisioning is, you'll have to do
research on it. Manpages, project pages, fora, tutorials, etc. A good
way to find detailed information is to look up support threads and see
what difficulties other people are having, so you can go straight to
useful advice. (search terms like "problem lvm thin provision") If the
software's remotely popular, you'll get some good results. Since we've
already established lvm2 uses it, you can consult its documentation
(usually found from HOMEPAGE) and get an idea for what it is. Some
terminology is understood differently in specialized scenarios, so the
only way to learn it is to read it.

A Web search for 'lvm thin provisioning' turned up results from Red Hat,
tech blogs, and other sources. This information is easily available, if
you're willing to seek it.
-- 
Daniel Campbell - Gentoo Developer, Trustee, Treasurer
OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net
fpr: AE03 9064 AE00 053C 270C  1DE4 6F7A 9091 1EA0 55D6



signature.asc
Description: OpenPGP digital signature

Re: [gentoo-user] thin-provisioning-tools - but I don't provision anything!!!!!

[Marc Joliet]

Am Freitag, 15. September 2017, 23:43:15 CEST schrieb Alan Mackenzie:
> On Fri, Sep 15, 2017 at 23:38:21 +0200, Marc Joliet wrote:
> > Am Freitag, 15. September 2017, 23:15:05 CEST schrieb Alan Mackenzie:
> > > Yes, but do I want it to go away?  What is it, what does it do?
> > > 
> > > OK, let's try emerge -s thin-provisioning-tools.  We get back only
> > > patronising garbage, namely "A suite of tools for thin provisioning on
> > > Linux" - well, duh!  Who write's this stuff?
> > > 
> > > So, WTF is thin provisioning?
> > 
> > I'm tempted to ask whether google is down or something, but I'm tired and
> 
> > waiting for 7z to finish so here you go anyway:
> For me, google is permanently down.

I use Duckduckgo, myself.

> > https://en.wikipedia.org/wiki/Thin_provisioning
> 
> Yes, I've read it, thanks.  My question above was somewhat rhetorical.

OK

> > I would say you probably don't need to care about it.
> 
> I do.  I need to spend time and effort removing it.  It sounds like
> something only useful in servers, yet I have a desktop profile installed.
> 
> There's something not quite right, here.

As Alan and Neil already mentioned, it's set by default in the ebuild (i.e., 
"+thin" somewhere in IUSE, which you can also see in the output of eix).  
You'd have to ask the maintainer why that is, though.

HTH
-- 
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup


signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] thin-provisioning-tools - but I don't provision anything!!!!!

[Marc Joliet]

Am Freitag, 15. September 2017, 19:56:54 CEST schrieb Andrew Lowe:
> Hi all,
>   I posted about a nasty infection my machine had with three versions of
> Ruby a few days ago. In the process of trying to fix that I noticed a
> thingy called "thin-provisioning-tools". I don't have anything thin and
> I don't provision anything so why I ask?
> 
>   From what I've been able to understand, it's something to do with
> Device Mapper, snapshots and "many virtual devices to be stored on the
> same data volume". This is all just jibberish to me and I have no idea
> as to why this has suddenly appeared in my world update. I haven't asked
> for it. I don't use any of the "more advanced" thingies such as lvm2 etc
> so does anyone have any idea as to why I've now go this to install?
> 
>   Back to Ruby killing now,
>   Andrew

Based on what I've researched for the other sub-thread, since you don't 
actually use LVM, then -- unless you set the wrong USE flags -- you probably 
have udisks:0 installed (it has an unconditional dependency on lvm2).  Use 
"emerge --depclean -pv lvm2" to find out for sure.

If it is udisks:0, then AFAICT you can get rid of it with appropriate USE flag 
settings ("equery depends" is your friend here).

HTH
-- 
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup


signature.asc
Description: This is a digitally signed message part.