Has anyone had the issue, when they own mac hardware, that when they install sound drivers it causes kernel instability, until you upgrade the kernel beyond the LTS recommended, then when installing VBox, due to OS instability with the headers, you need to downgrade the kernel to LTS, causing sound driver instability?
What distro are you running? Perhaps they also offer the VirtualBox modules as DKMS, theorically working with whatever kernel you are using?
Truth be told the Vbox kernel module rigmarole eventually prompted me to try virt-manager instead.
It does some things different and ends up being a touch less user-friendly, but the learning curve is not too big. Give it a spin, you might like it!
I know GNOME also has a very polished app called “Boxes” that uses the same tech virt-manager does. I haven’t used it myself but it might be nice too.No. I’ve installed all kinds of distributions on computers and giving them away and never seen that problem. I’ve never had to install sound drivers this decade.
Frankly I have no idea what you are talking about.
In my experience there is no relationship between the kernel and audio drivers of a host to that of a virtual machine running on that host, unless you’re doing some funky audio passthrough, but I can’t think of a way to achieve that unless you’re futzing with building your own drivers.
As far as “mac hardware”, I’m assuming that you’re talking about Intel based Apple hardware, since there’s extremely limited support for Apple Silicon (M1 and M2 with incomplete peripheral support through Asahi Linux) and AFAIK, there is no LTS support at all at this time.
honestly understandable, I only talked about the kernel since in order to compile and install the audio drivers I had to use kernel version 16.2, whereas I was using 8.1, and although I know there isn’t LTS, I was using the “ubuntu LTS” distro
Sound driver for Mac? What Mac year is it
2017 intel based, running an ubuntu LTS flavor.
Simple solution, don’t install vbox, it’s garbage anyway.
Headers don’t interact with the kernel, so there’s no stability issue there. I assume what you did was install a mainline kernel in an Ubuntu flavor of something, then needed the headers for the Vbox extensions, but headers aren’t available in packages for mainline kernel versions.
You can build VirtualBox and it’s components, or just the components from source. That means install the packages bits, then download kernel source, and use it to build the extensions, then you can package and install them.
I’ll have to look into this! thank you, I was getting around it by using my 2012 Macbook :D
