[Fixed] vboxdrv build failure, VBox 5.2.26 32-bit, kernel 4.4.168 (#18315)
-
- Posts: 25
- Joined: 21. Oct 2008, 04:05
- Primary OS: Ubuntu other
- VBox Version: PUEL
- Guest OSses: Ubuntu, Win2000/XP/7, OS/2, others...
Re: [Fixed] vboxdrv build failure, VBox 5.2.26 32-bit, kernel 4.4.168 (#18315)
Confirmed, virtualbox-6.0_6.0.4-128413~Ubuntu~xenial_amd64.deb resolved this VBox issue running 6.x on Ubuntu 16.04 Xenial with kernel 4.4.0-143-generic.
I am thankful,
I am thankful,
Re: [Fixed] vboxdrv build failure, VBox 5.2.26 32-bit, kernel 4.4.168 (#18315)
Are there any plans for this to be resolved on th 5.2 version? Not sure I can make the leap to test versions....
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: [Fixed] vboxdrv build failure, VBox 5.2.26 32-bit, kernel 4.4.168 (#18315)
The test builds are not as bad as they sound...skidvd wrote:Not sure I can make the leap to test versions....
They are what *I* would call "intermediate" builds, or the builds in between the releases. The "next-version" builds are known as the development builds.
If there's a "A.B.(2n-1)" test version, there will always be a "A.B.2n" release eventually.skidvd wrote:Are there any plans for this to be resolved on th 5.2 version?
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
- Posts: 17
- Joined: 8. Apr 2010, 00:58
- Primary OS: Ubuntu other
- VBox Version: OSE Debian
- Guest OSses: win xp, win7pro
Re: [Fixed] vboxdrv build failure, VBox 5.2.26 32-bit, kernel 4.4.168 (#18315)
I posted here viewtopic.php?f=7&t=92027&p=443993#p443993 that Ubuntu 14.04 kernel 4.4.0-143 causes
virtualbox version installed some time ago: 5.2.26 r128414 (Qt5.6.1) to fail with guest OS Win 7 Pro.
today I updated to kernel 4.4.0-144 and it also fails in the same manner.
I must revert to kernel 4.4.0-142 to make virtualbox work.
regards
oldunixguy
virtualbox version installed some time ago: 5.2.26 r128414 (Qt5.6.1) to fail with guest OS Win 7 Pro.
today I updated to kernel 4.4.0-144 and it also fails in the same manner.
I must revert to kernel 4.4.0-142 to make virtualbox work.
regards
oldunixguy
Re: [Fixed] vboxdrv build failure, VBox 5.2.26 32-bit, kernel 4.4.168 (#18315)
Same here. I just updated my Ubuntu 16.04 kernal to 4.4.0.145 and that will not allow Virtual Box 6.0.4 to open guest machines. I guess it's back to 4.4.0.142 again.
Richard
Richard
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: [Fixed] vboxdrv build failure, VBox 5.2.26 32-bit, kernel 4.4.168 (#18315)
Raspero, oldunixguy...
Did you even bother to read the thread from the beginning, the first post? Specifically the top part of the first post? In red letters? The issue *has* been resolved in the Test Builds!!!
Sometimes I wonder why I even bother to update the threads...
Did you even bother to read the thread from the beginning, the first post? Specifically the top part of the first post? In red letters? The issue *has* been resolved in the Test Builds!!!
Sometimes I wonder why I even bother to update the threads...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
- Posts: 17
- Joined: 8. Apr 2010, 00:58
- Primary OS: Ubuntu other
- VBox Version: OSE Debian
- Guest OSses: win xp, win7pro
Re: [Fixed] vboxdrv build failure, VBox 5.2.26 32-bit, kernel 4.4.168 (#18315)
YES SOCRATIS I READ THEM! So What? Changes thru the normal process have not reached us yet!
When will this be?
I am reporting data pertinent to this problem. Do the developers not want to understand the scope of the failure?
I am not able to use test builds. I am relegated to the normal VB, Ubuntu update methods.
We can only hope the kernel and VB developers READ our posts on the problem's scope....
I have received 2 kernel updates since this has been reported yet no fix yet.
And we can only hope that fixes trickle down the normal update methods sometime this year.
regards,
oldunixguy
When will this be?
I am reporting data pertinent to this problem. Do the developers not want to understand the scope of the failure?
I am not able to use test builds. I am relegated to the normal VB, Ubuntu update methods.
We can only hope the kernel and VB developers READ our posts on the problem's scope....
I have received 2 kernel updates since this has been reported yet no fix yet.
And we can only hope that fixes trickle down the normal update methods sometime this year.
regards,
oldunixguy
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: [Fixed] vboxdrv build failure, VBox 5.2.26 32-bit, kernel 4.4.168 (#18315)
Are you serious now? You're complaining about the delay of the official releases? Because you're willing to try the latest for the kernel, but not the latest of VirtualBox? You want to change Oracle's schedule? Really now?oldunixguy wrote:YES SOCRATIS I READ THEM! So What? Changes thru the normal process have not reached us yet!
There are test builds. If you don't like the process, there's not that much that can be done to accommodate your specific needs and/or desires, I'm sorry... Maybe if you had a contract with Oracle, although I highly doubt it.
Don't update the kernel then until you're sure that VirtualBox works with that. Or downgrade your kernel. Simple.oldunixguy wrote:I am not able to use test builds.
Ubuntu updates? Are you using the Ubuntu fork? I'm sorry, we don't even support this here. Please post the output of "VBoxManage -version", the complete output!oldunixguy wrote:I am relegated to the normal VB, Ubuntu update methods.
Yes, there is a fix, it's in the test builds. I thought I explained that part already! I hate repeating myself...oldunixguy wrote:I have received 2 kernel updates since this has been reported yet no fix yet.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
- Posts: 17
- Joined: 8. Apr 2010, 00:58
- Primary OS: Ubuntu other
- VBox Version: OSE Debian
- Guest OSses: win xp, win7pro
Re: [Fixed] vboxdrv build failure, VBox 5.2.26 32-bit, kernel 4.4.168 (#18315)
I too hate repeating myself.
Like most end users I rely on the Ubuntu software updater. Until this debacle I let the software updater install new kernels.
Likewise, when I start VB it prompts me if there is a new version and asks if I want to install it. I have always replied yes.
Apparently unlike you, we like to rely on these mechanisms because we just want stable systems and do not want to bit twiddle and poke around websites to get particular updates or even build kernels etc. We want to get work done with our computers and not spend time on monkeying around with things in contrast as apparently you do. In fact, I installed this VB years ago, built a single Win 7 pro guest and have never changed it except to allow VB to update itself when prompted. I like many end users don't even run command line programs for VB.
In response to your request:
In my original post I wrote:
5.2.26 r128414 (Qt5.6.1)
which came from the VB Help->About
Using your command line command:
5.2.26r128414
regards
oldunixguy
PS For what its worth I for a very long time constantly experience an MS Excel crash in VB, fully repeatable, and reported this problem to VB and never heard a peep nor seen a VB update that fixes it.
Like most end users I rely on the Ubuntu software updater. Until this debacle I let the software updater install new kernels.
Likewise, when I start VB it prompts me if there is a new version and asks if I want to install it. I have always replied yes.
Apparently unlike you, we like to rely on these mechanisms because we just want stable systems and do not want to bit twiddle and poke around websites to get particular updates or even build kernels etc. We want to get work done with our computers and not spend time on monkeying around with things in contrast as apparently you do. In fact, I installed this VB years ago, built a single Win 7 pro guest and have never changed it except to allow VB to update itself when prompted. I like many end users don't even run command line programs for VB.
In response to your request:
In my original post I wrote:
5.2.26 r128414 (Qt5.6.1)
which came from the VB Help->About
Using your command line command:
5.2.26r128414
regards
oldunixguy
PS For what its worth I for a very long time constantly experience an MS Excel crash in VB, fully repeatable, and reported this problem to VB and never heard a peep nor seen a VB update that fixes it.
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: [Fixed] vboxdrv build failure, VBox 5.2.26 32-bit, kernel 4.4.168 (#18315)
Are you trying to insult me? Monkeying? Seriously now?oldunixguy wrote:and not spend time on monkeying around with things in contrast as apparently you do
Listen, if you want help, you don't insult people, all right? Otherwise you know what the end result is going to be. And you're not going to like it, trust me! Consider this an official warning. And there's no 3 strikes rule...
So, drop the attitude and sit silently tight until the next official VirtualBox release. That's your option, that's your only option. I honestly couldn't care less if you like it or not, just stop whining. If you want you can always talk to your Oracle support representative. Oh, that's right, I forgot... you're a freeloader, you don't get to dictate what other people are doing!
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
- Posts: 6
- Joined: 15. Feb 2019, 03:20
Re: [Fixed] vboxdrv build failure, VBox 5.2.26 32-bit, kernel 4.4.168 (#18315)
For those who maybe interested..GOT IT WORKING on Vbox 5.2.27. did not try on version 6.0 test-builds
See also notes : https://bugs.launchpad.net/ubuntu/+sour ... ug/1818049
> DISTRIB_DESCRIPTION="Ubuntu 16.04.6 LTS" Xenial
> Linux 4.4.0-146-generic #172-Ubuntu SMP Wed Apr 3 09:00:08 UTC 2019 x86_64
https://www.virtualbox.org/wiki/Testbuilds
Downloaded test build Linux 64-bit 5.2.x revision 129666
Downloaded Extension Pack 5.2.x revision 129471
See also notes : https://bugs.launchpad.net/ubuntu/+sour ... ug/1818049
> DISTRIB_DESCRIPTION="Ubuntu 16.04.6 LTS" Xenial
> Linux 4.4.0-146-generic #172-Ubuntu SMP Wed Apr 3 09:00:08 UTC 2019 x86_64
https://www.virtualbox.org/wiki/Testbuilds
Downloaded test build Linux 64-bit 5.2.x revision 129666
Downloaded Extension Pack 5.2.x revision 129471
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: [Fixed] vboxdrv build failure, VBox 5.2.26 32-bit, kernel 4.4.168 (#18315)
Yes starbluedottts, it is stated in the first post of the thread that the 5.2.27 test builds contain the fix.starbluedottts wrote:For those who maybe interested..GOT IT WORKING on Vbox 5.2.27.
I guess nobody reads the first post anymore, maybe I should edit ALL the posts and copy paste the message, then people might notice...
ModEdit; Changed title from:
"vboxdrv build failure, virtualbox 5.2.26 32-bit, other distributions, Slackware 14.2, kernel 4.4.172" to:
"vboxdrv build failure, VBox 5.2.26 32-bit, kernel 4.4.168 (#18315)".
Related ticket: #18315: Kernel modules do not build with linux kernel 4.4.169, which appears to be fixed with builds r128999 and later, for both 5.2.27 and 6.0.5.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
- Posts: 25
- Joined: 21. Oct 2008, 04:05
- Primary OS: Ubuntu other
- VBox Version: PUEL
- Guest OSses: Ubuntu, Win2000/XP/7, OS/2, others...
Re: [Fixed] vboxdrv build failure, VBox 5.2.26 32-bit, kernel 4.4.168 (#18315)
Greetings,
VirtualBox 6.0.6-130049~Ubuntu~xenial has resolved this error for us. We were able to move back off the nightly release.
We appreciate the solution very much.
I am thankful,
VirtualBox 6.0.6-130049~Ubuntu~xenial has resolved this error for us. We were able to move back off the nightly release.
We appreciate the solution very much.
I am thankful,