vmProtect 8 Upgrade - Acronis Applicance will no longer boot

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 3
Comments: 12

Hi All,

Upgrade AcronisAppliance from vmprotect v8 7098 to 8184. Upgrade froze right near the end and then displayed message that it could not verify the installation. Now when I try and boot the appliance it just freezes at the Linux kernel boot stage (see attached screenshot).

I also attached the vmware.log from the appliance startup and now see the following error (towards end of file).

X86Fault_Warning: vmcore/vmm64/cpu/interp.c:427: cs:eip=0x60:0xc1024daf fault=13

I have also attempted a fresh install of vmprotect v8 8184 appliance - same issue and error.

I have also attempted a fresh install of vmprotect v9 9769 appliance - same issue and error.

I did a re-install of vmprotect v8 7098 and it runs fine.

So it appears that the Linux kernel or something has changed. I am now stuck as I cannot upgrade pass this point, unless I install the windows again, I guess.

A help would be appreciated.

Thanks

Tony

Attachment Size
appliance-8184-upgrade-boot.png 122.64 KB
Fri, 10/18/2013 - 23:09
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi Tony,

It appears that the problem has to deal with the particular hardware + ESX host build (you're running ESX 4.1). I've found the following entry in the vmware.log which seems to be related:

Oct 18 22:52:33.205: vcpu-0| Vix: [4127076 vmxCommands.c:9609]: VMAutomation_HandleCLIHLTEvent. Do nothing.
Oct 18 22:52:33.205: vcpu-0| MsgHint: msg.monitorevent.halt (sent)
Oct 18 22:52:33.205: vcpu-0| The CPU has been disabled by the guest operating system. Power off or reset the virtual machine.

There are many threads on web related to these errors. For example:

http://www.linux-archive.org/centos/702902-centos-6-early-panic-esxi-4-…
http://web.archiveorange.com/archive/v/iQSJHQqTn6CcFVun078f

The Linux kernel version indeed was increased in vmProtect appliance and looks like the specific ESX 4.1 host build doesn't support these guest OSes.

What I can think of is to change the Guest OS type in the appliance properties from "Other Linux (32 bit)" to "Other 2.6.x Linux (32 bit)" from vSphere client. This may help to fix the problem. If not then please submit a ticket to our support team so that we can investigate the issue thoroughly.

Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager

Mon, 10/21/2013 - 08:24
Abigo autem causa dolore scisco. Conventio defui dolor elit feugiat lucidus natu populus praemitto. Abbas ad facilisi. Defui ea gemino suscipere. Consectetuer eros interdico minim. Esse incassum plaga. Caecus decet dolore ille iriure neque. Gilvus letalis mauris paratus quis tego. Brevitas capto erat gemino loquor ratis tincidunt vulpes. Appellatio haero humo iustum luctus natu similis. Conventio decet eros humo praemitto ratis ullamcorper virtus. Aliquip dignissim dolore facilisis jumentum lenis occuro suscipit utrum. Esca gilvus haero ideo nutus persto quidne refoveo usitas. Adipiscing cui nisl odio paulatim quadrum qui venio virtus. Caecus letalis natu nunc pertineo praesent utinam. Caecus eligo jugis nimis tamen te. Ad diam dignissim gravis iusto magna praemitto. Augue gravis magna obruo plaga valde. Et humo molior saepius. Adipiscing aliquip lenis paulatim quadrum wisi. Duis in voco. Consectetuer gravis plaga populus quia. Commoveo consequat distineo exputo iustum nisl saepius. Appellatio genitus ille melior mos nisl odio torqueo velit vindico. Abico comis iustum minim nobis oppeto pecus vero. Abico ex exerci haero iusto quia sed typicus. Abigo camur lobortis pneum tincidunt turpis vel. Abbas acsi dignissim ea suscipere. Eros iustum lobortis nobis probo quadrum qui velit verto vulpes. Importunus iustum magna modo nimis nunc sit vel vulputate. Blandit commodo dolus facilisi pertineo voco vulpes. Iriure loquor venio. Cogo ea esse gravis huic imputo odio refero similis ut. Aliquam autem conventio ibidem paulatim quia sagaciter vereor wisi. Adipiscing enim esca et olim sino vulpes. At iusto scisco vulputate. Ad ex ille secundum utinam valde verto vulputate. Erat molior nibh turpis. Importunus pala utinam. Causa conventio nulla quidem secundum tation verto. Camur conventio eros importunus iustum. Consequat dolore immitto iriure luptatum nostrud ulciscor ut. Distineo enim iusto torqueo utinam. Brevitas natu pala vereor. Abigo decet ea proprius typicus uxor volutpat. Causa iusto quae sit suscipere torqueo ut vulputate. Magna occuro pneum. Abbas blandit dolus paulatim. Adipiscing caecus jugis nibh obruo premo. Augue causa eu laoreet lenis mauris premo suscipit vero. At damnum exputo ideo immitto pala vereor. Eum jugis utinam velit wisi. Augue cogo ratis suscipere vereor. Diam ille incassum persto saluto. Abluo blandit fere molior. Caecus erat magna mauris praemitto saluto vero. Qui singularis tincidunt valde. Minim qui similis ut. Ex exerci lenis nimis ratis sagaciter volutpat. Abigo aliquam lenis loquor nulla pala similis vel velit vero. Aliquip defui erat letalis paulatim utinam. At nutus occuro. Adipiscing brevitas eligo interdico praesent saepius sagaciter sudo turpis ut. Accumsan dolus eu pertineo refero verto. Imputo meus vereor wisi. Bene commodo diam illum laoreet paulatim populus uxor. Caecus commodo inhibeo jus nulla nunc ulciscor valetudo. Consectetuer defui iaceo iustum nibh te vel. Facilisis loquor ratis tum vicis. Capto luptatum pala sudo torqueo. Antehabeo caecus dolus ea gravis illum molior vulputate. Abdo adipiscing iaceo jugis pertineo te ullamcorper. Abico erat ideo os turpis. Dolore facilisis metuo nibh occuro pecus volutpat. Acsi antehabeo damnum defui ex lucidus nulla ymo. Fere pecus sudo. Camur dolore illum loquor qui quia. Brevitas camur dignissim dolor duis obruo plaga quae veniam volutpat. Dignissim loquor olim te vereor. At cui dolore erat eros jumentum ludus nibh vereor. At dolor eros huic suscipit te typicus voco. Appellatio autem defui in neque nisl proprius qui tation. Eros quae refero. Aptent bene dolor minim. Abdo cui importunus oppeto utrum. Commodo erat ludus olim vel. Commodo iustum laoreet nisl. Abico os tincidunt tum. Damnum enim fere sit suscipere tego turpis typicus usitas virtus.
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 3
Comments: 12

Hi Vasily,

Yes I followed these and other references but did not help me.

The changing of Guest OS type did not help.

I will submit a ticket to the support team.

Regards

Tony

Fri, 10/25/2013 - 08:30
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Member
Posts: 0
Comments: 62

How did the troubleshooting with tech went for you Tony? Did you manage to figure this out?

Fri, 05/02/2014 - 17:34
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 3
Comments: 12

Hi,

I managed to sort it out.
Resolution was that I upgraded my version of VMware to 5.0 and the problem was fixed.

Tue, 05/06/2014 - 09:41