I had the same problem, at the end I had to shutdown MS, then destroy the .vhd file that was created by the CS in the local storage of the clusters it used to start system vms. Then, you just need to start MS, and destroy the system vms that were already created. I was using Xen.
On Tue, Jul 8, 2014 at 12:56 AM, Carlos Reátegui <create...@gmail.com> wrote: > What is your environment? i.e. what management server os and hypervisors > are you using? > > > On Jul 7, 2014, at 6:42 PM, Nick Wales <n...@nickwales.co.uk> wrote: > > > I upgraded following the guide exactly. > > > > > https://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.1/html/Release_Notes/upgrade-instructions.html#upgrade-from-4.1-to-4.2.1 > > > > Everything went fine until running the script to restart the system VM's. > > > > cloudstack-sysvmadm -u cloud -p <password> -a > > > > > > The console vm restarted but the agent stayed disconnected. The SSVM > failed > > to restart, the VR restarted ok. > > > > I couldn't work out why the agent wouldn't connect so decided to destroy > > console and SSVM's so they would come back happy as they usually do. > > > > They didn't come back. Now my secondary storage is showing up as 0KB in > > size, and the system templates status is 'No space left on device' so I > > can't start any new systemvm's. > > > > I don't know where to begin to fix this, any ideas? > > -- Rafael Weingärtner
