kvdo-6.2.6.3 does not build against 5.17.4-200.fc35 about kvdo HOT 11 CLOSED

Hello,

Solution seems to be here :

• lwfinger/rtl8723ds#15
• lwfinger/rtl8723ds@76fb806

from kvdo.

Hi @tabowling, we are getting closer and closer every day for getting our mainline contribution out. Most of the major tasks that we have identified at this point have been addressed and we're just working on buttoning up the various low-level items that remain.

For your Fedora hypervisor being F36, can you provide details on how you are consuming the VDO code? That will help me with ensuring that we can help you get back up and running as soon as possible.

I will take ownership of this issue moving forward to help get it resolved.

from kvdo.

Hi @tigerblue77, unfortunately, it's an artifact of our workflow that isn't easy to overcome. However, as I had mentioned in the first paragraph of another thread, we have some changes coming up to our workflow that will make things easier. Stay tuned.

from kvdo.

After upgrading from F35 to 36, my Fedora hypervisor is now useless since my VM pool is on a VDO block device. Much appreciation to a quick resolution to this.

Are we any closer to kvdo being in mainline kernel and Fedora distribution?
Many Thanks,
Terry

from kvdo.

Same issue, i had to downgrade f36 to f35 with kernel 5.14.10-300.fc35 so i can use vdo volume and start vms again. i have tried the rpm on copr.

i would really apreciate this works on f36 so i can do the upgrade.

from kvdo.

I have just updated my forks to build and run on the current version of Fedora 35 and Fedora 36. I have tested it to work up to kernel 5.17, but I believe there is a lingering issue on 5.18 that some others have reported where we encounter a NULL pointer. That is still being investigated by the team.

Sadly (or luckily?), neither the released versions nor the Rawhide version of Fedora is currently using the 5.18 kernel. Currently Fedora 35 and Fedora 36 are running on a 5.17 kernel, and Rawhide is pointing at a 5.19 kernel. Though I suspect the 5.18 kernel is probably going to be coming soon, since I see some recent 5.18 builds on koji.

But for now, if you look at my forks for kvdo and vdo, they will build on kernels up to the currently available version on Fedora. Similarly the dm-vdo COPR has been updated with builds for these releases.

from kvdo.

Hello @rhawalsh, why do all RedHat VDO's team members all fork this repository instead of working into branches ? And why don't you merge/pull request into this main repository ? I think it's not a good practice and will cause you problems when you will want to merge all repositories.

from kvdo.

I updated kvdo to kmod-kvdo-6.2.7.9-2.fc36.x86_64 from dm-vdo COPR, it works fine with 5.17.14-300.fc36.x86_64 kernel.

from kvdo.

Hi @grz0, thanks for the confirmation.

Just a heads up... If you notice that the 5.18 kernel becomes available, please hold off on updating to it. There is a known issue that triggers a NULL pointer error. I am away from the office until Monday evening, so I can't fix it until then if it shows up.

from kvdo.

Hi Andy,
welcome back!
On F36 stable kernel-5.17.13-300.fc36.x86_64 your module rebuild 6.2.7.9-2.fc36 installed correctly.

Before that I was using 8.2.0.0 self build out of desperation, given the ton of errors with vdo 6.2.x.x build on 5.17 was producing. FYI kernel.x86_64 5.18.5-200.fc36 hit the stable repo, so you may want to put it on hold via rpm deps.

can you provide details on how you are consuming the VDO code

My usages is as local dedup volume, no compression, on RAID1 SSD for my local virtualization host, running Fedora stable. The kernel change after the upgrade to F36 hit me hard, forcing me to downgrade the kernel - not really pleasant.

Given the "officially unofficial" rpm copr repo has now a stable build, I'm closing this issue.

from kvdo.

Hello,
Maybe that you should not close this issue until it's merges into this repository ?

PS for RH team : I'll answer my opened issues but I'm very busy these last weeks

from kvdo.