Sorry...I should have mentioned this is 4.4. So, in this case, SSVM is actually running on XenServer; however, the user VM that is the beneficiary of the CopyCommand is running on VMware.
On Fri, Apr 18, 2014 at 12:04 AM, Amogh Vasekar <amogh.vase...@citrix.com>wrote: > Hi, > > Which CloudStack version is it? > AFAIK for vmware - deleting systemvm.iso from the secondary storage for > your VMWare zone, and restarting management server and SSVM should do the > trick. > > Thanks, > Amogh > > On 4/17/14 10:55 PM, "Mike Tutkowski" <mike.tutkow...@solidfire.com> > wrote: > > >Hi, > > > >I was debugging storage code for ESXi that runs in SSVM (a CopyCommand). > > > >I needed to make a change related to managed storage. > > > >I made the change, rebuilt the codebase, and have been trying various ways > >of getting that code into SSVM, but SSVM seems to have the older code > >still. > > > >In this situation, my SSVM is actually running on a XenServer host. > > > >Can someone provide me with the procedure to update the code that's > >running > >in SSVM on XenServer? > > > >I tried to scp the systemvm.iso file from where it was built to the > >XenServer host and then re-start SSVM, but that didn't seem to do the > >trick. > > > >Thanks! > > > >-- > >*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> > >*(tm)* > > -- *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> *(tm)*
