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.
Distribution: Slackware64-current with "True Multilib."
Posts: 8,402
Original Poster
Rep:
Quote:
Originally Posted by Daedra
Are you sure that the development snapshot 142300 is new? That's what I am running right now and I downloaded that weeks ago? Thanks for the heads up on the test builds though.
I didn't say the "development snapshot" was new.
I've been using it since it was release, as previously mentioned in post #10 in this thread.
Last edited by cwizardone; 02-09-2021 at 03:01 PM.
Well I don't know what I am doing wrong, I am not doing anything different; but I am still getting kernel panics in --Current installed with guest additions in Virtualbox.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 799
Rep:
Quote:
Originally Posted by Jeebizz
Well I don't know what I am doing wrong, I am not doing anything different; but I am still getting kernel panics in --Current installed with guest additions in Virtualbox.
I plan to try this solution sometime today (if I have time) https://www.virtualbox.org/ticket/20163
basically disabling
CONFIG_DEBUG_SPINLOCK
may help.
I am no very hopeful though as (if I remember correctly) I disabled all debugging in the kernel, but I am going to check.
I plan to try this solution sometime today (if I have time) https://www.virtualbox.org/ticket/20163
basically disabling
CONFIG_DEBUG_SPINLOCK
may help.
I am no very hopeful though as (if I remember correctly) I disabled all debugging in the kernel, but I am going to check.
update:
as suspected I did not have CONFIG_DEBUG_SPINLOCK in the config and vbox client with kernel 5.10.15 still crashing
booting host with kernel 5.4.96 and client with 5.10.15 did not help either.
so at this point client must run kernel less than 5.10.x
Well I don't know what I am doing wrong, I am not doing anything different; but I am still getting kernel panics in --Current installed with guest additions in Virtualbox.
You're not doing anything wrong. I've decided not to install GuestAddditions. Whatever I did GuestAdditions messed things up big time.
The following, at the moment, seems to work for me
On the host running 14.2 with Kernel 4.4.240 and VirtualBox 5.0.40
On the guest running Current with Kernel 5.10.14 and NO VirtualBox packages whatsoever. I've settled on the VirtualBox settings for display of 64MB and no 3D, anything more seems to cause problems i.e. something akin to buffering
With this setup I get screen resising and shared folders as these are all NOW supplied by the default kernel. All seem to work without issue.
I can't get VirtualBox's bi-directional copy/paste or drag and drop to work, I suspect these are supplied by GuestAdditions. I thought this was a big deal, but with shared folders working I can work around it.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 799
Rep:
Quote:
Originally Posted by aikempshall
You're not doing anything wrong. I've decided not to install GuestAddditions. Whatever I did GuestAdditions messed things up big time.
The following, at the moment, seems to work for me
On the host running 14.2 with Kernel 4.4.240 and VirtualBox 5.0.40
On the guest running Current with Kernel 5.10.14 and NO VirtualBox packages whatsoever. I've settled on the VirtualBox settings for display of 64MB and no 3D, anything more seems to cause problems i.e. something akin to buffering
With this setup I get screen resising and shared folders as these are all NOW supplied by the default kernel. All seem to work without issue.
I can't get VirtualBox's bi-directional copy/paste or drag and drop to work, I suspect these are supplied by GuestAdditions. I thought this was a big deal, but with shared folders working I can work around it.
I can install VirtualBox client with kernel 5.10.x and this works fine. However after installing Vbox client additions kernels 5.10.x crash with the error messages as posted by Jeebizz.
In fact vboxvideo and vboxfs are provided by kernel for pretty long time.
The only issue is copy/paste between client/host and client/client.
Copy/paste option is restored when client runs 5.4.x series (you can run 5.9.x also but it is EOL so no possible security updates)
Distribution: Slackware64-current with "True Multilib."
Posts: 8,402
Original Poster
Rep:
A new test build has been posted at, https://www.virtualbox.org/wiki/Testbuilds
Version Linux 64-bit, 6.1.x revision 142777 and its companion extension pack work as they should with -current as both user and root.
*sigh* Same here as above poster. Did a fresh install on both my desktop and laptop with 15 Alpha1 and now 142777 seg faults as both user and root. and 142300 launches but I can't actually create any virtual machines, the next and back buttons are greyed out. SMH
Distribution: Slackware64-current with "True Multilib."
Posts: 8,402
Original Poster
Rep:
Quote:
Originally Posted by Daedra
*sigh* Same here as above poster. Did a fresh install on both my desktop and laptop with 15 Alpha1 and now 142777 seg faults as both user and root. and 142300 launches but I can't actually create any virtual machines, the next and back buttons are greyed out. SMH
Ditto. Well, almost.
Did a fresh install earlier today and once done, 142777 would not run as root, but issuing the following command, as root,
Quote:
/usr/bin/vboxmanage extpack install --replace ~/Oracle_VM_VirtualBox_Extension-the-version you want to install
I was able to get it to run as user.
Sorry, I've forgotten the name of the user who was kind enough to provide that information.
Last edited by cwizardone; 02-16-2021 at 05:53 PM.
Ditto. Well, almost.
Did a fresh install earlier today and once done, 142777 would not run as root, but issuing the following command, as root,
I was able to get it to run as user.
Sorry, I've forgotten the name of the user who was kind enough to provide that information.
After getting the extension pack installed it runs as root but not as user for me. I really hope Oracle gets this straightened out soon, this is getting annoying.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.