What logging options can I specify for VBoxSVC.exe with VirtualBox release builds?












0















I'm experiencing consistent program initialization failures with VirtualBox 5.x and the new 6.0 builds (OpenSourceEdition) on Windows 7 64bit, and after a whole week of trying it seems the only way to figure out the culprit is to do some logging for the main component, VBoxSVC.exe, and I had to look elsewhere as the official docs gave very little information on that.



I receive a COM error E_NOINTERFACE upon involing the main GUI. After some analysis I can conclude that either VBoxSVC.exe failed to instantiate IVirtualBox and kept silent about that, or inter-process COM communication went wrong (but all other COM applications on my system works fine).



And below goes my questions in detail:




  1. Is “logging of COM components” (as seen in official docs) of VBoxSVC.exe possible in release builds? (I am not in the position of building a Debug version anyway.)

  2. Which logging groups, flags and switches (if any) are recommended for my purpose? To be precise: logging for (1) tracing the entire IVirtualBox instatiation process in the VBoxSVC class factory and (2) monitoring all QueryInterface calls on the ProxyStub marshalling interface on both C/S.

  3. How do VBox / IPRT logging differ? What is Sander / Bird logging? How is Log-level defined and used in VBox? Didn't find docs for them.




BTW, there shan’t be any hardware issue -- I have several machines of same hardware, VirtualBox runs flawlessly on the rest of them.










share|improve this question



























    0















    I'm experiencing consistent program initialization failures with VirtualBox 5.x and the new 6.0 builds (OpenSourceEdition) on Windows 7 64bit, and after a whole week of trying it seems the only way to figure out the culprit is to do some logging for the main component, VBoxSVC.exe, and I had to look elsewhere as the official docs gave very little information on that.



    I receive a COM error E_NOINTERFACE upon involing the main GUI. After some analysis I can conclude that either VBoxSVC.exe failed to instantiate IVirtualBox and kept silent about that, or inter-process COM communication went wrong (but all other COM applications on my system works fine).



    And below goes my questions in detail:




    1. Is “logging of COM components” (as seen in official docs) of VBoxSVC.exe possible in release builds? (I am not in the position of building a Debug version anyway.)

    2. Which logging groups, flags and switches (if any) are recommended for my purpose? To be precise: logging for (1) tracing the entire IVirtualBox instatiation process in the VBoxSVC class factory and (2) monitoring all QueryInterface calls on the ProxyStub marshalling interface on both C/S.

    3. How do VBox / IPRT logging differ? What is Sander / Bird logging? How is Log-level defined and used in VBox? Didn't find docs for them.




    BTW, there shan’t be any hardware issue -- I have several machines of same hardware, VirtualBox runs flawlessly on the rest of them.










    share|improve this question

























      0












      0








      0








      I'm experiencing consistent program initialization failures with VirtualBox 5.x and the new 6.0 builds (OpenSourceEdition) on Windows 7 64bit, and after a whole week of trying it seems the only way to figure out the culprit is to do some logging for the main component, VBoxSVC.exe, and I had to look elsewhere as the official docs gave very little information on that.



      I receive a COM error E_NOINTERFACE upon involing the main GUI. After some analysis I can conclude that either VBoxSVC.exe failed to instantiate IVirtualBox and kept silent about that, or inter-process COM communication went wrong (but all other COM applications on my system works fine).



      And below goes my questions in detail:




      1. Is “logging of COM components” (as seen in official docs) of VBoxSVC.exe possible in release builds? (I am not in the position of building a Debug version anyway.)

      2. Which logging groups, flags and switches (if any) are recommended for my purpose? To be precise: logging for (1) tracing the entire IVirtualBox instatiation process in the VBoxSVC class factory and (2) monitoring all QueryInterface calls on the ProxyStub marshalling interface on both C/S.

      3. How do VBox / IPRT logging differ? What is Sander / Bird logging? How is Log-level defined and used in VBox? Didn't find docs for them.




      BTW, there shan’t be any hardware issue -- I have several machines of same hardware, VirtualBox runs flawlessly on the rest of them.










      share|improve this question














      I'm experiencing consistent program initialization failures with VirtualBox 5.x and the new 6.0 builds (OpenSourceEdition) on Windows 7 64bit, and after a whole week of trying it seems the only way to figure out the culprit is to do some logging for the main component, VBoxSVC.exe, and I had to look elsewhere as the official docs gave very little information on that.



      I receive a COM error E_NOINTERFACE upon involing the main GUI. After some analysis I can conclude that either VBoxSVC.exe failed to instantiate IVirtualBox and kept silent about that, or inter-process COM communication went wrong (but all other COM applications on my system works fine).



      And below goes my questions in detail:




      1. Is “logging of COM components” (as seen in official docs) of VBoxSVC.exe possible in release builds? (I am not in the position of building a Debug version anyway.)

      2. Which logging groups, flags and switches (if any) are recommended for my purpose? To be precise: logging for (1) tracing the entire IVirtualBox instatiation process in the VBoxSVC class factory and (2) monitoring all QueryInterface calls on the ProxyStub marshalling interface on both C/S.

      3. How do VBox / IPRT logging differ? What is Sander / Bird logging? How is Log-level defined and used in VBox? Didn't find docs for them.




      BTW, there shan’t be any hardware issue -- I have several machines of same hardware, VirtualBox runs flawlessly on the rest of them.







      virtualbox error-logging com






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 21 at 14:55









      user786008user786008

      13




      13






















          0






          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "3"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1396651%2fwhat-logging-options-can-i-specify-for-vboxsvc-exe-with-virtualbox-release-build%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Super User!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1396651%2fwhat-logging-options-can-i-specify-for-vboxsvc-exe-with-virtualbox-release-build%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          "Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

          Alcedinidae

          RAC Tourist Trophy