Linux Kernel 5.0

[obwankenooby]

Hey P.Tide, just a quick "Thank you guys/team" - will test soon and report !!
Kind regards,
ok

[pdionisis@gmx.net]

Still no solution for Ubuntu 19.04 ?
Even experimental doe snot work
It compiles ok but does not load
insmod : ERROR : could not install module ./veeamsnap.ko Operation not permitted

[snoopy5707]

Kernel 5.0 was released in March, now we have July.....when can we expect the new version ??

by P.Tide » Jun 19, 2019 2:50 pm
The new update that will introduce support for kernel 5.0 is undergoing the final testing and will be released soon.

how long will be soon??

regards

[PTide]

Still no solution for Ubuntu 19.04 ?
Even experimental doe snot work
It compiles ok but does not load
insmod : ERROR : could not install module ./veeamsnap.ko Operation not permitted

Kindly try to insert the module one more time, run the following command immediately afterwards, and let me know what's in the output:

Code: Select all

dmesg | tail -20

[eberndt]

insmod : ERROR : could not install module ./veeamsnap.ko Operation not permitted

By any chance, are you running this command as sudo or root?

[pdionisis@gmx.net]

here is the output of dmesg :


root@i5:~/veeamsnap-experimental/source# dmesg | tail -20
[ 64.622198] input: HDA Intel PCH Line Out Surround as /devices/pci0000:00/0000:00:1f.3/sound/card0/input7
[ 64.622270] input: HDA Intel PCH Line Out CLFE as /devices/pci0000:00/0000:00:1f.3/sound/card0/input8
[ 64.622302] input: HDA Intel PCH Front Headphone as /devices/pci0000:00/0000:00:1f.3/sound/card0/input9
[41985.814146] usb 1-15: new high-speed USB device number 2 using xhci_hcd
[41985.967349] usb 1-15: New USB device found, idVendor=8087, idProduct=002c, bcdDevice= 2.00
[41985.967354] usb 1-15: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[41985.967357] usb 1-15: Product: USBr Composite Device
[41985.967359] usb 1-15: Manufacturer: Intel
[41985.967361] usb 1-15: SerialNumber: 0001
[41985.994057] hidraw: raw HID events driver (C) Jiri Kosina
[41985.999779] usbcore: registered new interface driver usbhid
[41985.999779] usbhid: USB HID core driver
[41986.007933] input: Intel USBr Composite Device as /devices/pci0000:00/0000:00:14.0/usb1/1-15/1-15:1.0/0003:8087:002C.0001/input/input10
[41986.066502] hid-generic 0003:8087:002C.0001: input,hidraw0: USB HID v1.10 Keyboard [Intel USBr Composite Device] on usb-0000:00:14.0-15/input0
[41986.066789] input: Intel USBr Composite Device as /devices/pci0000:00/0000:00:14.0/usb1/1-15/1-15:1.1/0003:8087:002C.0002/input/input11
[41986.126670] hid-generic 0003:8087:002C.0002: input,hidraw1: USB HID v1.10 Mouse [Intel USBr Composite Device] on usb-0000:00:14.0-15/input1
[41986.126983] input: Intel USBr Composite Device as /devices/pci0000:00/0000:00:14.0/usb1/1-15/1-15:1.2/0003:8087:002C.0003/input/input12
[41986.127592] hid-generic 0003:8087:002C.0003: input,hidraw2: USB HID v1.10 Mouse [Intel USBr Composite Device] on usb-0000:00:14.0-15/input2
[41998.444363] rfkill: input handler disabled
[42044.805543] Lockdown: insmod: Loading of unsigned module is restricted; see man kernel_lockdown.7


I run all the commands as root (sudo -i)

[pdionisis@gmx.net]

I found the problem: secure boot
Disabled it and it loaded fine but I have new problem:

root@i5:~/veeamsnap-experimental/source# veeam
Error: No such file or directory
Failed to connect: /var/tmp/veeam/socket/veeam.sock.
Failed to connect to veeamservice daemon.

[PTide]

Code: Select all

Lockdown: insmod: Loading of unsigned module is restricted; see man kernel_lockdown.7

This message means that the module must be signed before using it. Please check this article.

Thanks!

[pdionisis@gmx.net]

root@i5:~/veeamsnap-experimental/source# veeam
Error: Connection refused
Failed to connect: /var/tmp/veeam/socket/veeam.sock.
Failed to connect to veeamservice daemon.
root@i5:~/veeamsnap-experimental/source# veeamservice
Server is stopped.
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
No group found with name: [veeam]
--tr:Unable to create CGroupInfo for group name: [veeam].
Failed to init CLpbSvcServer.

[PTide]

Kindly try to start veeamservice manually via

Code: Select all

veeamservice --daemonize

You can also take an easier route and download the RTM version of VBR that includes the newest agent (3.0.2). Please find all details and the download link in this KB.

snoopy5707,

As you can see from the KB that I've mentioned, it is VERY soon

Thanks!

[pdionisis@gmx.net]

root@i5:~/veeamsnap-experimental/source# make load
Loading veeamsnap kernel module from current folder
mknod /dev/veeamsnap c 237 0
root@i5:~/veeamsnap-experimental/source# veeam
Error: Connection refused
Failed to connect: /var/tmp/veeam/socket/veeam.sock.
Failed to connect to veeamservice daemon.
root@i5:~/veeamsnap-experimental/source# veeamservice --daemonize
root@i5:~/veeamsnap-experimental/source# veeam
Error: Connection refused
Failed to connect: /var/tmp/veeam/socket/veeam.sock.
Failed to connect to veeamservice daemon.
root@i5:~/veeamsnap-experimental/source#



Also tried to download the full package (both ISO and update) from kb2970 but I can not
find the linux install file inside it. It seems that everything is for windows (except a plugin
directory for oracle and SAP Hana)

Any help?

[PTide]

Please get the packages here then.

Thanks!

[pdionisis@gmx.net]

Thanks .
It worked

[PTide]

FYI,

VAL v3.0.2 has been made generally available today and it fully supports v5 Linux kernel (up to 5.1.11 depending on the distro).

Thanks!

[Ge0rge]

Hi!
Sorry, what is the supported kernel version that is available in Fedora 30 repos?

[HannesK]

Hello George,
and welcome to the forums.

Just to make sure: you are not asking about Veeam Agent for Linux? You just want to run the repository role?

https://helpcenter.veeam.com/docs/backu ... =95u4#repo

Linux (bash shell, SSH and Perl are required). Check the full list of required Perl modules in this Veeam KB article.
64-bit edition of Linux must be able to run 32-bit programs. Pure 64-bit Linux editions are not supported (Perl installation must support 32-bit variables).

The kernel is not relevant for that use case.

Best regards,
Hannes

[Ge0rge]

Yes, I mean VAL 3.0.2. How it's not relevant? I need the kernel-devel package for the supported kernel version in order to build veeamsnap.ko, as far as I understand? The veeamsnap fails to build or install with the recent Fedora 30 kernel versions.

[Ge0rge]

That was my bad with an obsolete versions in dkms, it builds and works fine with the recent kernel-5.3.8.