Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
Sender: dcahill@midokura.jp
In-Reply-To: 
 <CANLSSBUXvchw6z3LeoinL8yO9DQPBc_8JsfWdXds6N85ERjCjA@mail.gmail.com>
References: 
 <CALFpzo7Duh9i13YaghfUfm1prh3AKHhz9nGmHirpunSbTngfAw@mail.gmail.com>
 <20130309094139.GA4496@cloud-2.local>
 <CALFpzo421m_Qbi37_p775dTWt=5eJNmhAEJKiyMqT7M2sOA5EA@mail.gmail.com>
 <CANLSSBUXvchw6z3LeoinL8yO9DQPBc_8JsfWdXds6N85ERjCjA@mail.gmail.com>
From: Dave Cahill <dcahill@midokura.com>
Date: Fri, 15 Mar 2013 15:52:34 +0900
Message-ID: 
 <CALytfWb9wTpCbHhsrRX7EMHovewhmyk5t0=4sFaMrMGB8zoQew@mail.gmail.com>
Subject: Re: devcloud-kvm updated
To: "cloudstack-dev@incubator.apache.org"
 <cloudstack-dev@incubator.apache.org>
Content-Type: multipart/alternative; boundary=f46d04308562b4a6ee04d7f11632

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

Hi Marcus,

With the recent KVM patchdisk changes in master, the old System VM template
doesn't seem to create the /dev/vport0p1 interface correctly, so it doesn't
get information on that port, and doesn't bring up the systemVM interfaces.
I'm guessing this is explained by this commit comment [1]:

"if system vm has proper driver it
will create a /dev/vport0p1 device within the VM. We will be updating the
system VM in 4.2/5.0 and will support this."

To fix this, we removed our existing System VM template and downloaded the
jenkins template you mention above, using cloud-install-sys-tmplt.

I think devs might be confused when they update to this point (system VM
interfaces mysteriously fail to come up), because changing the qcow2 in dev
generally only happens when doing a full fresh install. I wonder what we
can do to make it obvious to everyone - maybe a reminder mail to the list,
changing the recommended template link in docs etc?

Kudos on tackling the patchdisk problem by the way, I think this new system
will be a lot easier for new devs to understand. :)

Thanks,
Dave.


[1]
https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=commit;h=d81f7156dca5000e0e14a4a402c4e03a86ebbe2d


On Mon, Mar 11, 2013 at 3:23 PM, Rohit Yadav <bhaisaab@apache.org> wrote:

> Awesome, thanks Marcus!
>
> On Sat, Mar 9, 2013 at 9:33 PM, Marcus Sorensen <shadowsor@gmail.com>
> wrote:
> > The system vm template came from jenkins at
> > http://jenkins.cloudstack.org/job/build-systemvm-master/, and the
> > devcloud-kvm link is listed on the devcloud-kvm wiki.
> >
> > On Sat, Mar 9, 2013 at 2:41 AM, Prasanna Santhanam <tsp@apache.org>
> wrote:
> >> On Sat, Mar 09, 2013 at 01:29:24AM -0500, Marcus Sorensen wrote:
> >>> devcloud-kvm has been upgraded to CentOS 6.4, has new master systemvm
> >>> template preinstalled. Still getting intermittent default gateway
> >>> rules with the new systemvm (there's a bug in for it, seems to be
> >>> non-hypervisor specific) but everything seems to work :-)
> >>
> >> Great! Thanks for keeping it up to date. Is the new template published
> >> anywhere? I will use it for the devcloud-kvm CI I'm looking to set up,
> >> to save us from the blockers :)
> >>
> >> PS: Just testing out the older devcloud-ci on jenkins past few days.
> >> So we'll have both basic and advanced soon!
> >>
> >> --
> >> Prasanna.,
>

--f46d04308562b4a6ee04d7f11632--