VirtualBox

Ticket #4294 (closed enhancement: fixed)

Opened 5 years ago

Last modified 5 years ago

[feature-request] Please improve debugging and logging (vbox.log) for OpenGL -> Fixed in SVN.

Reported by: Technologov Owned by:
Priority: major Component: 3D support
Version: VirtualBox 2.2.4 Keywords:
Cc: Guest type: other
Host type: other

Description

VBox lacks a debugging for OpenGL in vbox.log...

I would like to see which OpenGL extensions are available on Host, and which are forwarded to guest (similar to CPU flags). This can be logged once OpenGL driver is loaded by guest.

This is important because on different Host OSes, same graphics card may have different features due to different drivers.

-Technologov, 24.6.2009.

Change History

comment:1 Changed 5 years ago by leonid

  • Summary changed from [feature-request] Please improve debugging and logging (vbox.log) for OpenGL to [feature-request] Please improve debugging and logging (vbox.log) for OpenGL -> Fixed in SVN.

I've added extensions dump on the host as it could be usefull indeed.

Regarding the ones which are forwarded to guest, it's an intersection of extensions supported on host and extensions supported in our code + some additions. It's not something which may vary as it's limited by the code and will just pollute the host log. In case of need one could run glxinfo or glewinfo on the guest to see this list.

Also, note that running host VM with CR_DEBUG=1 env set, will dump more information to the host log.

comment:2 Changed 5 years ago by Technologov

OK, this is now FIXED in v3.0. Please close bug.

-Technologov

comment:3 Changed 5 years ago by frank

  • Status changed from new to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use