Hi, That behaviour is the right one, but it may not be the one you would expect... this has been discussed recently in the list.
Check these threads: http://www.mail-archive.com/users@lists.opennebula.org/msg02782.html http://www.mail-archive.com/users@lists.opennebula.org/msg02827.html Regards -- Carlos Martín, MSc Project Major Contributor OpenNebula - The Open Source Toolkit for Cloud Computing www.OpenNebula.org <http://www.opennebula.org/> | cmar...@opennebula.org On Mon, May 9, 2011 at 4:37 PM, Koushik Annapureddy <koushik1...@gmail.com>wrote: > Hello All, > > Here is the virtual network template I have used > > NAME = "VM_LAN" > TYPE = RANGED > BRIDGE = br0 > NETWORK_ADDRESS = 192.168.2.25 > NETWORK_SIZE = 50 > GATEWAY = 192.168.2.3 > > I would like to have IP address allocated to VM's which starts from > 192.168.2.26 But when I launch a VM using Open Nebula it is assigning the ip > 192.168.2.1 to the first VM and hence forth. > In the VM I have used the same context script given along with opennebula > source. > > -- > Thanks > Koushik Annapureddy > > _______________________________________________ > Users mailing list > Users@lists.opennebula.org > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > >
_______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
