You are not logged in.
Host: win8.1, Virtualbox 5.0.20
Guest: Arch x64, latest updates and latest virtualbox-guest-modules-arch. Running fluxbox, VBoxClient is run from .xinitrc. Resolution is set from /etc/X11/xorg.conf.d
Action: running dmesg from a full screen xterm or aterm. Or opening large log files in vi in a full screen xterm or aterm.
Result: virtualbox window "freezes" and stops updating. However the system remains responsive; when I click outside the VM and then in the VM I can manually trigger an update of the screen. But from there it doesn't update again until I trigger the update again. This behavior occurs since about a month; before that there were no problems.
The same happens occassionally when running dmesg or vi in a smaller window, but not always.
Unfortunately there is nothing in the virtualbox logs in the host, nor in the kernel logs in the guest VM.
What I tried to do to fix:
- update everything and following the virtualbox wiki closely
- changing the amount of video RAM in virtualbox
- setting the resolution differently (hardcoded in a kernel line or from the virtualbox shortcut in windows)
- enabling and disabling video accelleration in the VM.
Any help is appreciated!
Last edited by anadyr (2016-08-15 14:17:17)
Offline
See if this helps: use Ctrl+Alt+F1 or similar to switch to text console then Alt+F? to switch back to GUI
Offline
...and latest virtualbox-host-modules-arch.
Probably unrelated to your issue but why are you running the host modules? Surely you should be using the guest modules.
Offline
pm3840 what you suggest works. When switching to console and then back to the GUI the problem disappears entirely. This is a workaround I can live with, but it isn't a structural solution so I am hesitating to set this post to solved.
slithery: I made a typo and I corrected it just now. I was indeed running the guest-modules.
Offline
I have the same exact issue in windows 10
Offline