VirtualBox

Version 97 (modified by Michael Thayer, 7 years ago) ( diff )

Instructions for the new ticket page too.

Bugtracker

This site offers a public bugtracker. In case you encounter problems with VirtualBox or have other suggestions for improvements, you can use this facility to report those issues, which will then be called a "ticket". Each such ticket receives a unique number that you can later refer to in order to see if any progress was made, or add comments to it.

How to improve your chances of getting your problem solved

  • Remember that VirtualBox has a huge community including highly skilled programmers. The core team is small and busy, the number of users with bug reports is large and we have to prioritise customer issues. But there might well be someone else out there with the same problem and the skills to fix it. Or talk to us about whether it would be covered by a support contract for a given number of licences.
  • Remember that you can still do a lot of work on a bug even if you can't program by studying and isolating it. Problems which developers can reproduce quickly and easily are much more likely to be fixed than problems which only happen on certain systems, or require installing special software in special virtual machines. So look for simpler ways of triggering the problem.
  • Try out a test build to see if the problem has already been fixed.
  • Do some research (e.g. using search engines, our ​forums and existing bug tickets) before creating a ticket. Try to solve as much of the problem as you can yourself or in collaboration with other users.
  • Describe as precisely as you can how to reproduce the problem, bearing in mind that it may be triggered by something special on your own computer system. Fixing problems which cannot be reproduced is long and painful, both for the developer and the bug reporter. It may help to find other people with the same problem and compare notes.
  • Attach a (full) log file straight away to save time for you and for us. The log file contains a lot of useful information about both the host and the guest systems as well as information about what happened during a particular machine run. Please do not cut and paste it.
  • Look for possible duplicate tickets and ​end-user forum topics first, but unless you are sure, create a new ticket and point out the possible duplicates there.
  • Choose a summary carefully. The bug tracker and ticket notifications are mainly seen by (busy) developers, and unless a summary catches their eye and looks related to the things they as an individual work on the ticket may not even be read.
  • Please stay polite, relevant and on-topic. Offensive or unrelated comments and tickets hurt everyone and may be deleted.
  • Do not report compile and development problems here, use the developer mailing list for such problems.
  • If you want to report a crash of VirtualBox on a Linux/Solaris host, please provide a core dump if possible. If you want to report a crash on a Windows host, please attach a minidump if possible.
  • Use {{{ and }}} to enclose verbose text. See Wikiformatting for more details on how to use other format specifiers to make your text look pretty.

To create new tickets, you must have registered with this site and be logged in with your user name and password. Use the "Register" and "Login" links at the top right for that. If you add a comment to an existing ticket, you will receive e-mail notification every time that ticket is updated.

Then, use these links to access the bugtracker:

Note: See TracWiki for help on using the wiki.

© 2023 Oracle
Contact – Privacy policy – Terms of Use