cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pranav Saxena <>
Subject RE: The IPaddr parameter for vmcreate API
Date Mon, 22 Apr 2013 10:57:07 GMT
Hey Jerry,

Custom ip allocation failure leads to vm deploy failure. Happens in
following cases:
* If ipAddress doesn't exist in the network.
* If requested ip address exists in the network, but already allocated.
* If network model doesn't support custom ip allocation (see list of
cases below), the runtime exception "Does not support custom ip
allocation at this time"  is being thrown.

Custom ip allocation is SUPORTED FOR - 

* Guest Virtual Network
* Direct network in Advanced zone


* ExternalFirewall setup case. The reason for not supporting: the
original ip can be changed automatically by ExternalGuestNetworkGuru
after the vm is stopped/started.
* Basic zone - as we have 1 Global Network, but separate ip ranges per
each Pod, so the decision about which ip address to take happens after
Allocators figure out the destination Pod.
If you specify the ip address of Pod2, and allocators will pick up Pod1
- the vm creation will fail.

So you can figure out which case might explain your problem to the best extent possible.

-----Original Message-----
From: Jerry Jiang [] 
Sent: Monday, April 22, 2013 3:40 PM
Subject: 答复: The IPaddr parameter for vmcreate API

Anyone has reponsed to the issue, thanks in advance.




发件人: Jerry Jiang []
发送时间: 2013年4月18日 星期四 10:29
收件人: ''
主题: The IPaddr parameter for vmcreate API


Hello all,


I am using cloudstack API to create a VM instance. The IP address as one of parameters is
provided to API

However, I found it didn’t work well, The IP address of creating VM is not what I provided
for API.

Eg, using IP1 as the parameter, the vm operational IP addr is IP2


Why does this issue happen?




View raw message