Prasanna, This is correct, an upgrade to 4.2 or whatever will require upgrading the system VMs. I mentioned/inquired on this in another thread, and it seemed like the we were going to require a system VM upgrade. I wanted to make sure this change was ok. Chiradeep said there was a procedure for it.
On Fri, Mar 15, 2013 at 1:09 AM, prasanna <t...@apache.org> wrote: > Since we are now patching via socket, will the older system vm > template still work? Or will upgraded deployments have to seed the new > template, destroy systemVMs and have the new ones come up? > > On 15 March 2013 12:22, Dave Cahill <dcah...@midokura.com> wrote: >> 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 <bhais...@apache.org> wrote: >> >>> Awesome, thanks Marcus! >>> >>> On Sat, Mar 9, 2013 at 9:33 PM, Marcus Sorensen <shadow...@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 <t...@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., >>>
