After following the documentation here: http://wiki.cloudstack.org/display/~kdamage/CloudStack+3+and+advanced+networking http://confluence.cloudstack.org/display/~kdamage/Anatomy+of+Basic+Virtual+Networking
It seems that i would need to create the cloudVirBr<VLAN-no> bridge and associate that with a physical interface manually for the shared network. I will give it a shot and share my findings. On Fri, Aug 17, 2012 at 9:55 AM, citrix-dev <citrix-...@clogeny.com> wrote: > Hello Kelcey, > I think i have identified the issue. It seems that Cloudstack is > associating the VM's interface with a non-existent bridge cloudVirBr0 > instead of the cloudbr0 which it creates. I figured it from the virsh dump > xml : > > <interface type='bridge'> > <mac address='06:66:e4:00:00:20'/> > <source bridge='*cloudVirBr0*'/> > <target dev='vnet7'/> > <model type='virtio'/> > <alias name='net0'/> > <address type='pci' domain='0x0000' bus='0x00' slot='0x03' > function='0x0'/> > </interface> > > > I grep'ped to the cloudstack config as well as database, i cannot seem to > find any configuration pointing to *cloudVirBr0*. > > It would be great if you can share your thoughts. > > -- > Regards, Kalpak > > On Thu, Aug 16, 2012 at 12:23 AM, citrix-dev <citrix-...@clogeny.com>wrote: > >> 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 >>> >>> >> >
