LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 01-24-2021, 11:05 AM   #31
Daedra
Senior Member
 
Registered: Dec 2005
Location: Springfield, MO
Distribution: Slackware64-15.0
Posts: 2,738

Rep: Reputation: 1401Reputation: 1401Reputation: 1401Reputation: 1401Reputation: 1401Reputation: 1401Reputation: 1401Reputation: 1401Reputation: 1401Reputation: 1401

I am also noticing that I can only get sound to play in both my Linux and Windows guests if I set the Host Audio Driver to Alsa instead of PulseAudio. Is anyone else having this issue?
 
1 members found this post helpful.
Old 01-24-2021, 11:06 AM   #32
Jeebizz
Senior Member
 
Registered: May 2004
Distribution: Slackware15.0 64-Bit Desktop, Debian 11 non-free Toshiba Satellite Notebook
Posts: 4,202

Rep: Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387
Quote:
Originally Posted by bitfuzzy View Post
The kernel panic is on the guest? or host??
Guest.
 
1 members found this post helpful.
Old 01-24-2021, 04:09 PM   #33
1337_powerslacker
Member
 
Registered: Nov 2009
Location: Kansas, USA
Distribution: Slackware64-15.0
Posts: 862
Blog Entries: 9

Rep: Reputation: 592Reputation: 592Reputation: 592Reputation: 592Reputation: 592Reputation: 592
I was in the middle of the mass upgrade, and all of a sudden I was getting file corruption errors. I decided to safest way to proceed was to do a clean install. Went swimmingly. Now all is well. Super-performant and rock-solid, as I would expect from Slackware.

Rock on!
 
1 members found this post helpful.
Old 01-24-2021, 08:44 PM   #34
Aeterna
Senior Member
 
Registered: Aug 2017
Location: Terra Mater
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,038

Rep: Reputation: Disabled
Quote:
Originally Posted by Daedra View Post
I am also noticing that I can only get sound to play in both my Linux and Windows guests if I set the Host Audio Driver to Alsa instead of PulseAudio. Is anyone else having this issue?
I have Gentoo, antiX, Slackware and Artix running only with Alsa. In contrast FreeBSD and OpenBSD run with PulseAudio.
 
3 members found this post helpful.
Old 01-25-2021, 03:32 AM   #35
aikempshall
Member
 
Registered: Nov 2003
Location: Bristol, Britain
Distribution: Slackware
Posts: 902

Rep: Reputation: 153Reputation: 153
Ever so briefly this morning I fell across a web page that mentioned that vboxsf support is new to the kernel starting with the 5.10 series.

Retraced my browsing history, but couldn't find that reference again.

Wondering if I need to use VBoxGuestAdditions do I need to blacklist the Linux kernel modules vboxvideo, vboxguest and vboxsf?
 
1 members found this post helpful.
Old 01-25-2021, 07:24 AM   #36
aikempshall
Member
 
Registered: Nov 2003
Location: Bristol, Britain
Distribution: Slackware
Posts: 902

Rep: Reputation: 153Reputation: 153
I've got a fully update kubuntu 20.04 vboxguest, it was working perfectly well screen resizing, shared folders and bi-directional copy/paste. The host is Slackware-14.2 running VirtualBox 5.0.40 r115130

I've taken a clone of it and upgraded it to use the 5.10 kernel following the instructions here https://sypalo.com/how-to-upgrade-ubuntu

I removed the VBoxGuestAdditions-6.0.22 and installed VBoxGuestAdditions-6.1.18.

Rebooted the guest and it fails in similar fashion to how Slackware-current fails as reported in this thread.

I've attached a screenshot with the point of failure.
Attached Thumbnails
Click image for larger version

Name:	SegmentationFault.png
Views:	47
Size:	16.6 KB
ID:	35363  
 
1 members found this post helpful.
Old 01-25-2021, 08:38 PM   #37
Jeebizz
Senior Member
 
Registered: May 2004
Distribution: Slackware15.0 64-Bit Desktop, Debian 11 non-free Toshiba Satellite Notebook
Posts: 4,202

Rep: Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387
Well I think until Oracle addresses this issue, there is nothing we can really do other than suggest not installing guest additions. I would have to theorize that this is not just affecting Slackware as a guest, but any other Linux distro running the 5.10.x kernel. *shrug>
 
