[LINUX] Kernel 5.8 and later

[PhoenixHGIC]

Unfortunately the update has already taken place and rolling back the Kernel is by no means straightforward.
Also due to our security/ compliance commitments as a company, we have to keep up to date with latest releases.

Which distro are you using?

We are using Ubuntu 20.10 (GNU/Linux 5.8.0-43-generic x86_64)

[Ejdesgaard]

The latest news can be seen here:
https://patchwork.kernel.org/project/li ... ies=427209

Associated correspondence on lkml.org, for those who are interested

https://lkml.org/lkml/2021/2/3/797

Good to see progress

[PTide]

@PhoenixHGIC,
VAL works with kernels 5.8 if you use the latest version form this experimеntal branch:
https://github.com/veeam/veeamsnap/tree/experimental
We plan to include it into the next update.

If you would like to request an official fix now, please contact our support team directly and make an inquiry.

Please note the same statements don't apply to 5.9 or later, so be sure not to upgrade to those until further notice.
But in 5.8, there are still some "left-overs" of the removed kernel functionality that enabled us to support it.

Thanks!

[marcwa19197]

Any news on this?
Im following https://patchwork.kernel.org/project/li ... rder=-date but i dont know how they are updating the information....

[Gostev]

Guys, I will share any significant updates here the moment I receive the news. Until then, consider the latest status update from me to be the current state.

[toxic9]

Hi! I have opened an incident on this subject and I never received an answer.
My question is simple, will ever be a new veeam for linux version with this problem fixed?
or will we keep on relying on workarounds from now on?
thanks

[marcwa19197]

As i understand, as soon as the needed kernel-patch is implemented by the linux kernel-team, veeam can work like before on Kernel < 5.8

[PTide]

Hi,

@toxic9,

My question is simple, will ever be a new veeam for linux version with this problem fixed?
or will we keep on relying on workarounds from now on?

The fix needs to be implemented both in VAL and in the Linux kernel. As soon as the kernel patch series that Veeam has developed to restore the required kernel functionality is accepted into the kernel, the VAL is expected to start working out of the box on those kernels that implement the patch.

Thanks!

[toxic9]

so if I understood correctly, the kernel devs should "accept" these changes?
I thought it was only depending on veeam devs.

thanks for your explanation.

[PTide]

Roughly speaking - yes. In order for the whole fix to work the kernel changes proposed by us have to be accepted by the kernel devs. Veeam team, in turn, has to write the kernel patch in such way that it satisifes the kernel maintainers' "sense of beautiful" : ) Well, jokes aside - the (linux) community has pretty strict standards of how things should be done, and also certain technical requirements have to be met.

Thanks!

[marcwa19197]

Im just reverted back to kernel 5.7.

On Fedora 33 just do the following (you need koji installed):

1.) koji download-build --arch=x86_64 kernel-5.7.0-1.fc33
2.) sudo dnf install kernel-5.7.0-1.fc33.x86_64.rpm kernel-core-5.7.0-1.fc33.x86_64.rpm kernel-devel-5.7.0-1.fc33.x86_64.rpm kernel-modules-5.7.0-1.fc33.x86_64.rpm
3.) reboot

This will download Kernel 5.7.0 and install it. After that you need an reboot and Veeam will work again.
I will wait till everything is ready for the newer kernels.

Thank you very much!

[Ejdesgaard]

Is the expectation that the patches will be approved/pulled for the 5.12 merge window or should we expect it to be pushed for 5.13 or later ?

[Gostev]

Since we have absolutely no control over the approval part, we don't have ANY expectations at the moment...