Bug 259234
| Summary: | emulators/virtualbox-ose proliferation of ~/⋯-VirtualBoxVM-⋯.log files | ||
|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Graham Perrin <grahamperrin> |
| Component: | Individual Port(s) | Assignee: | Virtualbox Team (Nobody) <vbox> |
| Status: | Closed FIXED | ||
| Severity: | Affects Many People | CC: | madpilot, newton.ja.terry |
| Priority: | --- | Flags: | bugzilla:
maintainer-feedback?
(vbox) |
| Version: | Latest | ||
| Hardware: | Any | ||
| OS: | Any | ||
|
Description
Graham Perrin
2021-10-17 18:49:11 UTC
From opening post <https://forums.freebsd.org/posts/537276>: > … from virtualbox-ose-6.1.22_1 to virtualbox-ose-6.1.26_3. … If it helps to understand the bug, as it is now: * I vaguely recall occasional manual removal of .log files from ~ with _lesser_ versions of VirtualBox. There were, in the past, so few that I paid almost zero attention. I did wonder whether they were visible debris, from guest sessions that were abnormally killed. (So little attention, I never thought to browse my home directory _during_ a run of a guest, to tell whether a .log was normally visible during a run.) ---- As things are now: % pkg info -x virtualbox virtualbox-ose-6.1.26_3 virtualbox-ose-kmod-6.1.26 % I see a log file appear immediately after starting, for example, a saved session. During the run: % date ; cat 2021-10-21-05-50-55.003-VirtualBoxVM-56324.log Thu 21 Oct 2021 06:55:39 BST Log created: 2021-10-21T05:50:55.038476000Z Process ID: 56324 (0xdc04) Parent PID: 56320 (0xdc00) Executable: /usr/local/lib/virtualbox/VirtualBoxVM Arg[0]: /usr/local/lib/virtualbox/VirtualBoxVM Arg[1]: --comment Arg[2]: Windows Arg[3]: --startvm Arg[4]: 6bec4796-c6ff-4ebc-8c20-3e56093e1eca Arg[5]: --no-startvm-errormsgbox % (In reply to Graham Perrin from comment #1) > … During the run: … After graceful closure and save of the guest, followed by a graceful quit of the Oracle VM VirtualBox application: the same. (The file persists, nothing appended.) This is a known issue since 6.1.x got in the tree. It was deemed not important enough to not update the port to 6.1. They are left behind every time a virtual machine is started. Someone (can't remember who) observed they used to be created in the past too, but usually automatically removed if everything went fine with the launched VM. One thing that could help with this is dig out in the source code where these files are being created. When debugging such issues a lot of time needs to be spent on finding the involved part of the source code [1], especially when the involved people do not know the structure of the code by hearth. So if you have time to spend on this digging the source code would help more than describing the external behaviour of the software, which is already known. Also understanding the original purpose of these log files could help. [1] this is also the reason why good backtraces are so important when any bug arises in any mildly complex software Thanks, I'll do what I can (and draw attention in FreeBSD Forums). (In reply to Guido Falsi from comment #3) > One thing that could help with this is dig out in the source code where these > files are being created. It looks like the involved parts of the source code are to find in https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Runtime/VBox/log-vbox.cpp "Create the default logging instance." https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Runtime/VBox/log-vbox.cpp#L496 "Write a log header." https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Runtime/VBox/log-vbox.cpp#L519 I'm not sure how to proceed from here to find the purpose of their creation and the cause of the log files not being removed, assuming they are automatically removed. Apropos, the creation of those log files can be suppressed by setting VirtualBox env variable "VBOX_LOG_DEST" to "nofile". References: https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Runtime/VBox/log-vbox.cpp#L38 https://www.virtualbox.org/wiki/VBoxLogging (In reply to Newton Terry from comment #5) Thanks for your findings. So this is the default logging mechanism doing its work. If configured to log a lot of information would be logged to these files. As far as I know these files have always been created by virtualbox but usually got deleted, maybe right away, depending on..."Something". But I cannot see any code to remove these files in `src/VBox/Runtime/common/log/log.cpp` or `src/VBox/Runtime/VBox/log-vbox.cpp`. So at present I'm asking myself how these got deleted in version 5.2.x. A quick look at the old distfile or the change history of these files is not helpful unluckily. To the OP, is this still an issue? Looks like the latest update (6.1.32) fixed this. Can you confirm? My testing shows the issue has been fixed after upgrade to 6.1.32 (In reply to Guido Falsi from comment #7) My apologies for the late response. I removed the setenv VBOX_LOG_DEST nofile workaround from my ~/.cshrc then used Oracle VM VirtualBox Manager to start two guests. After gracefully shutting down one of the guests then quitting Oracle VM VirtualBox Manager: * no unexpected .log file in my home directory. Thank you! ---- % ls ~/*.log | grep -i virtualbox ls: No match. % ls ~/*.log ls: No match. % pkg info -x virtualbox virtualbox-ose-6.1.32_2 virtualbox-ose-kmod-6.1.32_1 % pkg -vv | grep -e url -e enabled url : "pkg+http://pkg0.pkt.freebsd.org/FreeBSD:14:amd64/latest", enabled : yes, url : "https://alpha.pkgbase.live/current/FreeBSD:14:amd64/latest", enabled : no, url : "file:///usr/local/poudriere/data/packages/main-default", enabled : yes, % uname -aKU FreeBSD mowa219-gjp4-8570p-freebsd 14.0-CURRENT FreeBSD 14.0-CURRENT #8 main-n254268-50e244964e9-dirty: Mon Apr 4 09:29:49 BST 2022 root@mowa219-gjp4-8570p-freebsd:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG amd64 1400056 1400056 % |