Changeset 58478 in vbox

Timestamp:

Oct 29, 2015 12:39:11 PM (9 years ago)

Author:

vboxsync

Message:

Manual: Expanded paravirt debug section slightly.

File:

• trunk/doc/manual/en_US/user_AdvancedTopics.xml (modified) (5 diffs)

trunk/doc/manual/en_US/user_AdvancedTopics.xml

@@ -3978 +3978 @@
           <para>Default: When debugging is enabled, <computeroutput>1</computeroutput>,
           otherwise <computeroutput>0</computeroutput></para>
-          <para>Specify whether to expose the "VS#1" (virtualization service interface) to the
+          <para>Specify whether to expose the "VS#1" (virtualization service) interface to the
           guest. This interface is required for debugging Microsoft Windows 10 32-bit guests, but
           is optional for other Windows versions.</para>
@@ -4017 +4017 @@
               <computeroutput>kdvm.dll</computeroutput> from a Windows 8.0 installation<footnote>
               <para>Only Windows 8.0 ships <computeroutput>kdvm.dll</computeroutput>. Windows 8.1
-              and newer Windows guests do not.</para></footnote>. This file is
+              and newer Windows versions do not.</para></footnote>. This file is
               typically located in <computeroutput>C:\Windows\System32</computeroutput>. Copy it
               to the same location in your Windows 7 guest. Make sure you copy the 32-bit or
@@ -4068 +4068 @@
                   and may be used if security is not a concern. If you do not specify any encryption key,
                   <computeroutput>bcdedit</computeroutput> will generate one for you and you will need to copy
-                  this key to later paste into Microsoft WinDbg on the remote end.</para>
+                  this key to later enter in Microsoft WinDbg on the remote end.</para>
                 </listitem>
                 <listitem>
@@ -4078 +4078 @@
                     <screen>bcdedit /set bootdebug {bootmgr} on</screen>
                   </para>
-                  <para>Refer to your official Microsoft documentation for what each of the above
+                  <para>Please refer to Microsoft Windows documentation for what each of the above
                   debug option covers.</para>
                 </listitem>
@@ -4097 +4097 @@
               <para>Now press "OK" to start listening for connections. Microsoft WinDbg typically shows
               a "Waiting to reconnect" message during this phase.</para>
+
+              <para>Alternatively, launch WinDbg from the command line to launch a debug session:
+                <screen>windbg.exe -k net:port=50000,key=1.2.3.4</screen>
+              Please refer to the WinDbg documentation for complete command line syntax.
+              </para>
 
             </listitem>