Return-Path: 
 <cloudstack-dev-return-4085-apmail-incubator-cloudstack-dev-archive=incubator.apache.org@incubator.apache.org>
X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org
Delivered-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 6B31FDD59
	for <apmail-incubator-cloudstack-dev-archive@minotaur.apache.org>;
 Fri, 17 Aug 2012 04:26:08 +0000 (UTC)
Received: (qmail 74421 invoked by uid 500); 17 Aug 2012 04:26:07 -0000
Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org
Received: (qmail 74304 invoked by uid 500); 17 Aug 2012 04:26:04 -0000
Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:cloudstack-dev-help@incubator.apache.org>
List-Unsubscribe: <mailto:cloudstack-dev-unsubscribe@incubator.apache.org>
List-Post: <mailto:cloudstack-dev@incubator.apache.org>
List-Id: <cloudstack-dev.incubator.apache.org>
Reply-To: cloudstack-dev@incubator.apache.org
Delivered-To: mailing list cloudstack-dev@incubator.apache.org
Received: (qmail 74241 invoked by uid 99); 17 Aug 2012 04:26:02 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Aug 2012 04:26:02 +0000
X-ASF-Spam-Status: No, hits=2.2 required=5.0
	tests=HTML_MESSAGE,NORMAL_HTTP_TO_IP,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL
X-Spam-Check-By: apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Received: from [209.85.161.175] (HELO mail-gg0-f175.google.com)
 (209.85.161.175)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Aug 2012 04:25:54 +0000
Received: by ggmq1 with SMTP id q1so4013624ggm.6
        for <cloudstack-dev@incubator.apache.org>;
 Thu, 16 Aug 2012 21:25:33 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=google.com; s=20120113;
        h=mime-version:sender:x-originating-ip:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:cc:content-type
         :x-gm-message-state;
        bh=i4kC8ys8Fnpabr1JeeKIsfDijc5jbMYlvF0f3MY40Fs=;
        b=MlzQXIl89c5QKs+7yalSP/J2Qf4Rohz44vsB86GNeyVEEnNxfxtqVOPfRsKFY5Pm0D
         GgFPH/wlEo2i2weXdiTUPv/STYEQRT9pu7Xemlf3XdpTh2yLSM0jtZzZnZMNizbM04KJ
         1GREs2D1u9M82f3BZvVx2yVjYruCC3buWGwHT4Q93lPYG+2zFY3Fjw0aFtFZI5fIkurW
         XvPcPvVBztjiTaaSvF1TFfsGMOS4LO/KkiIZOaiAOKKlHl1JHNUJbO0u92pe4R4/QiGB
         IXvCJeFP9LlVge/guWa6lZrvi3A8HdJuPh8wsyqoyp3sUPExADFGmYZnHqRe4pe8AEHj
         f2zQ==
MIME-Version: 1.0
Received: by 10.50.94.195 with SMTP id de3mr439906igb.68.1345177532377; Thu,
 16 Aug 2012 21:25:32 -0700 (PDT)
Sender: chirag@clogeny.com
Received: by 10.42.76.68 with HTTP; Thu, 16 Aug 2012 21:25:32 -0700 (PDT)
X-Originating-IP: [223.230.128.200]
In-Reply-To: 
 <CADRU-YA0ZV+kN4t1E-Jp9PFLbyXoqS88RVEbp+FtS1W1jmCcWQ@mail.gmail.com>
References: 
 <CADRU-YB6vKcqHf_7BV2Q52pE-BJR=8rmEzPPfXufQi086mWi7A@mail.gmail.com>
	<021301cd7b11$88db0d10$9a912730$@bbits.ca>
	<CADRU-YA0ZV+kN4t1E-Jp9PFLbyXoqS88RVEbp+FtS1W1jmCcWQ@mail.gmail.com>
Date: Fri, 17 Aug 2012 09:55:32 +0530
X-Google-Sender-Auth: uimxKuwCZgFdUDU9WuOcasC7tQw
Message-ID: 
 <CADRU-YALbggBZwJLHtpeW3J1Q_pikEmoqbRsaStdJO9GCL1gng@mail.gmail.com>
Subject: Re: Spawning VMs in bridged mode on KVM ( Cloudstack 3.0.2)
From: citrix-dev <citrix-dev@clogeny.com>
To: kelcey@bbits.ca, cloudstack-dev@incubator.apache.org
Cc: Prasanna Citrix <prasanna.santhanam@citrix.com>
Content-Type: multipart/alternative; boundary=e89a8f235443fa29fe04c76e8c52
X-Gm-Message-State: 
 ALoCoQmFGwN2uO5cPi9NWNbywwaFjuULjurQ5bd8B7ZvFTj8qaLbXFWBzjsUZHlfUIVF6uFMOc12

--e89a8f235443fa29fe04c76e8c52
Content-Type: text/plain; charset=ISO-8859-1

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-dev@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) <kelcey@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
>> kelcey@bbits.ca | 604-331-1152 ext. 114
>>
>> -----Original Message-----
>> From: chirag@clogeny.com [mailto:chirag@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
>>
>>
>

--e89a8f235443fa29fe04c76e8c52--