VirtualBox

Ticket #15005 (new defect)

Opened 4 years ago

Last modified 4 years ago

no 3D accelaration when using WebService or VBoxManage startvm --headless (iGPU HD4000)

Reported by: peter_temp Owned by:
Component: other Version: VirtualBox 5.0.12
Keywords: Cc: peter_temp@…
Guest type: other Host type: other

Description (last modified by frank) (diff)

Host:cat /etc/*-releaseDISTRIB_ID=LinuxMint
DISTRIB_RELEASE=17.3
DISTRIB_CODENAME=rosa
DISTRIB_DESCRIPTION="Linux Mint 17.3 Rosa"
NAME="Ubuntu"
VERSION="14.04.3 LTS, Trusty Tahr"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 14.04.3 LTS"
VERSION_ID="14.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
cat: /etc/upstream-release: Is een map
Linux Cinnamon 64 bit
  1. procedure: installed latest VB & extension pack
  2. installed phpvirtualbox 5.0.4
  3. import via webinterface a Win7 appliance

When starting appliance, following error occors:

This VM was configured to use 3D acceleration. However, the 3D support of the host is not working properly and the VM cannot be started. To fix this problem, either fix the host 3D support (update the host graphics driver?) or disable 3D acceleration in the VM settings (VERR_NOT_AVAILABLE)

3D is working & enabled

glxgears work ok

/usr/lib/nux/unity_support_test -p
OpenGL vendor string:   Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Mobile 
OpenGL version string:  3.0 Mesa 10.5.9

Not software rendered:    yes
Not blacklisted:          yes
GLX fbconfig:             yes
GLX texture from pixmap:  yes
GL npot or rect textures: yes
GL vertex program:        yes
GL fragment program:      yes
GL vertex buffer object:  yes
GL framebuffer object:    yes
GL version is 1.4+:       yesr

Unity 3D supported:       yes

is also ok.

The appliance can only be started directly in VB interface, not via VboxManage or webinterface.

Attachments

vboxlogs.zip Download (25.6 KB) - added by peter_temp 4 years ago.
vbox logfiles
outpout.log Download (6.0 KB) - added by peter_temp 4 years ago.
logfile of /usr/lib/virtualbox/VBoxTestOGL --test 3d

Change History

Changed 4 years ago by peter_temp

vbox logfiles

Changed 4 years ago by peter_temp

logfile of /usr/lib/virtualbox/VBoxTestOGL --test 3d

comment:1 Changed 4 years ago by frank

  • Description modified (diff)

comment:2 Changed 4 years ago by frank

  • Description modified (diff)

comment:3 Changed 4 years ago by frank

The reason for this behavior is the following: When you start the VM with the regular frontend (VirtualBox) then it is possible to enable 3D acceleration because this frontend can run on a graphical system. If the VM is executed headless (either with VBoxHeadless or from the VBox web services) then there is no graphical desktop available (no DISPLAY variable).

If you enabled 3D in the VM settings and the guest is using this feature, we are in a dilemma: The saved state of the VM contains the guest state when the guest used 3D. Now you try to run this VM with a frontend which does not support 3D anymore. Therefore loading this saved state is not possible anymore.

The ultimate fix for this behavior would be to implement a software-based emulation of the 3D support on the host side and load the saved 3D state into this emulation. This will not happen, at least not in the near future.

You can only run the saved state with 3D enabled on a frontend which supports 3D (VirtualBox). If you disable 3D in the VM settings then the guest will not depend on 3D on the host and you will also be able to load such a saved state from a headless frontend.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use