VirtualBox

Opened 6 years ago

Closed 6 years ago

#17687 closed defect (fixed)

VB kernel mods fail to build

Reported by: George R. Goffe Owned by:
Component: host support Version: VirtualBox 5.2.6
Keywords: Cc:
Guest type: other Host type: other

Description

New kernel from Fedora folks (4.17.0-0.rc0.git7.1.fc29.x86_64) and "latest" VirtualBox not compatible.

Attachments (1)

vbox-install.log.gz (9.4 KB ) - added by George R. Goffe 6 years ago.
gzip'd install.log

Download all attachments as: .zip

Change History (10)

by George R. Goffe, 6 years ago

Attachment: vbox-install.log.gz added

gzip'd install.log

comment:1 by George R. Goffe, 6 years ago

No activity on this bug report?

Don't you guys test new versions of VB against the various distributions? Can you add Fedora (x86,x86_64) to that list?

Thanks,

George...

comment:2 by Socratis, 6 years ago

George, do you know what a wise man once said?

"Patience you must have my young padawan..."
Yoda

You didn't see activity after 6 day for a test release? I would call that normal procedure. The current release is Fedora 27. That's the one supported. Yes, Fedora *is* in the list of tested and supported software. The released versions of Fedora that is...

Fedora 28, is not yet supported because it's a beta. I think you can suspect what the status of not-even alpha software like Fedora 29 is going to be; being worked on. Having said that, you could also give a hand in that effort, if Fedora pre-releases are that important to you, and you know a little bit of programming.

So, just like Yoda said, patience you must have my young padawan... ;)

comment:3 by George R. Goffe, 6 years ago

Socratis (Yoda),

My intent in using early available software is to report back to developers on possible problems that may need to be addressed.

Bugs like this one seem to boil down to a kernel change where VB uses a field or function in the "new" kernel that doesn't exist or has changed in the "new" kernel. This almost always shows up in the install log. I don't know enough about the internals of VB or the internals of the kernel to affect useful changes.

What kind of feedback can I give that would be useful? Research as much as I can and then report it in a bug report?

Regards,

George...

in reply to:  3 comment:4 by Socratis, 6 years ago

Replying to obiewan:

What kind of feedback can I give that would be useful? Research as much as I can and then report it in a bug report?

Well, let me put it like that:

  • F27 is supported.
  • F28 is not yet supported, even in the wiki:Testbuilds (5.2.11 r122202, as of this writing), it's the next one to be addressed, so if you want to help Fedora become better supported, keep an eye on the updates of the Testbuilds and see if and when it works. I'm pretty sure there's a F28 ticket open, I simply can't find it at the time. Beta-test this one, feedback is appreciated!
  • Given the fact that you love Fedora, but Fedora isn't the only distro in town and other distros require the Dev's attention as well, I would expect F29 issues to be addressed at a later time, and it wouldn't be a far fetched *personal* estimate (I'm not a Dev, I'm not Oracle), that such issues will be addressed after F29 is in beta or even RC. But it *will* be addressed.

You simply are far ahead of your time ;)

comment:5 by Michael Thayer, 6 years ago

comment:6 by George R. Goffe, 6 years ago

Hi,

VB on this FC29 system just started working!

rpm -qa | grep virtualbox virtualbox-guest-additions-5.2.10-1.fc29.x86_64 VirtualBox-5.2-5.2.10_122088_fedora26-1.x86_64

Kernel: 4.17.0-0.rc1.git3.1.fc29.x86_64

I'm constantly applying package upgrades... New kerenel?

George...

comment:7 by Michael Thayer, 6 years ago

Did you actually test whether it was working before? The error you are reporting here should only cause problems for people using PCI pass-through. To be honest I do not even know how well it works when that error does not occur.

comment:8 by George R. Goffe, 6 years ago

Michael,

I have been running VB frequently. Just before I reported this bug, the start failed. I looked at the log and thought "new kernel... build of VB kernel mods failed... time to upgrade VB". I got the latest release of VB and installed it after removing the older version of VB. Start of VB failed. I got the dev version of VB and installed it, again the start failed. I wrote this bug. Earlier this evening I started VB and this time it started.

I'm gonna have to start tracking which kernel I'm running vs which level of VB I'm running. I usually keep a couple of versions of the VB install materials around for reference.

George...

comment:9 by janitor, 6 years ago

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy