Today I updated the 4 machines affected by the issue. (2) Dell desktops, (1) ASUS desktop, (1) Lenovo desktop. The Lenovo and the ASUS have aftermarket graphics cards but nothing spectacular, just enough for dual monitors.
TEST 1: Kernel 5.18.3
VirtualBox Windows 7 Guests seem to run fine at first (they did not crash in the first minute or less, like previously).
Windows 7 Guest on the Lenovo crashed after about 30 minutes.
Windows 7 Guest on the ASUS seemed a bit sluggish compared to before this mess. One piece of software wouldn’t run. Chrome seemed to run fine but I kept seeing the “busy” icon appear next to my mouse.
I didn’t see an issue on the Dell machines but I didn’t play with them for more than 20 minutes.
TEST 2: Kernel 5.4 (yes all the way back to 5.4 because 5.10 didn’t work either)
I decided to go back to 5.4 because I tried it with one of the machines on Monday and left it running overnight. This morning it was still running fine with dozens of tabs open in both Chrome and Firefox, plus a couple of other programs running.
As of 8pm, all 4 computers are running fine with 5.4, none are sluggish, and none have crashed after several hours of testing.
I see Kernel 5.4 is LTS so guess its fine for now. Maybe its the lack of sleep over the past 48 hours, but I just find this whole thing super frustrating.
@linux-aarhus yes, I’ve played with several including qemu and vmware. As we have a dozen or so workstations all running Manjaro with VirtualBox and Windows 7 guests, I really need to keep them all the same.
Today I’m waiting to hear if there are any complaints from people using the kernel 5.4 machines, and if all looks good, then I will be installing updates and reverting the other machines from 5.15 to 5.4. The machines currently using 5.15 are working fine with VirtualBox because they’re still using the previous linux515 headers.
I’d love to hear this is fixed soon. I’m one of those people who is always telling people they can switch to Manjaro as a desktop, and I still believe this is true! The support in this forum is always great.
linux515 is preferable but if not achievable and lts is - supposedly better in the long run - maintenance wise.
I just didn’t connect my problems to the kernel in use and in hindsight I see now why - my windows began abruptly closing - my visual studio 2022 stopped working - I admit I blamed Windows for the instability.
So I did a test yesterday on a clean install - and there is definately something off with linux515 and virtualbox - on kernel 5.18 no issues but if I reboot into 5.15 - windows works but visualstudio do not.
Perhaps it is caused by may habit of using dkms for host modules - instead of using the prebuilt modules
Update: Disclaimer: My testing is subjective and inconclusive - but they point in direction of the previous assesment that 5.10 and 5.15 are flaky. Systematic reboot over the course of approx. 60 minutes - using prebuilt modules instead of dkms.
Windows 10 2016ltsb
Runing a debug session on a API hosted on IIS Express.
Posting requests against the API using postman running on the host
$ uname -rsv
Linux 5.18.4-1-MANJARO #1 SMP PREEMPT_DYNAMIC Wed Jun 15 07:05:22 UTC 2022
5.18 - appears stable
$ uname -rsv
Linux 5.15.47-1-MANJARO #1 SMP PREEMPT Wed Jun 15 07:06:46 UTC 2022
5:15 - flaky - may work and after reboot it does not
$ uname -rsv
Linux 5.10.122-1-MANJARO #1 SMP PREEMPT Wed Jun 15 07:06:00 UTC 2022
5.10 - worked for about 10-15 min. then visual studio crashed.
$ uname -rsv
Linux 5.4.198-1-MANJARO #1 SMP PREEMPT Tue Jun 14 16:52:20 UTC 2022
Thanks for the checks. I can also confirm that kernel 5.15 with current updates (date: 2022-06-16) is causing havoc. Testing with manjaro VM in manjaro virtual box Host system. Same issue as others here reported - vm becomes unusable after some minutes, sometimes even on boot
Switching forward to kernel 5.18 in the host system solved the issue for now.
… waiting for a 5.15 fix and will keep on testing as well in the next days.
P.S.: Manjaro VM (KDE, Kernel 5.15, booting via btrfs on a luks encrypted VMdrive) works flawless, I retested installation procedure multiple times. Each Install roundtrip took ~5 minutes. Tested different installer options regarding SWAP, btrfs and encryption during installation.
… this works (tested ~6 combinations) as designed every time … when virtualbox is working correctly
looks like today (2022-06-17) virtualbox-host-modules 6.1.34-17 is available
pamac is just installing it for both of my kernels…
linux515-virtualbox-host-modules (6.1.34-14 → 6.1.34-17)…
… testing …
Test 1: Host (kernel 5.18) rebooted, VM (kernel 5.15) started, updated, rebooted (kernel 5.15 has a new release also…)
Result: working as expected, all fine
… rebooting host to kernel 5.15 to see if this is now fixed …
Virtualbox host rebooted (kernel 5.15.48-1-MANJARO, linux515-virtualbox-host-modules 6.1.34-17), VM started.
Result: No good, KDE in the VM / VirtualBox still breaks down pretty much directly after login.
I’m glad I found this thread. I thought I was going crazy with constant app crashes in a Windows VM in Virtualbox. I am on 5.15.46 ( though I just updated to 5.15.48 but have yet to reboot. I was reading this as I updated ) I have not tried 5.18 though I don’t really plan to. I prefer sticking with LTS. I also have 5.10 installed but had not thought to boot into that. Not 5.4 though
Thanks too for your hints
I only can confirm that upgrading to 5.18.5-1-MANJARO also works smoothly with VB 6.1.34r150636 (HOST)
und windows 10 X64(GUEST)
After trying downgrading 6.1.34 to 6.1.32 with LTS kernel linux515 (OS reboots at random, blue screen) and other possibilties,I tried, as mentionned, also 5.18.5-1-MANJARO (linux518) and did a fresh install
Windows 10 Professionnel
Processeur Intel(R) Core™ i7-5600U CPU @ 2.60GHz 2.59 GHz
VB RAM allocated 5,98 Go
Its frustrating because it seams that LTS isn’t compatible with VB 6.1.34.
Yesterday Kernel 5.15.48-1 did not work for me - same install status as mentioned in my last post. Does it work for you? if yes, could you please show how your result for this shell command looks like?
pamac search virtualbox | grep -i install
looks like … example: for me this looks like:
pamac search virtualbox |grep -i install
linux518-virtualbox-host-modules [Installiert] 6.1.34-8 extra
linux515-virtualbox-host-modules [Installiert] 6.1.34-17 extra
virtualbox-guest-iso [Installiert] 6.1.34-1 community
virtualbox-ext-oracle [Installiert] 6.1.34-1 AUR
virtualbox [Installiert] 6.1.34-4 community
I was of the impression this wasn’t only happening on my computer, since the bug is mentioned on VirtualBox’s forum and I didn’t create this thread. It’s my first time using a distro with rolling updates, I’m not used to stuff breaking when running on a stable branch.