New fc12 kernel (2.6.31) has broken VirtualBox

[typerlc]

Due to a deprecated API that has been removed in 2.6.31, VirtualBox, and possibly other virtualisation software will no longer work.

I have made a pacth for vbox 2.2.4 and 3.0.0b1 and these are posted on the upstream bug tracker and forum respectively.

Is the fc12 team aware of the potential problems with the 2.6.31 kernel update, and decided to go ahead anyway?

[scottro]

The problem is that VirtualBox is not ready for newer Linux kernels. Don't you think this should be considered a VirtualBox, rather than Fedora problem?

However, I wonder if it's worth posting this in Fedora's bugzilla as well. I'm sure many people will run into the issue soon.


Both VBox and VMware have a (bad?) habit of falling behind the Linux kernel. Sometimes, it seems as if all the VBox people are using Ubuntu and don't notice till Ubuntu catches up.

(As I see you haven't posted much, and I have that CM thingie by my name, let me make it VERY clear that this is just my opinion, not a Fedora opinion. These forums have no official connection to the Fedora project.)

I don't think that this would be a valid reason to stop working with the 2.6.31 kernel. I think it's really up to the vendor to keep up or make it clear on their site that there product will not work with newer kernels.

For others running into the issue, here is your bug report. (I assume it's yours since it has the same user name.) :)

http://www.virtualbox.org/ticket/4264



While posting links, I'll also post the one to suggested guide on the VirtualBox forums about using diff and patch.

http://stephenjungels.com/jungels.net/articles/diff-patch-ten-minutes.html


I suspect a lot of people will soon be rather grateful to you for this patch.

I only have F12 on an underpowered laptop, so haven't tried it for myself. It's not a machine where I could practically use VBox.

By the way, do you know the VBox 3.x beta addresses the issue?

[typerlc]

The problem is that VirtualBox is not ready for newer Linux kernels. Don't you think this should be considered a VirtualBox, rather than Fedora problem?

I'm trying not to blame anyone here. But I just wanted to bring it to someone's attention (hopefully within fedora) that the decision to move to this kernel may have repercussions. As long as they have been carefully considered, then fine.

Anyway, as you alluded to, people will first come to fedora bugzilla/forums to track down the problem. It will appear to be a fedora problem.

Yes, the patch was posted by me.

By the way, do you know the VBox 3.x beta addresses the issue?

Not yet. But I posted an equivalent 3.0b1 patch here: http://forums.virtualbox.org/viewtopic.php?f=15&t=18970


Cheers,
Richard

[scottro]

Heh, judging from the reaction to your thread in the VBox forums, they're considering it a Fedora problem.

The thing is, that soon, I suspect, Arch, Gentoo, and probably Ubuntu's Koala will all start offering it too, so until they fix it, your patch will probably be a lifesaver.

[typerlc]

Heh, judging from the reaction to your thread in the VBox forums, they're considering it a Fedora problem.

Yes, I wasn't very impressed with the reaction. I tried to contact the moderator, but they have no listed contact details ... even PMs are disabled. So I lodged a complaint with the Sun staff listed on the beta forum. But I don't really expect them to do anything.

Buck-passing is the order of the day. Especially since everyone has too much to do, and not enough time to do it all in.