Old 01-25-2021, 09:34 PM   #38
Jeebizz
Senior Member
 
Registered: May 2004
Distribution: Slackware15.0 64-Bit Desktop, Debian 11 non-free Toshiba Satellite Notebook
Posts: 4,202

Rep: Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387
Quote:
Originally Posted by Jeebizz View Post
Well I think until Oracle addresses this issue, there is nothing we can really do other than suggest not installing guest additions. I would have to theorize that this is not just affecting Slackware as a guest, but any other Linux distro running the 5.10.x kernel. *shrug>
Well I don't know what is going on to be honest. I booted just fine after installing guest additions on 5.10.10 - so I thought maybe the issue was resolved - as soon as I logged as root I got a weird kernel panic (stupid me didn't screenshot). So I rebooted again, I got a kernel panic - so I rebooted yet again, and this time I was able to boot with another weird error, and logged into as root with no error, so SOMETHING is up still... What I don't know but everything seems suspect to me:


Click image for larger version

Name:	VirtualBox_Slackware --Current_25_01_2021_21_37_25.png
Views:	32
Size:	31.8 KB
ID:	35365Click image for larger version

Name:	VirtualBox_Slackware --Current_21_01_2021_23_04_40.png
Views:	33
Size:	40.0 KB
ID:	35366


-edit

So basically I don't know what to expect each time I boot the VM, I could either boot into it just fine - or get a kernel panic for some random reason; this is even more weird now.

Last edited by Jeebizz; 01-25-2021 at 09:43 PM.
 
Old 01-25-2021, 09:51 PM   #39
Jeebizz
Senior Member
 
Registered: May 2004
Distribution: Slackware15.0 64-Bit Desktop, Debian 11 non-free Toshiba Satellite Notebook
Posts: 4,202

Rep: Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387
Ok --- SO; I rebooted a few times and this confirms my theory - sometimes the VM will get all the way to a login prompt, I tried to get into root and got another kernel panic - so really this is all over the place now. So here are some incoming threads with screenshots:


Click image for larger version

Name:	VirtualBox_Slackware --Current_25_01_2021_21_38_46.png
Views:	35
Size:	32.6 KB
ID:	35371Click image for larger version

