With the new EFI firmware in the Fusion Tech Preview, all-zero network addresses appearing in the Boot Manager does not indicate a failure to acquire an IP address... it just means that a static IP address has not been configured into the boot process, and DHCP will be used instead.
I'll have the boot failure fixed as soon as I can. Thanks for reporting!
Rumor has it that you're the person who made Fusion and NetBoot play together. You (or the actual developer, if it isn't you) have greatly improved the lives of Mac admins everywhere--if there's ever any question regarding "should Fusion keep supporting NetBoot?" know that Mac admins everywhere appreciate and recommend Fusion because of the NetBoot feature.
Rumor is correct: I was the one who pushed forward the development of NetBoot-in-a-VM (including a lot of reverse-engineering and packet-capture analysis), although I was equally assisted by my awesome co-workers to get this feature into your hands, so I shan't personally claim all the credit.
There's no question about whether we'll continue to support NetBoot -- it's most disheartening that a very late change to the EFI firmware in the July Tech Preview broke NetBoot in this way. We've already fixed the problem internally.
Your positive feedback is greatly appreciated! It's awesome to hear that we're really making a difference.