Comment 4 for bug 564355

This also Effects 1.6.2 CentOS release. When ADDRPERNET is set to 256 it causes same behavior with this error:

[Wed Aug 11 08:22:12 2010][005109][EUCADEBUG ] RunInstances(): params: userId=admin, emiId=emi-54A01BEF, kernelId=eki-5A861EB7, ramdiskId=UNSET, emiURL=http://192.168.1.11:8773/services/Walrus/x86_64-CentOS-5.4/managed-public-nil-nil-x86_64-CentOS-5.4-v1.2-2.0.manifest.xml, kernelURL=http://192.168.1.11:8773/services/Walrus/Kernels-x86_64/nil-public-nil-nil-x86_64-vmlinuz-2.6.18-xenU-ec2-v1.2-1.0.manifest.xml, ramdiskURL=UNSET, instIdsLen=1, netNamesLen=1, macAddrsLen=1, networkIndexListLen=1, minCount=1, maxCount=1, ownerId=admin, reservationId=r-43C4087C, keyName=, vlan=10, userData=, launchIndex=0, targetNode=UNSET
[Wed Aug 11 08:22:12 2010][005109][EUCADEBUG ] RunInstances(): running instance i-3816057B with emiId emi-54A01BEF...
[Wed Aug 11 08:22:12 2010][005109][EUCAERROR ] vnetAddHost(): failed to add host d0:0d:38:16:05:7B on vlan 10
[Wed Aug 11 08:22:12 2010][005109][EUCADEBUG ] RunInstances(): assigning MAC/IP: d0:0d:38:16:05:7B/0.0.0.0/0.0.0.0/5
[Wed Aug 11 08:22:12 2010][005109][EUCAERROR ] RunInstances(): could not find/initialize any free network address, failing doRunInstances()
[Wed Aug 11 08:22:12 2010][005109][EUCADEBUG ] RunInstances(): done