I thought I had, but it was for my apcupsd (told ya I get easily confused, heh). I'll get on this now and let you know what happened. This looks like what might be the 'problem'...besides PEBCAK.

You have a working VirtualBox host working on your 14.2 machine. Which version of VirtualBox?

On another machine running a 4/27 current iso (full) install VirtualBox fails to start. What happens if you try to start it from the command line?

I added that to rc.local and created rc.local_shutdown. Something in the rc.local worked a little bit, this time in the log file I see that usb is recognized. Unfortunately I still get the same or similar error stuff at the end of the log file:

I'm wondering if it's because this is the huge.s kernel and not an/the generic smp kernel as PV suggests to use in the 'Changes_and_Hints.txt':

Either way, this *IS* still a Beta build I'm trying out, it's the 3.1GB iso installer of 27 APR 21, and I see that the latest iso has a buttload of changes, big ones it seems, compared to this installer. The only reason I don't go get it and try it, is because I've put a lot of work into getting *this* one going, other than the VirtualBox, and just hate wiping it all away and the 'upgrade.txt' got me so confused just a few paragraphs into it that I just need to sort of let this install lapse slowly and use it less and less without doing anything more to it until it won't bother me quite as much to just wipe everything and start from fresh, heh.

Other than that, I just don't see VirtualBox working on this install anytime soon and it seems to be a waste of time anymore since this build is already an over-ridden downgrade of what is there now to install and test. If I figure out that all I need to do is scrub the / drive when starting with a fresh install, I might get to trying that out, so long as the option to use an smp *or* the huge kernel is given this time (it wasn't during this install and was probably on purpose for whatever reason I won't, don't and can't question as the folks making our Slackware are gods, damn near, in my eyes, heh heh...they can code and know what the hell they're doing, I can open a text file and change stuff and screw up half the planet).

Thanks for all the suggestions though and the time you guys used to try and help me with this. I'm sure it's just something simple that will be cured by the time 15 comes out of Beta.

According to the manual, yes. It will work fine.
But I never do that my self, I first remove (uninstall) the previous installation, this mainly due to that I often switch between testing and official (full) releases.


As for SUPR0QueryVTCaps -> VERR_SVM_DISABLED

Make sure you have set Virtualization technology -> On
in your BIOS (this can be labeled something else, of course)

This is named differently depending on what motherboard manufacturer you have.

I had a similar problem my self after an BIOS update, but it said AMD-v disabled in my case (found that setting under Advanced -> CPU in my case. ASUS motherboard)

1 members found this post helpful.

Yes, I tried to find that in the BIOS early on also, but this MSI BIOS isn't very well explained and they skimped on finding and using a decent translator so that there's plenty of things like 'If want use, is best this is.' type of stuff, which makes understanding any particular instruction or whatever a bit more difficult for English readers, heh.. I'll see if maybe a DuckDuckGo search will find it though, because it could be in some little nook or cranny of this BIOS that I haven't found yet...even in the manual for it.

Okay, I found the AMD virtualization switch in my BIOS and it was disabled and is now enabled, rebooted, re-installed VirtualBox and started it up and all I get is the same two or three seconds and a segmentation fault message.

I'm going to play around with some different versions again, maybe I'll get lucky, heh.

Unfortunately still a no go. 6.1.18 and 6.1.20 are the only two versions that built without errors, but still would quit with a segmentation fault within a few seconds of starting up. Oh well.

You are trying the correct version of VirtualBox for the kernel you have installed?

Less fun with this type of problems, but all good as long as it is a problem (all problems have a solution )

Good reading you found the setting in BIOS.

Regarding your kernel being the huge, instead of generic. I have no idea, if this even matters as I always use a generic kernel my self.

So this is how I would've done it, in order to try solve this...

1. Remove the current installation of VirtualBox, by running the command
VirtualBox-6.1.20-143896-Linux_amd64.run uninstall

(of course using the version you have, which might be other than 6.1.20-143896)


