Hello, This is more of a general question pertaining to best practices of how everyone works with multiple ESX hosts in a cloudstack zone. It seems that if a VM instance resides on a different host from other instances, there is no networking ability on the alienated instance(s). Since the hosts are chosen automatically, occasionally instances are created on an alternate host and the instance boots up without networking. Adding a tag in the computer offering is a way of forcing instances to be created on a particular hosts, though that requires additional offerings for every host.
Using a dvSwitch would be great, though on 4.0.2 I do not believe it is supported or I am unable to find any documentation to prove me otherwise. What is the best practice or workaround for this? - Stan
