Enhancment - VBoxBugReport to include guest logs, optional components

[Socratis]

VBoxBugReport seems to be a great information collecting tool. However, as it stands right now, I believe that there is a vital piece of information missing: the Guest Logs. It should be trivial to include them along with the Guest.vbox and the GuestProperties. The whole subdirectory with the 4 logs.

On the other hand, under Windows, there is information included that is not always necessary for basic troubleshooting. For example, on my system, a typical report will include:

• 17 MB of setupapi.dev.log.
• 7 MB of setupapi.app.log.
• The whole Windows update history.

That alone makes the size of the compressed report almost 1.5 MB, which makes it not attachable to the forums.

So, please also consider the possibility of adding command line switches to control the output of the VBoxBugReport tool:

• -m or--minimal for the really bare minimal information like Guest.vbox and Guest logs,
• -n or--network for the minimal plus networking,
• -u or--usb for the minimal plus USB,
• -b or --basic (that's the default option) a combination of "-m -n -u" and
• -f or--full for the complete (as is now) report.

[Frank Mehnert]

VBoxBugReport already contains the -A switch which adds the VBox.log files of all registered virtual machines. Specifying selected VMs is also possible. I don't see a reason to add many more command line parameters.

[Socratis]

• The "-A" switch was already there, no problem, but it did not add the "VBox.log.*" files, it was simply going through each registered VM, see next.

• At 5.1.14 when the ticket was opened, the four "VBox.log.*" logs were not included in the report. Now they are. It shows in the source code changes, I just didn't search for the exact revision that the change was implemented. The change happened between 5.1.16 and 5.1.18, if you search for "VmDir.next" in the "VBoxBugReport.cpp", so thank you for that.

• The rest of the switches as I said were not meant to increase the size of the report, but to decrease/filter it so that it could fit into a logical/acceptable size at the forums, depending on the problem. You don't want to include the kitchen sink if you're simply looking for USB problems. Not from the get-go at least...

Thanks for looking into it, no matter the outcome... :(

I can see that the report is a work in progress in every revision, so one can only hope. Hope that I become competent enough in C so that I can make and contribute the changes ;)