Name:	VirtualBox_Slackware --Current_25_01_2021_21_41_31.png
Views:	25
Size:	40.6 KB
ID:	35370[Click image for larger version

Name:	VirtualBox_Slackware --Current_25_01_2021_21_43_58.png
Views:	26
Size:	38.1 KB
ID:	35369Click image for larger version

Name:	VirtualBox_Slackware --Current_25_01_2021_21_44_26.png
Views:	23
Size:	36.8 KB
ID:	35368Click image for larger version

Name:	VirtualBox_Slackware --Current_25_01_2021_21_44_57.png
Views:	22
Size:	38.4 KB
ID:	35367
 
Old 01-25-2021, 09:56 PM   #40
Jeebizz
Senior Member
 
Registered: May 2004
Distribution: Slackware15.0 64-Bit Desktop, Debian 11 non-free Toshiba Satellite Notebook
Posts: 4,202

Rep: Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387
And then the next time I rebooted:

Click image for larger version

Name:	VirtualBox_Slackware --Current_25_01_2021_21_38_08.png
Views:	19
Size:	38.1 KB
ID:	35375Click image for larger version

Name:	VirtualBox_Slackware --Current_25_01_2021_21_37_25.png
Views:	21
Size:	31.8 KB
ID:	35374Click image for larger version

Name:	VirtualBox_Slackware --Current_21_01_2021_23_06_50.png
Views:	29
Size:	40.0 KB
ID:	35373Click image for larger version

Name:	VirtualBox_Slackware --Current_21_01_2021_23_04_40.png
Views:	24
Size:	40.0 KB
ID:	35372

I actually made it to the login prompt - logged into root and then kernel panic again. SO... Yea I don't know how useful all this is - but this is what I have seen with 5.10.10 and guest additions for VirtualBox 6.1.18 r142142. Sometimes you can boot all the way, sometimes you won't - and sometimes you will still boot even after the kernel panic. It makes no sense.

-edit

Forgot to mention this is --Current up to today's updates (changelog) too.

Last edited by Jeebizz; 01-25-2021 at 10:07 PM.
 
1 members found this post helpful.
Old 01-26-2021, 07:29 AM   #41
cwizardone
LQ Veteran
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,199

Original Poster
Rep: Reputation: 7398Reputation: 7398Reputation: 7398Reputation: 7398Reputation: 7398Reputation: 7398Reputation: 7398Reputation: 7398Reputation: 7398Reputation: 7398Reputation: 7398
FWIW, as I said in post #10,
Quote:
Development revision 142300 and Extension Pack development revision 142298
WILL run both as root and as user.

https://www.virtualbox.org/wiki/Testbuilds
Now, I only use it to run winXp-sp3, so I can run the HP drivers for my flatbed scanner, but for that purpose the VirtualBox versions mentioned above are working perfectly.
 
Old 01-28-2021, 06:58 AM   #42
linuxxer
Member
 
Registered: Apr 2011
Location: I have my own planet
Distribution: SlackwareŽ
Posts: 257

Rep: Reputation: Disabled
Quote:
Originally Posted by bitfuzzy View Post
Slackware -Current64 - Kernel 5.4.84 - VirtualBox 6.1.16 r140961
As Root w/ root added to vboxusers group
I was also facing the same issue (with same version of Linux kernel and VirtualBox). This issue was because of NetworkManager library.

I uninstalled the NetworkManager and then run VirtualBox. After that I installed the NetworkManager.
And disbled Preferences -> Update -> Check for updates option in VirtualBox. After that I had not facing issue while running the VirtualBox. Now I am running both NetworkManager and VirtualBox together.

I don't know what was the exact issue. But What I understand is, Everyday first time when I start VirtualBox, it was checking for update and get crash because of that library. I don't know this is right or wrong. But it is working for me.
 
1 members found this post helpful.
Old 01-28-2021, 09:32 AM   #43
chrisretusn
Senior Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 3,007

Rep: Reputation: 1568Reputation: 1568Reputation: 1568Reputation: 1568Reputation: 1568Reputation: 1568Reputation: 1568Reputation: 1568Reputation: 1568Reputation: 1568Reputation: 1568
This looks to only be an issues when starting, using virtualbox from a console session with -current as the host. This is not an issue (as far as I can see from my own testing) when using virtualbox as a user. Did I get that right?
 
Old 01-28-2021, 10:38 AM   #44
maltux
LQ Newbie
 
Registered: Jul 2015
Location: Williamsville, NY
Distribution: Slackware64-current, Debian, Fedora
Posts: 26

Rep: Reputation: 12
Thumbs up Thank you

Quote:
Originally Posted by ctrlaltca View Post
This command should fix Virtualbox crashing on startup:
Code:
VBoxManage setextradata global GUI/UpdateDate never
At startup, Virtualbox checks for updates; disabling this check avoids the crash. As far as i understand this is caused by Virtualbox bundling its own version of the Qt5 libraries.
Thank you - this worked for me..
 
1 members found this post helpful.
Old 01-28-2021, 10:57 AM   #45
Jeebizz
Senior Member
 
Registered: May 2004
Distribution: Slackware15.0 64-Bit Desktop, Debian 11 non-free Toshiba Satellite Notebook
Posts: 4,202

Rep: Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387Reputation: 1387
Quote:
Originally Posted by chrisretusn View Post
This looks to only be an issues when starting, using virtualbox from a console session with -current as the host. This is not an issue (as far as I can see from my own testing) when using virtualbox as a user. Did I get that right?
My scenario, the hose is 14.2 64-Bit, and --Current is the guest. That is where I am experiencing these random kernel panics in --Current as the guest.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] virtualbox is installed along with virtualbox-dkms and virtualbox-ext-pack and linux-headers-generic, but error for no /dev/vboxdrv Astral Axiom Linux - Software 2 03-04-2019 08:09 PM
Issues activating virtualbox within my linux fedora 25 virtualbox on my windows device. QuantumChaos Linux - Virtualization and Cloud 5 02-21-2017 08:31 AM
Move Slackware guest from a Slackware hosted Virtualbox to Windows hosted Virtualbox? damgar Slackware 1 08-07-2012 11:28 PM
virtualbox or virtualbox ose manuleka Linux - Software 2 06-11-2009 02:56 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 06:01 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration