On 10/31/2014 04:56 PM, Michael Brown wrote:
However, if the problem is caused by packets arriving during the
Windows driver start-up, then this fix would only make the problem
less likely to occur; it wouldn't eliminate it. A random packet
arriving at a bad time (e.g. a totally unrelated ARP request, NetBIOS
name announcement, etc) could still trigger the problem.
It would be interesting to know if you can reproduce the problem even
in your "fixed" build by sending frequent packets (e.g. flood pings
with a manually created ARP cache entry) from the iSCSI target during
the boot.
Flood pinging with static ARP entry does not seem to affect installation
(when using ipxe with patches reversed) at all.
Like virtualbox is only allergic to receiving retransmits at the wrong
moment for some strange unknown reason.
(in the case of "resetting" the VM at the wrong time when windows has
its long wait, shortly after reboot, while starting ipxe, it receives a
retransmit of an iSCSI NOP command from SAN to iPXE).
Yours sincerely,
Floris Bos
_______________________________________________
ipxe-devel mailing list
[email protected]
https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
