Hi,
I have an installation that's been upgraded from 4.2.1 to 4.3.
In light of the heartbleed exploit, I have the need to upgrade the system
vm template.
As part of the upgrade process from 4.2.1 to 4.3, I registered and
downloaded a new system vm template, named systemvm-xenserver-4.3.
Now when
Hi,
1) Register new system vm template and change the type = “SYSTEM” in
vm_template table. (update `cloud`.`vm_template` set type='SYSTEM' where id =
)
2) Update vm_template_id = “” for all system vm entries in vm_instance
table corresponding to the hypervisor.
3) Stop start the s
Thanks for your feedback.
Still not sure what I should call it though.
Does it matter what I call it, as long as I change type in the DB?
--
Erik Weber
On Wed, Apr 23, 2014 at 8:04 AM, Harikrishna Patnala <
harikrishna.patn...@citrix.com> wrote:
> Hi,
>
> 1) Register new system vm template ##
Hari - I guess you are also supposed to delete the old systemvm template
by marking it removed in the DB.
Also how would stop/start pick the new template ? I would say just destroy
them. Does heart bleed affect VR ?
On 22/04/14 11:04 PM, "Harikrishna Patnala"
wrote:
>Hi,
>
>1) Register new syst
Don't know about VR but it does affect ssvm (download service).
So, should i start by marking the old as removed (what happens with the
files Then?), and Then add the new?
Erik Weber
23. apr. 2014 19:52 skrev "Nitin Mehta" følgende:
>
> Hari - I guess you are also supposed to delete the old sys
