Why does anaconda fail to automated installation using kickstart in VMWare ESXI 5u3 environment for Red Hat Enterprise Linux 7.2?

Issue

• Why does anaconda fail to automated installation using kickstart in VMWare ESXI 5u3 environment for Red Hat Enterprise Linux 7.2?
• The anaconda command line used is as follows.

initrd=initrd.img inst.stage2=hd:LABEL=RHEL-7.2\x20Server.x86_64 quiet inst.ks=ftp://192.168.122.1/ks.cfg ip=192.168.122.35::192.168.122.1:255.255.255.0:testhostname:ens224:none BOOT_IMAGE=vmlinuz 

• Anaconda failed to retrieve the kickstart file itself and ended up in dracut shell generating the file /tmp/run/rdsosreport.txt.

[  141.376947] localhost dracut-initqueue[553]: Warning: dracut-initqueue timeout - starting timeout scripts
[  141.930208] localhost dracut-initqueue[553]: Warning: dracut-initqueue timeout - starting timeout scripts
[  142.462770] localhost dracut-initqueue[553]: Warning: dracut-initqueue timeout - starting timeout scripts
[  142.994735] localhost dracut-initqueue[553]: Warning: dracut-initqueue timeout - starting timeout scripts
[  143.528742] localhost dracut-initqueue[553]: Warning: dracut-initqueue timeout - starting timeout scripts
[.........................]
[  204.383844] localhost dracut-initqueue[553]: Warning: dracut-initqueue timeout - starting timeout scripts
[  204.915447] localhost dracut-initqueue[553]: Warning: dracut-initqueue timeout - starting timeout scripts
[  204.916552] localhost dracut-initqueue[553]: Warning: Could not boot.
[  204.978565] localhost systemd[1]: Received SIGRTMIN+20 from PID 557 (plymouthd).
[  205.004205] localhost systemd[1]: Starting Dracut Emergency Shell...