Changeset 64653 in vbox for trunk/src/VBox/ValidationKit/docs

Timestamp:

Nov 11, 2016 9:57:24 PM (8 years ago)

Author:

vboxsync

svn:sync-xref-src-repo-rev:

111897

Message:

TestBoxImaging.txt: Noted down the solution for PXE showing ARP troubles during TFTPing.

Location:

trunk/src/VBox/ValidationKit/docs

Files:

• TestBoxImaging.html (modified) (1 diff)
• TestBoxImaging.txt (modified) (1 diff)

trunk/src/VBox/ValidationKit/docs/TestBoxImaging.html

@@ -678 +678 @@
 </ul>
 </blockquote>
+</div>
+<div class="section" id="troubleshooting">
+<h1>Troubleshooting</h1>
+<dl class="docutils">
+<dt><tt class="docutils literal"><span class="pre">PXE-E11</span></tt> or something like <tt class="docutils literal">No ARP reply</tt></dt>
+<dd>You probably got the TFTP and DHCP on different machines.  Try move the TFTP
+to the same machine as the DHCP, then the PXE stack won't have to do any
+additional ARP resolving.  Google results suggest that a congested network
+could use the ARP reply to get lost. Our suspicion is that it might also be
+related to the PXE stack shipping with the NIC.</dd>
+</dl>
 <hr class="docutils" />
 <table class="docutils footnote" frame="void" id="id6" rules="none">

trunk/src/VBox/ValidationKit/docs/TestBoxImaging.txt

@@ -342 +342 @@
 
 
+Troubleshooting
+===============
+
+``PXE-E11`` or something like ``No ARP reply``
+  You probably got the TFTP and DHCP on different machines.  Try move the TFTP
+  to the same machine as the DHCP, then the PXE stack won't have to do any
+  additional ARP resolving.  Google results suggest that a congested network
+  could use the ARP reply to get lost. Our suspicion is that it might also be
+  related to the PXE stack shipping with the NIC.
+
+
+
 -----