Hello Kelcey, Thanks for the quick response. I create the additional guest network and the another network interface gets added to the VM, although the VM isnt accessible from either of the interfaces. On accessing the VM from the console, i cannot seem ping anyone outside.
The default gateway in the route table is to the router-instance (r-2-xxx). I seem to be missing something. Please let me know. -- Regards, Kalpak On Wed, Aug 15, 2012 at 11:42 PM, Kelcey Damage (BBITS) <kel...@bbits.ca>wrote: > Create a shared network with that IP range, then when you create(instance) > the VMs add both networks to the instance and it will come up with 2 > interfaces, one on each network. > > Kelcey Jamison-Damage > Infrastructure Systems Architect > > Backbone Technology | Backbone Datavault | Backbone IT Services > 55 East 7th Ave Vancouver - BC Canada V5T 1M4 > kel...@bbits.ca | 604-331-1152 ext. 114 > > -----Original Message----- > From: chi...@clogeny.com [mailto:chi...@clogeny.com] On Behalf Of > citrix-dev > Sent: Wednesday, August 15, 2012 11:01 AM > To: cloudstack-dev@incubator.apache.org > Subject: Spawning VMs in bridged mode on KVM ( Cloudstack 3.0.2) > > Hello, > We have a KVM-based setup with the following configurations: > Private Network : 10.88.88.0/28 > Public Network: 108.x.x.x/24 > > Each KVM host has a statically assigned IP Address to it from the > 10.88.88.x > pool. 10.88.88.1 is the default gateway which is used to route traffic to > the external world. The VMs that we spawn via Cloudstack come-up fine on > the > 10.1.1.x Cloudstack network. But we would like to have the 10.88.88.x > network-based IP addresses assigned the VMs as well. i.e bridged mode. > > Is it possible to achieve the same? or will the VMs always come-up on the > 10.1.1.x network *only* ? > > -- > Regards, Kalpak > >
