DHCP, TFTP and kernel image transfer.. from server.. over lan.. works without any issue.

No loadable modules or initrd.. all drivers built into the kernel.

The client has two ethernet devices.. one facing the lan and one facing the wan (client is to be the iptables nat/snat router).

If I declare both device drivers in the kernel config, my kernel loading just stops.. due to lan facing device going down (presumably.. I notice from kernel messages that the wan facing device gets a dhcp address from my internet provider's server, and.. possibly.. does not continue to do so from my dhcp server for the lan facing device).

If I declare only the lan facing ethternet device driver in the kernel.. all is well with the booting process.. (successful virt shell prompt).

I am not yet aware of how to capture the kernel boot process log, but working on it at this moment (dmesg isn't activated until after a successful kernel loading).

I believe that I need to better specify the kernel command line parameters for an nfsroot kernel so that the lan facing iface is not killed in the process.

I did not know that.. very good. Do you happen to have any references handy for that? If not no problem I'll end up google searching it. Thanks for your input.. you're first post was very interesting.. i've bookmarked it for future deep kernel endevours.. _________________ProDataLab.com -- A Focus On Efficiency