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.
When trying to run VirtualBox 6.1.21 installed on Slackware64-current running Linux 5.11.16, I get a segfault ...
Code:
kernel: UINetworkReplyP[5716]: segfault at 10 ip 00007f8f9407f0c2 sp 00007f8f8cff1850 error 4 in libnm.so.0.1.0[7f8f94046000+a2000]
Has anyone experienced anything like this. I have done some reading and some people suggest removing NetworkManager, but I want to avoid that.
I have previously had VirtualBox 6.1.18 working using a SlackBuild from ponce's repository, but I was hoping this manner of installation might make periodic kernel upgrades easier to manage (I am not sure if this is a well-founded idea).
Distribution: Slackware 15.0 x64, Slackware Live 15.0 x64
Posts: 618
Rep:
I can't get Virtualbox to start without crashing within 3 seconds on my stock kernel (I think it's 5.10.32) in the 4/27 current iso (full) install. I've even done the installation of *dozens* of the different versions of Virtualbox, from the 5.0.40 in the SlackBuilds for 14.2 to the latest and greatest 6.1.22-x.
Building them via the SlackBuild from SlackBuilds.org keeps giving a 'sysvers' error and a vdrvbox (or something like that) error.
If I use the '.run' download file from Virtualbox, they all install fine except for the 5.0 series, but they also all crash just two or three seconds after installing them.
Installed in stable with the 4.4.240 kernel. Guest running -current with the 5.10.31 kernel and GuestAdditions. Seems to do what it's supposed to do except when i run a script from a shared folder I get this message
My workaround is using /etc/rc.d/rc.local to rsync the contents of the shared directory to a non shared directory and run the script from non shared directory a bit of a nuisance, but the scripts then work. Strange.
I did report it to our friends at oracle, but it might have got lost with everything else that was going on
Before I report it again I shall test with -current host and -current guest.
Cheers for now
Without further prompting our friends at Oracle have fixed the problem of running scripts from a shared folder. Fixed in VBoxGuestAdditions_6.1.22.iso
I can't get Virtualbox to start without crashing within 3 seconds on my stock kernel (I think it's 5.10.32) in the 4/27 current iso (full) install. I've even done the installation of *dozens* of the different versions of Virtualbox, from the 5.0.40 in the SlackBuilds for 14.2 to the latest and greatest 6.1.22-x.
Building them via the SlackBuild from SlackBuilds.org keeps giving a 'sysvers' error and a vdrvbox (or something like that) error.
If I use the '.run' download file from Virtualbox, they all install fine except for the 5.0 series, but they also all crash just two or three seconds after installing them.
Is there anything in the log files that can help you? No error messages?
/var/log/vbox-install.log | vbox-setup.log
or other log file?
Distribution: Slackware 15.0 x64, Slackware Live 15.0 x64
Posts: 618
Rep:
Quote:
Originally Posted by MDKDIO
Is there anything in the log files that can help you? No error messages?
/var/log/vbox-install.log | vbox-setup.log
or other log file?
I have them, but I have absolutely no idea what I'm looking at or what any of it means. The smallest of them is 45.6Kb, so quite large, for someone like me who has no programming skills, look at and try to figure out what's going wrong, heh. What's more, I don't know who I should show it to...here, on the Slackware forums, or hand it over to the Virtualbox folks. I'm apparently so easily confused, lol.
I can't get Virtualbox to start without crashing within 3 seconds on my stock kernel (I think it's 5.10.32) in the 4/27 current iso (full) install. I've even done the installation of *dozens* of the different versions of Virtualbox, from the 5.0.40 in the SlackBuilds for 14.2 to the latest and greatest 6.1.22-x.
Building them via the SlackBuild from SlackBuilds.org keeps giving a 'sysvers' error and a vdrvbox (or something like that) error.
If I use the '.run' download file from Virtualbox, they all install fine except for the 5.0 series, but they also all crash just two or three seconds after installing them.
What crashes within 3 seconds. The host or the guests?
I'd stick with the files obtained directly from Oracle and install them as per their instructions. As you've been doing a lot of testing I suggest you try and uninstall as much of your existing Virtualbox software as possible. Might even need a restart of your machine
I've installed VirtualBox using VirtualBox-6.1.22-144080-Linux_amd64.run on my host. I see it installed in /opt. My host is Slackware stable (14.2) with the 4.4.240 kernel.
I've installed on each of my guest VBoxGuestAdditions_6.1.22.iso. I see it installed in /opt. The guests are Slackware Current with the 5.10.31 kernel.
The Virtualbox hosts starts cleanly and is stable.
Each of the Virtualbox guests start cleanly and are stable.
I have them, but I have absolutely no idea what I'm looking at or what any of it means. The smallest of them is 45.6Kb, so quite large, for someone like me who has no programming skills, look at and try to figure out what's going wrong, heh. What's more, I don't know who I should show it to...here, on the Slackware forums, or hand it over to the Virtualbox folks. I'm apparently so easily confused, lol.
One thing I notice, is the size of the smallest log file being that big,
Mine are like:
vbox-install.log = 384 bytes
vbox-setup.log = 102 bytes
I have to admit that these .log files doesn't show much of info, and I should've investigated it a bit more. Sorry about that!
Correct log files are located here:
/home/username/.config/VirtualBox/
Latest being named VBoxSVC.log (you'll see by the time/date it's been created)
See if that .log file contains any useful information (or any of the other files found in that directory)
One more thing, did you add a group before you installed VirtualBox?
As per instructions says:
"You have to create a vboxusers group, e.g. "groupadd -g 215 vboxusers"
and make your user a member of that group."
If that is of no help, try what aikempshall suggested, and start over again.
Distribution: Slackware 15.0 x64, Slackware Live 15.0 x64
Posts: 618
Rep:
Quote:
Originally Posted by aikempshall
What crashes within 3 seconds. The host or the guests?
I imagine it's the 'host', since it doesn't stay up long enough for me to use it or do anything with it after just installing it (it being Virtualbox).
Quote:
Originally Posted by aikempshall
I'd stick with the files obtained directly from Oracle and install them as per their instructions. As you've been doing a lot of testing I suggest you try and uninstall as much of your existing Virtualbox software as possible. Might even need a restart of your machine
I found out that if you install a different version of Virtualbox, it has its own script(?) that uninstalls the previous version one was using, at least that's the messaging I would see when trying newer versions trying to find one that would work.
Quote:
Originally Posted by aikempshall
I've installed VirtualBox using VirtualBox-6.1.22-144080-Linux_amd64.run on my host. I see it installed in /opt. My host is Slackware stable (14.2) with the 4.4.240 kernel.
I've installed on each of my guest VBoxGuestAdditions_6.1.22.iso. I see it installed in /opt. The guests are Slackware Current with the 5.10.31 kernel.
The Virtualbox hosts starts cleanly and is stable.
Each of the Virtualbox guests start cleanly and are stable.
I think I mentioned it installed (or I mean *is* installed) on my 14.2 machine and working fine there with a Win7 guest so I can play that rpg using their software window(s). I've used that system to try out other distros of Linux, just to remind myself of what I'm *not* missing, heh, and I kept wanting to try out some BSD's but have been holding out by trying GhostBSD and another that are trying themselves to have 'live' versions on a flashdrive, as AlienBob has done with our beloved Slackware (which, I keep a flashdrive of in my pocket at all times for myself and to show others about Slackware if they're interested enough to want to see Linux at all, heh).
Distribution: Slackware 15.0 x64, Slackware Live 15.0 x64
Posts: 618
Rep:
Quote:
Originally Posted by MDKDIO
One thing I notice, is the size of the smallest log file being that big,
Mine are like:
vbox-install.log = 384 bytes
vbox-setup.log = 102 bytes
I have to admit that these .log files doesn't show much of info, and I should've investigated it a bit more. Sorry about that!
Correct log files are located here:
/home/username/.config/VirtualBox/
Latest being named VBoxSVC.log (you'll see by the time/date it's been created)
See if that .log file contains any useful information (or any of the other files found in that directory)
One more thing, did you add a group before you installed VirtualBox?
As per instructions says:
"You have to create a vboxusers group, e.g. "groupadd -g 215 vboxusers"
and make your user a member of that group."
If that is of no help, try what aikempshall suggested, and start over again.
I'll look into those. Thank you.
I read that about adding the group and becoming a member of it, but I presumed that meant *after* I'd installed Virtualbox. Let me test that out and I'll get back if it changed anything. Another thanks for another suggestion.
Distribution: Slackware 15.0 x64, Slackware Live 15.0 x64
Posts: 618
Rep:
Well, it seems those ideas didn't work either, unfortunately. I tried starting VirtualBox up as user and root and get the same message for both:
Code:
(process:20547): GLib-GObject-WARNING **: 08:48:59.901: cannot register existing type 'NMAgentManagerError'
(process:20547): GLib-CRITICAL **: 08:48:59.901: g_once_init_leave: assertion 'result != 0' failed
(process:20547): GLib-GObject-WARNING **: 08:48:59.901: cannot retrieve class for invalid (unclassed) type '<invalid>'
Segmentation fault
Here's what I found in the /home/me/.config/VirtualBox VBoxSVC.log, these are the only lines that had 'errors', everything before these lines looked fine and dandy (this is the 2.3Kb file, heh):
Code:
00:00:00.109012 nspr-2 SUPR0QueryVTCaps -> VERR_SVM_DISABLED
00:00:00.109122 nspr-2 VD: VDInit finished with VINF_SUCCESS
00:00:00.109431 nspr-2 VirtualBox: object created
00:00:06.539442 main VirtualBox: object deletion starts
00:00:06.539677 main HostDnsMonitor: shutting down ...
00:00:06.541369 main HostDnsMonitor: shut down
00:00:06.610828 Watcher ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={d0a0163f-e254-4e5b-a1f2-011cf991c38d} aComponent={VirtualBoxWrap} aText={The object is not ready}, preserve=false aResultDetail=0
00:00:11.541460 main {00007f7b64016330} HostPowerServiceLinux::~HostPowerServiceLinux: RTThreadWait() for 5000 ms failed with VERR_TIMEOUT
00:00:11.541738 main VirtualBox: object deleted
As I said, I have no idea what that all means and it might as well be the language of Martians or something. This is really getting to be a bummer.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
