| 1 | <?xml version='1.0' encoding='UTF-8'?>
|
|---|
| 2 | <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
|
|---|
| 3 | <topic xml:lang="en-us" id="gimdebughyperv">
|
|---|
| 4 | <title>Hyper-V Debug Options</title>
|
|---|
| 5 |
|
|---|
| 6 | <body>
|
|---|
| 7 | <p>All of the options listed below are optional, and thus the default value specified will be used when the
|
|---|
| 8 | corresponding key-value pair is not specified. </p>
|
|---|
| 9 | <ul>
|
|---|
| 10 | <li>
|
|---|
| 11 | <p>Key: <b outputclass="bold"><codeph>enabled</codeph></b>
|
|---|
| 12 | </p>
|
|---|
| 13 | <p>Value: <codeph>0</codeph> or <codeph>1</codeph>
|
|---|
| 14 | </p>
|
|---|
| 15 | <p>Default: <codeph>0</codeph>
|
|---|
| 16 | </p>
|
|---|
| 17 | <p>Specify <codeph>1</codeph> to enable the Hyper-V debug interface. If this key-value pair is not specified or
|
|---|
| 18 | the value is not <codeph>1</codeph>, the Hyper-V debug interface is disabled regardless of other
|
|---|
| 19 | key-value pairs being present. </p>
|
|---|
| 20 | </li>
|
|---|
| 21 | <li>
|
|---|
| 22 | <p>Key: <b outputclass="bold"><codeph>address</codeph></b>
|
|---|
| 23 | </p>
|
|---|
| 24 | <p>Value: IPv4 address </p>
|
|---|
| 25 | <p>Default: 127.0.0.1 </p>
|
|---|
| 26 | <p>Specify the IPv4 address where the remote debugger is connected. </p>
|
|---|
| 27 | </li>
|
|---|
| 28 | <li>
|
|---|
| 29 | <p>Key: <b outputclass="bold"><codeph>port</codeph></b>
|
|---|
| 30 | </p>
|
|---|
| 31 | <p>Value: UDP port number </p>
|
|---|
| 32 | <p>Default: 50000 </p>
|
|---|
| 33 | <p>Specify the UDP port number where the remote debugger is connected. </p>
|
|---|
| 34 | </li>
|
|---|
| 35 | <li>
|
|---|
| 36 | <p>Key: <b outputclass="bold"><codeph>vendor</codeph></b>
|
|---|
| 37 | </p>
|
|---|
| 38 | <p>Value: Hyper-V vendor signature reported by CPUID to the guest </p>
|
|---|
| 39 | <p>Default: When debugging is enabled: <codeph>Microsoft Hv</codeph>, otherwise: <codeph>VBoxVBoxVBox</codeph>
|
|---|
| 40 | </p>
|
|---|
| 41 | <p>Specify the Hyper-V vendor signature which is exposed to the guest by CPUID. For debugging Microsoft Windows
|
|---|
| 42 | guests, it is required the hypervisor reports the Microsoft vendor. </p>
|
|---|
| 43 | </li>
|
|---|
| 44 | <li>
|
|---|
| 45 | <p>Key: <b outputclass="bold"><codeph>hypercallinterface</codeph></b>
|
|---|
| 46 | </p>
|
|---|
| 47 | <p>Value: <codeph>0</codeph> or <codeph>1</codeph>
|
|---|
| 48 | </p>
|
|---|
| 49 | <p>Default: <codeph>0</codeph>
|
|---|
| 50 | </p>
|
|---|
| 51 | <p>Specify whether hypercalls should be suggested for initiating debug data transfers between host and guest
|
|---|
| 52 | rather than MSRs when requested by the guest. </p>
|
|---|
| 53 | </li>
|
|---|
| 54 | <li>
|
|---|
| 55 | <p>Key: <b outputclass="bold"><codeph>vsinterface</codeph></b>
|
|---|
| 56 | </p>
|
|---|
| 57 | <p>Value: <codeph>0</codeph> or <codeph>1</codeph>
|
|---|
| 58 | </p>
|
|---|
| 59 | <p>Default: When debugging is enabled, <codeph>1</codeph>, otherwise <codeph>0</codeph>
|
|---|
| 60 | </p>
|
|---|
| 61 | <p>Specify whether to expose the VS#1 virtualization service interface to the guest. This interface is required
|
|---|
| 62 | for debugging Microsoft Windows 10 32-bit guests, but is optional for other Windows versions. </p>
|
|---|
| 63 | </li>
|
|---|
| 64 | </ul>
|
|---|
| 65 | </body>
|
|---|
| 66 | </topic>
|
|---|
