[vbox-dev] Enabling logging in R0 context

[Frank Mehnert]

Luca,

On Thursday 26 November 2015 10:56:20 Luca Carotenuto wrote:
> > R0 logging is not possible with 'release' logging. You need to build
> > a debug build (as you already did) and enable the 'debug' logging.
> > And you need to add
> > 
> >   VBOX_WITH_R0_LOGGING=1
> > 
> > to your LocalConfig.kmk, see src/VBox/VMM/include/VMMInternal.h lines
> > 47ff.
> > 
> > When you run your VM, set 'VBOX_LOG=srv_intnet.e.l.l2.f'. Make sure that
> > these environment settings apply to the VM process you start. The 'debug'
> > log file is placed into the current directory, not into Logs/ subdirectory
> > of the VM directory.
> 
> I have done exactly what you suggested, but it's not working. I also tried
> to check if VBOX_WITH_R0_LOGGING is set to 1 at runtime by adding a Log in
> a R3 network driver, but it shows that this flag is not set.
> Any other suggestions?

at first you should check if VBOX_WITH_R0_LOGGING is really defined when
you compile the VMM part. Apply this patch manually:

--- VMMR3/VMM.cpp       (revision 104360)
+++ VMMR3/VMM.cpp       (working copy)
@@ -383,6 +383,7 @@
         }
 
 # ifdef VBOX_WITH_R0_LOGGING
+# error EXPECTED
         size_t const cbLogger = RTLogCalcSizeForR0(pLogger->cGroups, 0);
         for (VMCPUID i = 0; i < pVM->cCpus; i++)
         {

and compile your tree. If 'kmk' does not abort with a build error "EXPECTED"
then you did something wrong.

Kind regards,

Frank
-- 
Dr.-Ing. Frank Mehnert | Software Development Director, VirtualBox
ORACLE Deutschland B.V. & Co. KG | Werkstr. 24 | 71384 Weinstadt, Germany

ORACLE Deutschland B.V. & Co. KG
Hauptverwaltung: Riesstraße 25, D-80992 München
Registergericht: Amtsgericht München, HRA 95603

Komplementärin: ORACLE Deutschland Verwaltung B.V.
Hertogswetering 163/167, 3543 AS Utrecht, Niederlande
Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
Geschäftsführer: Alexander van der Ven, Astrid Kepper, Val Maher