top posting sorry: If anyone is testing upgrade paths to 4.3, please do check the release notes:
http://apache-cloudstack-release-notes.readthedocs.org/en/latest/ And send any patches to correct them (edit on github button on the top right of the page) thanks, On Mar 18, 2014, at 6:15 AM, Marcus <shadow...@gmail.com> wrote: > I never did get an answer as to how those upgrade instructions are supposed > to work. I did however look at the code and we came up with our own > procedure. It's a bit messy because it involves changing the db, use at > your own risk. > > 1. Make changes to system vm template. save as systemvm-ver<num>.qcow2 and > upload to a place that the ssvm will be able to reach (e.g. > http://something.com/template). > 2. Register new qcow2 template in cloudstack under the name/description > “SystemVM Template v<num> (KVM)”, with Debian 7 as the type. > 3. Log into mysql for the cloudstack install, find the template, make note > of template id: > mysql > use cloud; > select * from vm_template where name="SystemVM Template v2 (KVM)"; > 5. Update the template to be a SYSTEM template:mysql update vm_template set > type='SYSTEM' where id=<id>; > ▪ New system vms will now use this template simply because it's the highest > ID SYSTEM template for KVM. Existing system vms will either need to be > destroyed/recreated, or updated in the db and rebooted if you have > systemvm.recreate.enabled=true in global settings. Here's how to update so > that existing system vms will get the new template when rebooted:mysql > update vm_instance set vm_template_id='<new template id>' where > vm_template_id='<old template id>'; > If you are unsure of the latest, you can check for the latest template in > use via: > > mysql > select * from vm_instance where name like 'r-%' order by id desc limit 1; > > Finally, go into cloudstack's global config and change the value of > router.template.kvm to be the name of your system vm template (e.g. > “SystemVM Template v2 (KVM)”). This will ensure new routers use the > template. > > > > On Mar 17, 2014 8:19 PM, "Yichi Lu" <yichi...@sungard.com> wrote: > >> I have a problem that bothers me to no end. >> I tried to upgrade from CloudPlatform 4.2.0 to CloudStack 4.3.0. So I first >> registered a 64-bit 4.3.0 systemvm template from: >> >> http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14-master-xen.vhd.bz2 >> >> this step was successful. So now I have TWO active systemvm templates. This >> can be verified from vm_template table. If now I upgrade the rpm packages >> to cloudstack 4.3.0 from CloudPlatform 4.2.0, and restart >> cloudstack-management service, I always get a 32-bit ssvm: >> root@s-1-VM:~# uname -a >> Linux s-1-VM 3.2.0-4-686-pae #1 SMP Debian 3.2.41-2 i686 GNU/Linux >> >> I was never able to run a 64-bit ssvm for CloudStack 4.3.0. >> >> Any suggestions/thoughts? >> >> Yichi >>
