SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The installer failed with exit code 1: VBoxExtPackHelperApp: error: The owner is not root: '/opt'.
set opt to root and then if you need to let users read and write to opt not VBOX then set users can modify opt
But your vbox is set to root:users right now this is what causes this.
chown root:root /opt/VirtulaBox
That's strange. What happened in my case was that I moved /opt itself to another partition and made a symlink. VB started working again when I put it back. The stuff in /usr/bin is the same as on your system.
What does "ls -lds /opt" look like?
Is that wrong?
Code:
bash-5.1# ls -lds /opt
4 drwxr-xr-x 3 m users 4096 aug 21 06:12 /opt
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,170
Original Poster
Rep:
A new test build 6.1.27-revision 146512,
a companion extension pack 6.1.27-146413,
a new guest additions 6.1.27-146512
and
a new development snapshot 6.1.97-146539
have been posted at, https://www.virtualbox.org/wiki/Testbuilds
Edit in: I've installed both test build 6.1.27-revision 146512, and extension pack 6.1.27-146413 and they are running perfectly (so far ).
Last edited by cwizardone; 08-26-2021 at 12:54 PM.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,170
Original Poster
Rep:
A new test build 6.1.27-revision-146688,
a companion extension pack 6.1.27-146688,
and
a new development snapshot 6.1.97-146677
have been posted at, https://www.virtualbox.org/wiki/Testbuilds
Last edited by cwizardone; 09-01-2021 at 10:41 AM.
A new test build 6.1.27-revision-146688,
a companion extension pack 6.1.27-146688,
and
a new development snapshot 6.1.97-146677
have been posted at, https://www.virtualbox.org/wiki/Testbuilds
I just added the the guest ISO and that did the job.
It was the guest that was failing will do a full install when is stable.
I do to much work in VM for windows and mac and slackware64-14.2.
So I put 127 on my test rig.
It seems the kernel has changed some headers and is unable to find type of cpu.
This is what I am using in my dev machine in Slackware64-current
For slackware64-current
Code:
Version 6.1.22 r144080 (Qt5.6.1)
using Oracle_VM_VirtualBox_Extension_Pack-6.1.22.vbox-extpack
using VBoxGuestAdditions_6.1.27-146512.iso
for the other ones slackware64-14.2 mac and windows using VBoxGuestAdditions_6.1.22.iso
At every boot I get "vboxdrv.sh building VirtualBox kernel modules" it used to do that only after a kernel upgrade, but now it builds the modules every single time which slows down boot time massively.
Virtualbox version is 6.1.26 r145957 (Qt5.6.1) and I'm running the 5.13.13 kernel (can't switch to 5.14 because of zfs) on Slackware current
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,170
Original Poster
Rep:
Quote:
Originally Posted by M0M0
At every boot I get "vboxdrv.sh building VirtualBox kernel modules" it used to do that only after a kernel upgrade, but now it builds the modules every single time which slows down boot time massively.
Virtualbox version is 6.1.26 r145957 (Qt5.6.1) and I'm running the 5.13.13 kernel (can't switch to 5.14 because of zfs) on Slackware current
That behavior was fixed in test build 6.1.27-146035 as reported in post #208 in this thread.
All the test builds I have installed since have behaved properly. https://www.linuxquestions.org/quest...ml#post6272156
That behavior was fixed in test build 6.1.27-146035 as reported in post #208 in this thread.
All the test builds I have installed since have behaved properly. https://www.linuxquestions.org/quest...ml#post6272156
Thanks! But I can't remember where to find the beta versions, on there web page I can only download the .26 version
edit: Nevermind the link is post #208 as well. Sorry
Last edited by M0M0; 09-18-2021 at 09:41 PM.
Reason: I should read before I ask
Edit in: Both are installed and working perfectly here.
Installed yesterday, working well on a Slackware64-current host. Only issue I have unrelated to this build as it's been around for awhile, is on a Slackware64-current guest machine, the kernel builds on each reboot. These two screen happen with every boot, shutdown/reboot.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,170
Original Poster
Rep:
A new test build 6.1.27-revision-147000,
a companion extension pack 6.1.27-146989,
and
a new development snapshot 6.1.97-147001
have been posted at, https://www.virtualbox.org/wiki/Testbuilds
Edit in: Installed the test build and extension pack and so far, so good.
Last edited by cwizardone; 09-23-2021 at 10:38 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
).
