Re: VR for VPC won't start anymore

2022-08-04 Thread vas...@gmx.de
hi slavka, i checked the log and didn't found anything like "failed to read from template.properties". Just for understanding: When deploying a new "systemvm"-template, which i normally would do while upgardeing mi CS-Environment, the values of the template.properties will be transfaired into DB.

Re: VR for VPC won't start anymore

2022-08-04 Thread Slavka Peleva
Hi Christopher, For some reason, these fields' values are empty, which probably happened while you seed the system VM template. > qcow2.virtualsize= > virtualsize= > qcow2.size= >From the DB record, the only option for the values of physical_size = 0 and size=Null, is that CS couldn't read the

Re: VR for VPC won't start anymore

2022-08-04 Thread vas...@gmx.de
Hi everyone - @Gary thanks for your input @Wei ZHOU Yes, the image is completely downloaded to the imagestore. I also checked the availeabilty on the storage beneath - everything seems to be in place like it should Following the values out ouf the db you requested: id= 18 store_id = 1 download_

Re: VR for VPC won't start anymore

2022-08-04 Thread Slavka Peleva
Hi Christopher, Can you share the information of the `template.properties` file located on your secondary storage, where the template file is downloaded? You can find the path in the template_store_ref tabled - install_path. Best regards, Slavka On Thu, Aug 4, 2022 at 12:41 PM Gary Dixon wrote:

RE: VR for VPC won't start anymore

2022-08-04 Thread Gary Dixon
Hi Christopher My values show : size=262144 physical size=375471104 and this is for a 4.15.1 systemVM template BR Gary Gary Dixon Senior Technical Consultant T: 0161 537 4980 W: www.quadris.co.uk The information contained in this e-mail from Quadris may be confidential and privileged for

Re: VR for VPC won't start anymore

2022-08-04 Thread vas...@gmx.de
I forgot to ask - might anyone take a quick look into the database and can give a hind if the fields are indeed "filled" with values (template_store_res.size / template_store_res.physical_size)? Another question for understanding would be the difference of the values - physical size is the actual a