Changes between Version 8 and Version 9 of VBoxLogging

Timestamp:

Nov 29, 2012 2:22:00 PM (11 years ago)

Author:

Michael Thayer

Comment:

Slightly expanded, particularly for Linux guests.

VBoxLogging

@@ -9 +9 @@
 control debug log output and `VBOX_RELEASE_LOG`, `VBOX_RELEASE_LOG_DEST` and
 `VBOX_RELEASE_LOG_FLAGS` to control release log output.  Logging settings can also be
-changed at runtime using the debugger, and starting with 4.1.8 via `VBoxManage debugvm`.
+changed at runtime using the debugger, and starting with 4.1.8 via `VBoxManage debugvm`.  If you are wanting to get logging from ring-0 components or from the Guest Additions please see the specific sections about those too (both if you need ring-0 Additions logging).
 
 Examples:
@@ -50 +50 @@
 sparingly in performance-critical code.
 
-Logging from ring-0 context is by default using a hardcoded config found in [/browser/trunk/src/VBox/Runtime/VBox/log-vbox.cpp#L469 Runtime/VBox/log-vbox.cpp]. Since it would generally be more useful to get the ring-0 context log output in the same log file as the ring-3 and raw-mode context log statements when debugging VMM issues on the host, we've created little hack for doing so: Add VBOX_WITH_R0_LOGGING=1 to !LocalConfig.kmk or pass it to kmk in the command line. When using this hack the ring-0 logger will mostly use the same settings as the ring-3 logger.
+== Ring-0 logging ==
+
+Logging from ring-0 context is by default using a hardcoded config found in [/browser/trunk/src/VBox/Runtime/VBox/log-vbox.cpp#L469 Runtime/VBox/log-vbox.cpp]. Since it would generally be more useful to get the ring-0 context log output in the same log file as the ring-3 and raw-mode context log statements when debugging VMM issues on the host, we've created (for *host* ring-0 logging!) a little hack for doing so: Add VBOX_WITH_R0_LOGGING=1 to !LocalConfig.kmk or pass it to kmk in the command line. When using this hack the ring-0 logger will mostly use the same settings as the ring-3 logger.
+
+When setting up ring-0 logging on a Linux guest using self-built additions, make sure that your changes to log-vbox.cpp really made it into log-vbox.c in the kernel module source code on the guest.  If you wish to enable ring-0 logging on a Linux guest using an official Additions build, you can modify VBox/log-vbox.c in the module source on the guest and force a rebuild and reload of the module.  If you wish to pass through guest ring-3 logging to the host, change the make file to build a debug version of the module.
 
 Some notes about group suffixes:[[BR]]
@@ -70 +74 @@
 export VBOX_LOG=-all
 }}}
+
+== Guest Additions logging ==
 
 To enable Guest Additions logging, add to the host environment variables: