LHC@home

I thought I'd create a new thread here as I'm not finding any related posts on the LHC boards.
In attempting to troubleshoot the issues my Win10 host is having in thread https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=5751, I'm looking more into how to troubleshoot vbox guest instances and their interaction with host machines. The individual VM vbox.log and vboxhardening.log are created inside the "<BOINC directory>/slots/n/..." and removed/deleted when a task fails.

I know that part of the VBoxSVC.log is copied into the LHC task stderr output under the "Hypervisor System Log:" and I believe a part of the individual vm vbox.log is under the "VM Trace Log:" section. (I'm not sure of the VM TRace log info since I have not looked into the vbox.log of a running CMS task.) It does not look like any of the vboxhardening.log info is captured in the task stderr output. For my host issue above, I need to get the whole log files for troubleshooting with VirtualBox forums.

The only option right now is to hover over my client, waiting for a CMS task to be assigned, and watching the vm log files in the ~20 minutes it's running.

- Is there a way to capture/copy the whole log file to another directory when a task fails?
- Can this functionality be added to the LHC features or capabilities backlog for development?
- Could it be a debug option enabled through one of the BOINC client config files? (no idea if that is feasible or not)

- Is there a way to capture/copy the whole log file to another directory when a task fails?

On Linux you would use the tail command from within a separate monitoring console like:
tail -f name_of_the_log >logcopy_at_a_save_location

On windows there's no extra command but you may try something like this from a powershell:
get-content name_of_the_log –wait >logcopy_at_a_save_location

I made a guestimate and was waiting on my host when it received a CMS task. I've captured the VBox, VBoxHardening, VBoxUI, and vbox_trace logs from the ./slots/ folder the task was running in. I'm posting to the VirtualBox forums for help in troubleshooting the logs.

https://forums.virtualbox.org/viewtopic.php?f=3&t=104465