Seconds field of DHCP Discover message not set?

I have a KVM sytem (RHEL6.1, qemu-0.12.1.2, seabios-0.6.1.2, gpxe-0.9.7, 
virtio bridge interfaces) where we are trying to PXE boot the guest OS.

It does not appear that the seconds field of the DHCP Discover message 
is being incremented (it is always set to 0).  The DHCP server is not 
connected locally and the DHCP request is not being forwarded to the IP 
helper device (DHCP server) unless the forward delay time is set to 0 on 
the local switch (Omni-switch compares this delay time to the seconds 
field of the DHCP request and only forwards the request if the seconds 
field is >= the delay time).

Depending upon the configuration of the other machines in this local 
network, there may or may not be a DHCP server active to service this 
system.  We would like the local server to reply if it is configured, or 
else have it forward to the higher level server (which the delay timer 
works nicely for).

I have seen this problem on an older version of gPXE, and I have tried 
the newest version (1.0.1), and am seeing the issue in all of the versions.

Does anyone have any experience with this?

Thanks,
Kenton Cabiness

------------------------------------------------------------------------------
Magic Quadrant for Content-Aware Data Loss Prevention
Research study explores the data loss prevention market. Includes in-depth
analysis on the changes within the DLP market, and the criteria used to
evaluate the strengths and weaknesses of these DLP solutions.
http://www.accelacomm.com/jaw/sfnl/114/51385063/