Summary: | app-emulation/virtualbox-5.1.20: Fails to start VMs for Windows guests that are started fine with app-emulation/virtualbox-5.1.18 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | fuse809 |
Component: | Current packages | Assignee: | Lars Wendler (Polynomial-C) (RETIRED) <polynomial-c> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | captaincrutches, masterzorag, paolo.pedroni, perfect007gentleman, proxy-maint, rossi.f, wgh |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | diff_5.1.22_dlopen_fix |
Description
fuse809
2017-04-21 17:59:36 UTC
All other VMs (including for the BSDs: FreeBSD 11, 11-STABLE, NetBSD 7.1, OpenBSD 6.0; Icaros desktop, OpenIndiana, Linux, FreeDOS and ReactOS) work fine with both app-emulation/virtualbox-5.1.18 and app-emulation/virtualbox-5.1.20. For me, after upgrading to 5.1.20, Linux guests stopped working: in Gentoo guest, plasma session faield to start, and KDE Neon guest doesn't boot anymore, too (host has 5.1.20 version). I have similar issue with 5.1.20 (didn't check 5.1.18). When I start VirtualBox from console, I got following output: libGL error: unable to load driver: i965_dri.so libGL error: driver pointer missing libGL error: failed to load driver: i965 libGL error: unable to load driver: i965_dri.so libGL error: driver pointer missing libGL error: failed to load driver: i965 libGL error: unable to load driver: swrast_dri.so libGL error: failed to load driver: swrast For some reason VirtualBox can't load host OpenGL. Disabling 3D-acceleration in guest setting allows to boot VM, however another issue arise: VirtualBox states that: No audio devices could be opened. Selecting the NULL audio backend with the consequence that no sound is audible. HostAudioNotResponding Another workaround for OpenGL is to set LIBGL_DRIVERS_PATH=/usr/lib64/mesa, to folder where drivers binary lays; setting it /usr/lib64/dri where symlinks present doesn't work! IMO, something is terribly spoiled. Might be relevant that in all my VMs I have VirtualBox Guest Additions (VBGA) 5.1.18 installed in all my Linux and Windows VMs. It was installed from the VBGA ISO inserted into the VMs. (In reply to Brenton Horne from comment #4) > Might be relevant that in all my VMs I have VirtualBox Guest Additions > (VBGA) 5.1.18 installed in all my Linux and Windows VMs. It was installed > from the VBGA ISO inserted into the VMs. I couldn't start my Win7 VM after upgrading to 5.1.20. At first I thought it was due to the VM being suspended with the previous 5.1.18. However, a few tries later (installing/deinstalling Guest Additions), I can state the culprit is VirtualBox 5.1.20 with Guest Additions installed: if I launch my Win7 VM with VirtualBox 5.1.20 before installing its GA, the VM starts. But, if later on I install GA and reboot the VM, not only it does not complete the start, but Plasma itself becomes non-responsive to mouse clicks even tough I can move the cursor around. I can only gain control back if I swith to a console tty and reboot the host. (In reply to urcindalo from comment #5) > (In reply to Brenton Horne from comment #4) > > Might be relevant that in all my VMs I have VirtualBox Guest Additions > > (VBGA) 5.1.18 installed in all my Linux and Windows VMs. It was installed > > from the VBGA ISO inserted into the VMs. > > I couldn't start my Win7 VM after upgrading to 5.1.20. At first I thought it > was due to the VM being suspended with the previous 5.1.18. However, a few > tries later (installing/deinstalling Guest Additions), I can state the > culprit is VirtualBox 5.1.20 with Guest Additions installed: if I launch my > Win7 VM with VirtualBox 5.1.20 before installing its GA, the VM starts. But, > if later on I install GA and reboot the VM, not only it does not complete > the start, but Plasma itself becomes non-responsive to mouse clicks even > tough I can move the cursor around. I can only gain control back if I swith > to a console tty and reboot the host. Just for the shake of clarity. I deinstalled GA by booting the Win7 VM into Windows Safe Mode, and then the Win7 VM starts OK normally with 5.1.20 when *no* GA are installed. I am having the same problem on two different systems (Desktop and Laptop): Result Code: NS_ERROR_FAILURE (0x80004005) Component: SessionMachine Interface: ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7} I reinstalled 5.1.18 and everything started working again. Seems only to be the Windows VMs (WinXP, Win 7, and Win 10). Some other information about this in this gentoo forum thread : https://forums.gentoo.org/viewtopic-p-8060154.html I keep getting this error with 5.1.22 too! This issue also occurs with app-emulation/virtualbox-bin-5.1.22.115126. Yes. This 'feature' is still there. So downgrade back to 5.1.18 release is only possibility. :-( I still have problem after installing 5.1.22, went back to 5.1.18. Seeing https://www.virtualbox.org/ticket/16693 it looks like VirtualBox refuses to load shared libraries with 777 permissions. On gentoo the dri libraries in /usr/lib64/dri are symlinks to libraries in /usr/lib64/mesa (thus 777) and VirtualBox is not smart enough to determine that they are symlinks and not actually world writable libraries, thus denying loading. Created attachment 472320 [details, diff] diff_5.1.22_dlopen_fix Patch from https://www.virtualbox.org/ticket/16693 Placed the patch provided by Frank into /etc/portage/patches/app-emulation/virtualbox-5.1.22 VirtualBox 5.1.22 compiling and all my VMs are working again. commit 711bd6953ba3b6e086e30f77048b693f31082d73 (HEAD -> master, origin/master, origin/HEAD) Author: Lars Wendler <polynomial-c@gentoo.org> Date: Thu May 11 14:07:06 2017 app-emulation/virtualbox: Fixed OpenGL issue (bug #616238). Package-Manager: Portage-2.3.5, Repoman-2.3.2 Any chance to backport this fix to 5.0.x? Unfortunately, 5.1.x is broken in different way, so I'm stuck with 5.0.x for now: https://www.virtualbox.org/ticket/15863 LIBGL_DRIVERS_PATH=/usr/lib64/mesa workaround does work. |