You are not logged in.
Hello all,
Due to a failing SSD drive I made a ddrescue image of my whole arch installation, then converted to a vdi file hoping to be able to run the system in virtualbox on another computer under debian jessie.
After a little fiddling with EFI in virtualbox, I managed to boot the system but failed to start the GUI. A quick pacman session to install the missing guest modules later and I went from a missing vboxvideo to an ABI version mismatch causing Xorg to fail.
Xorg.0.log shows:
[ 12.466] (II) Module vboxvideo: vendor="Oracle Corporation"
[ 12.466] compiled for 1.17.4, module version = 1.0.1
[ 12.466] Module class: X.Org Video Driver
[ 12.466] ABI class: X.Org Video Driver, version 19.0
[ 12.466] (EE) module ABI major version (19) doesn't match the server's version (20)
[ 12.466] (II) UnloadModule: "vboxvideo"
[ 12.466] (II) Unloading vboxvideo
[ 12.466] (EE) Failed to load module "vboxvideo" (module requirement mismatch, 0)
additional errors:
[ 12.475] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 12.475] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 12.485] (EE) Screen 0 deleted because of no matching config section.
[ 12.485] (EE) Device(s) detected, but none match those in the config file.
[ 12.554] (EE)
[ 12.554] (EE) no screens found(EE)
[ 12.554] (EE)
[ 12.554] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 12.554] (EE)
[ 12.562] (EE) Server terminated with error (1). Closing log file.
I tried reinstalling from repo-ck and rebuilding virtualbox-ck-guest-modules from AUR but the issue remains. Did I miss something ? Where can I find information to fix this ?
Last edited by kazimir (2015-12-20 18:07:13)
Offline
That error isn't about the vboxvideo kernelmodule , but the xorg vboxvideo module.
What version is your virtualbox-guest-utils package ?
Last edited by Lone_Wolf (2015-12-19 13:30:45)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
yeah, i can confirm the problem.
After this last -Syu (yesterday) i am getting same errors here.
I can start Xorg after installing xf86-video-vesa driver on guest, but without vboxvideo support. Can´t change resolution, etc...
I had rebuild the modules and the problem persist. I am using stock kernel in both host and guest.
I am looking for a solution...
Offline
The installed virtualbox-guest-utils version is the current one from the community repository so 5.0.10-3.
I installed xf86-video-vesa in the guest but X still fails to start with this new error:
(EE) VESA(0): V_BIOS address 0x0 out of range
Last edited by kazimir (2015-12-19 14:32:34)
Offline
For a temporary solution :
Downgrading virtualbox-guest-utils to 5.0.10-2 seem to work.
Offline
Maybe should be open a bug report?
Offline
I'm having exactly this same problem here.
I can confirm that downgrading virtualbox-guest-utils to 5.0.10-2 temporarily solves the problem as suggested by matmoul.
Last edited by kwash (2015-12-19 21:37:40)
Offline
@semeion: this is already a known bug.
A fix will be included for VirtualBox 5.0.12 build: (look at latest comments)
https://bugs.archlinux.org/task/45748
Last edited by kwash (2015-12-19 22:02:41)
Offline
virtualbox-guest-utils 5.0.12-1 released and this problem seems fixed.
Working normal for me now.
Offline
5.0.12-1 works for me too. Marking the thread as solved.
Offline
Yes, it was fixed with 5.0.12-1.
Write [SOLVED] in topic
Offline