2. Make sure the folder /opt/VirtualBox is empty, if not. Either rename it to something like VirtualBox_old, or have it removed
(I would've renamed it if it were me, have it removed once done trying the new installation).


3. As an option, but should not be needed.
Rename (Do not delete!) the /home/username/.config/VirtualBox to something like VirtualBox_backup
(This to make sure you'll keep any previously made guests. So do not delete the folder!)

4. As cwizardone mentioned, make sure you have the correct version for the kernel you are running.

5. Install VirtualBox again. Make notes of any errors, if there are any.

1 members found this post helpful.

Yep.

Doesn't matter. I run the huge kernel and don't even install the generic. With "modern" hardware there is no perceived performance advantage to running the generic kernel.


One can go to /opt/VirtualBox and run, as root, of course,
sh uninstall.sh
and that will remove VirtualBox and empty the directory.

One learn something new every day!

I had totally missed that uninstall.sh file/option Thank you!

1 members found this post helpful.

I have to presume I am, I am afterall using 5.10.32 that comes on the 4/27 current full install iso from AlienBob's site.

That's how I've been doing it (and/or the way cwizardone shows in a later post after this one of yours), after you mentioned it instead of relying on the newer version being installed doing it for me.


Like I said, I've started things from scratch almost every time. Nothing in the /opt/VirtualBox folder before each attempt at installing a version of it. The only thing(s) in that .config folder ever, are the log files showing the same exact errors from every single install attempt of every version. Starting VirtualBox in konsole each time so I can hopefully get some kind of message of what happens, and all I ever get is 'segmentation fault' and the errors I pasted in another post earlier from the VBox log(s) in that .config file. I think I also mentioned that I tried going from version(s) in the 5.0's through to the latest and greatest 6.1's with the same happening with each and any version I would try.

I can only figure that it *must* be something to do with that version of the 'current' Slackware iso that I installed. Surely it can't be VBox when every 'error' message I get is the same for every version of it I tried. I'm just gonna bite the bullet and try a different 'current' Slackware full install iso, I mean I am just trying to help with the final testing of Slackware and others are getting this VBox running in other versions of the 'current', so I guess I need to try and keep up and try the newer stuff too to see if it's VBox, Slackware, or just some really obviously stupid thing I'm doing, or not doing, heh. Yeah, I bitch about the time put into building programs I want to use in it, but it's just dumb and giving me a little venting room is all...I am disabled and probably close to 85% of my day is stuck in front of the computer trying to keep my mind occupied so that I don't go nuts (after 21 years of this though I probably already am and just don't know it and no one will tell me! lol).

Just a question about installing a 'newer' version of 'current'...would it make any difference to *NOT* format the partition I have as /home, but format the others (namely / (root)) and it be okay for testing of the VBox install(s)?

And again, thanks a million for sticking with me and trying to help get this figured out. I hope I don't get you guys mad that I want to try a different 'current' instead of keeping up with this version...unless you guys think of other things I should try first that may be of importance to the testing of the Slackware beta's.

Ok, all good!

I have only seen 1 or 2 segmentation faults, running VirtualBox. Both times due to trying a testrelease for 5.11.x kernel (eventually it got sorted).

I as well made my installations of current this way, using the latest current install ISO kindly provided by AlienBOB.

Question: Do you keep the installation up-to-date as well? (slackpkg update, slackpkg install-new, slackpkg upgrade-all)

See question above.

All good that, testing of current sure is one good thing to do to keep mind occupied. And one learn a few new things along the way

Even if I'm not fully disabled my self, I do have limitations to what I can and can't do. So same thing here, I spend a lot of time in front of a computer.

Reinstallation is an option, true. And leaving /home as is and not format it, leaves you with your files intact. Documents etc...
The only thing to do once done with the reinstallation would be to make sure it is up-to-date and dependencies being installed again.

I can only speak for my self here, but making me go mad because of something like this? That is the last thing you have to worry about. We've all been down this
route, asking for help with Linux. In my case, I ask for info/help almost every day.

So ask for help as much as you like!

As for trying something first... Make sure your current installation is up-to-date. Go the reinstall route if that should fail.

1 members found this post helpful.

I don't use slackpkg or any of those things...way too confusing for me and I always worry that they're adding in things I don't see or am giving 'permission' to install. I don't mean that the program is being sneaky or doing wrong or bad things, I mean I just kind of prefer to 'install' stuff by hand, so I *know* it got installed and I *know* it got such-and-such dependency built and installed first, etc. It's much slower, I'm absolutely positive, but any 'updates' my system needs I've always waited to be told about in the Slackware e-mails, like I get for the vulnerability updates to install also, or kernel.

I guess though, I could try that slackpkg here, on this setup before I wipe it and start fresh with a newer version of 'current' and see what happens and if anything changed to make it so VBox installs. Give me a little while to install it and to figure out how to use it just enough to try the update thing or maybe the upgrade all thing (just writing that out gives me the willies! lol)...it's like an Ubuntu monster turning into a bacteria and infecting Slackware, heh heh.

I'll holler if something happens, or if it doesn't work as hoped. Meh...I just remembered, now I have to swap the video card again into the new system and all the USB cables and such, lol.