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.
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 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.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 799
Rep:
Quote:
Originally Posted by Daedra
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.
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
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 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:
-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.
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:
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.
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.
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.
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?
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.
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.