Since a few days Virtualbox 7.2.22 does not start guests at all, both windows and linux guests. The startup screen of the host stays black and mouse and keyboard do not work. (ctrl-home does work, but ending the host does not). With timeshift I could revert to a situation where Virtualbox works normally. Pacman -Syu shows the list of packages with upgrades. Virtualbox (ofcourse) fails again when these upgrades are installed. I have compared that list with Virtualbox dependencies. I would expect that one or more upgrades are needed by Virtualbox, but none do (I think).
This is on Manjaro KDE Unstable, KDE Plasma Version: 6.8.1, KDE Frameworks Version: 6.31.0, Qt Version: 6.12.0 Kernel Version: 6.18.58-1-MANJARO (64-bit) Graphics Platform: Wayland. The vbox log file does not show anything unusual (although I am not sure). Guest Addition 7.2.22 is installed.
:: Synchronizing package databases...
core is up to date
extra is up to date
multilib is up to date
:: Starting full system upgrade...
warning: rsync: ignoring package upgrade (3.4.4-1 => 3.5.1-3)
resolving dependencies...
looking for conflicting packages...
Packages (38) alsa-card-profiles-1:1.6.10-1 brotli-1.2.1-1 ca-certificates-mozilla-3.132-1 fwupd-2.1.9-1 glib-networking-1:2.90.1-1
glycin-2.2.4-1 gst-plugin-pipewire-1:1.6.10-1 kwin-6.8.1-2 lib32-brotli-1.2.1-1 lib32-libldap-2.7.2-1
lib32-libpipewire-1:1.6.10-1 lib32-librsvg-2:2.63.4-1 lib32-pipewire-1:1.6.10-1 lib32-pipewire-jack-1:1.6.10-1 libldap-2.7.2-2
libphonenumber-1:9.0.42-1 libpipewire-1:1.6.10-1 librsvg-2:2.63.4-1 libuv-1.53.0-1 mhwd-nvidia-615.78.08-2 mpd-0.24.17-1
nss-3.132-1 obsidian-1.14.5-1 openh264-2.7.0-1 perl-uri-5.40-1 pipewire-1:1.6.10-1 pipewire-alsa-1:1.6.10-1
pipewire-audio-1:1.6.10-1 pipewire-jack-1:1.6.10-1 pipewire-pulse-1:1.6.10-1 python-brotli-1.2.1-1 python-dnspython-1:2.9.0-1
python-googleapis-common-protos-1.76.0-1 python-importlib-metadata-9.1.0-1 python-pycparser-3.12-1 python-pycryptodome-4.2.0-1
python-reportlab-5.1.0-1 webkit2gtk-4.1-2.54.2-1
Addition to first post: I have uninstalled Guest Additions, upgraded, restarted, retested Virtualbox with the guest without Guest Additions: A small change: desktop was started, visible and then guest froze.
I have the same problem, too. Would be very interested in any solution
Mod edit:-
@simonriley – Firstly, welcome to the Manjaro forum.
However, please note that so-called “me too” posts are not generally not encouraged. The golden rule is that if you have nothing useful to say, say nothing; or, at the barest minimum, add some useful context that might contribute toward a solution.
Forum Rules are designed to help everyone maximise their forum experience, so please take the time to read through them, along with other helpful guidelines discovered along the way.
It is good to know I am not the only one experiencing this (although we don’t know whether your ‘this’ is my ‘this’). I have been using VBox for several years now, and once in a while things like this happen. On the Internet I can not find similar posts. My current approach to this: wait-and-see, not update anything (no partial updates) until I see updates that (I think) maybe related to this, and try again.
Well if you have 7.22 installed i guess you are on unstable. I noticed the same behaviour on my unstable host with freezing vm’s.
My suggestion would be to install a fresh manjaro on stable branch with 7.2.16-1 virtualbox.
No problems with that version and all my vm’s are working ok
So keep your main systems on stable and experiment in vm’s imho
Pretty sure it was the virtualbox forum about a work around by disabling audio in virtualbox settings. All of my vm’s are now working with 7.2.22 now. I do not use audio in virtualbox anyway so I will not miss it.
A couple of suggestions: try starting VirtualBox from a Terminal, so hopefully you get to see error messages when you try to launch a VM. (Post those here, too).
Is it possible for you to show some logging of a “freezing” vm ?
There’s a Logs directory in every vm you created.
If you put a tail on that file when starting the vm perhaps the output will show some usefull information.
I found another solution that keeps the audio active. For me, it helped to change the following settings in VirtualBox under the audio configuration for each host:
Host-driver: PulseAudio
Controller: Intel HD
Although I also have—or rather, had—this problem, I am not the person who started this thread. Therefore, I am not sure whether providing a log from my side would be appropriate.
This thread is becoming a bit confusing, as mentioned by ManLuxer. I have tagged Straycat’s post as the solution / workaround yesterday. I would suggest to open a new thread if you’d like to discuss the subject further.
see: [Bug]: `alsa`: Freezes when playing audio · Issue #929 · VirtualBox/virtualbox · GitHub
The fix is created in Arch, i.e. the packaging of VBox. Only Arch -related distro’s had this issue (I think).