This maybe helpful: VirtualBox - Manjaro
Please not this excerpt from the above link:
Yes.
But after I have deinstalled ‘dkms’ and ‘virtualbox-guest-dkms’ the same situation.
I wasn’t expecting it to make a difference, ‘virtualbox-guest-dkms’ would only break mhwd-kernel.
The ‘virtualbox-guest-dkms’ package is the Arch solution, ‘{kernel}-virtualbox-guest-modules’ is Manjaro’s pre-compiled solution for mhwd-kernel.
Ergo, ‘dkms’ and ‘virtualbox-guest-dkms’ are not necessary.
The problem is ‘linux41-virtualbox-guest-modules’.
What mean mhwd-kernel?
mhwd is the Manjaro Hardware Detection software.
https://wiki.manjaro.org/index.php?title=Manjaro_Hardware_Detection
mhwd-kernel is used to identify, install, and remove kernels and extra modules associated with them.
https://wiki.manjaro.org/index.php?title=Manjaro_Kernels
Hello,
What mean you?
The problem is ‘linux41-virtualbox-guest-modules’.
with regards
Ch. Hanisch
If the issue only appears with the precompiled kernel module for virtualbox in Manjaro/Netrunner Rolling then something might be wrong with them.
Did you tried already removing the precompiled kernel module package linux41-virtualbox-guest-modules and installing the dkms package ? virtualbox-guest-dkms
Does it work with it ?
Neither of the guest-modules packages are going to make a difference if guest additions was downloaded and installed within the appliance from outside the Manjaro repository, doing this will have rendered that installation unusable.
No. dkms and virtualbox-guest-dkms has no effect for this problem; if always linuxXXX-virtualbox-guest-modules are missing.
I think dkms and virtualbox-guest-dkms are not necessary. In Manjaro in a VirtualBox this packages are also not present and it works fine with linuxXXX-virtualbox-guest-modules .
with regards
Ch. Hanisch
We make no changes to the system in regards to Manjaro’s virtualbox implementation.
You might try installing the same kernel series in you appliance that was installed with the Manjaro release that you tried.
The vbox guest module give direct access to the hardware, the kernel itself would need to be compatible with that hardware.
Example: Skylake require a minimum of kernel 4.6 to function without special setup steps: https://wiki.archlinux.org/index.php/intel_graphics#Skylake_support
We tend to ship with the latest kernel available at the time of release on our Netrunner ISO’s.
Manjaro tends to stick with the latest LTS kernels for their official releases.
Which Manjaro release ISO did you use to test in VBox?
The difference between Netrunner Rolling Release (64Bit) and my Manjaro Test is the 32 Bit System on Manjaro.
I have Manjaro installed for example from manjaro-i3-15.09-i686.iso with Kernel 4.1.25-1-MANJARO
In Netrunner I have the same Kernel.
with regards
Ch. Hanisch
Is that the Manjaro KDE edition ISO?
Is the issue on an already installed and updated/modified vbox appliances or on a fresh boot to the ISO image in vbox?
Have you tried the 64 bit version of the Manjaro ISO (same release) yet?
The comparison you’ve made would be the about the same as comparing Ubuntu 15.10 32bit against netrunner 17 64bit.
Not only is it a completely different base system and DE, but a completely different architecture as well.
KDE is heavier in resources than I3, unity, xfce, etc.
Manjaro KDE also doesn’t enable as many of the 3D effects by default as Netrunner does.
What we need is an apples to apples comparison, not an apples to watermelon comparison.
Hello,
I have Netrunner installed from ISO: netrunner-rolling-2016.01-64bit.iso in a VirtualBox.
That was working wery well.
But after updating the system with about 610 packages the system do not work anymore.
Only without GuestAdditions ‘linux44-virtualbox-guest-modules’ the system work now.
That is the situation.
with regards
Ch. Hanisch
Doesn’t help anybody if you repeat the situation over again.
Is there anything in the journalctl logs when you install this module again like a warning or error message that could lead us to the right direction.
OK, can you get to a tty (ctrl +alt + F2) after boot with the linux44-virtualbox-guest-modules package installed?
After installing the fore mentioned package, did you rebuild the initramfs before rebooting?
sudo pacman -S virtualbox-guest-utils linux44-virtualbox-guest-modules
sudo mkinitcpio -p linux44
This could also be the issue: https://wiki.archlinux.org/index.php/VirtualBox#Guest_freezes_after_starting_Xorg
Try disabling the 3d acceleration option in the virtual box appliances settings.
I’ve had to do this for an intel GPU based system before.
Update, it seems there is an issue with Manjaro under virtualbox after all.
https://forum.manjaro.org/t/xorg-is-broken-in-virtualbox-after-the-april-26th-update/876/3
https://forum.manjaro.org/t/xorg-still-broken-in-virtualbox-after-update-2016-05-22-stable/1999/13
The new Manjaro forums are a bit harder for me to use than the old forums, it took me more time to search the issue there.
Yes, that is the solution in [vbox?] lightdm fails · Issue #208 · manjaro/manjaro-tools · GitHub
with
press the hostkey of your virtualbox plus F2
login on the console
sudo nano /etc/X11/xorg.conf.d/90-mhwd.conf
comment out these lines:
#Section “Device”
Identifier “Device0”
Driver “vboxvideo”
#EndSection
save the changes with 'Ctrl'+o and 'Enter' and close with 'Ctrl'+x
Thanks for help!
with regards
Ch. Hanisch