I kind of doubt that the new systemvm.iso will be propagated to the sec. storage. You can always follow the process in the wiki [1] to propagate the new iso which will contain your code change.
[1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/SystemVm.iso#SystemV m.iso-VMWare Thanks, -Nitin On 09/12/14 8:15 AM, "Mike Tutkowski" <mike.tutkow...@solidfire.com> wrote: >Thanks, Sateesh! > >On Monday, December 8, 2014, Sateesh Chodapuneedi < >sateesh.chodapune...@citrix.com> wrote: > >> > -----Original Message----- >> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com >><javascript:;> >> ] >> > Sent: 09 December 2014 05:41 >> > To: dev@cloudstack.apache.org <javascript:;> >> > Subject: [Question] System VM >> > >> > Hi, >> > >> > I was wondering, I changed code related to copying a template down to >> primary storage from secondary storage. This code - related >> > to ESXi - gets run in the SSVM. >> > >> > Is it sufficient if I rebuild the codebase using the systemvm profile, >> destroy my SSVM, and allow a new one to be created? Does this >> > kind of code get applied to system VMs are a patch as part of >> systemvm.iso? >> Yes, that should be sufficient. >> Just make sure there is no stale systemvm.iso in systemvm folder of the >> secondary storage share in the zone. >> >> Regards, >> Sateesh >> > >> > The way I've tested this kind of code to date is by putting a >>breakpoint >> in VMwareGuru and redirecting the command to run in the >> > management server instead of in the SSVM. >> > >> > Thanks! >> > >> > -- >> > *Mike Tutkowski* >> > *Senior CloudStack Developer, SolidFire Inc.* >> > e: mike.tutkow...@solidfire.com <javascript:;> >> > o: 303.746.7302 >> > Advancing the way the world uses the cloud >> > <http://solidfire.com/solution/overview/?video=play>** >> > > >-- >*Mike Tutkowski* >*Senior CloudStack Developer, SolidFire Inc.* >e: mike.tutkow...@solidfire.com >o: 303.746.7302 >Advancing the way the world uses the cloud ><http://solidfire.com/solution/overview/?video=play>**
