Skip to main content

Run VM from backup and then Storage VMOtion on ESX5 fails

Thread needs solution

Hello,

I am testing vmProtect 8 (latest build)

Running VM from backup and then Storage VMOtion on ESX5 fails

With not a clear error.

See attached.

Attachment Size
test1.png 2.75 KB
test2.png 19.65 KB
0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi Jeremy,

There was such issue in vmProtect 8 which caused the vmkernel to dump when trying to vMotion of VM ran from backup (our mounted VM missed one parameter in .vmx which caused such behavior). We have fixed it in the 9th version. You can verify this issue with vmProtect 9 Beta to confirm that it works.

P.S. (just for record) internal bug ID: AVMPIX-1134

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

It seems to fail at the very last process.... vmotion part of migrating the VM state...

Logfiles of vmprotect are attached.

Attachment Size
135739-108697.zip 1.47 MB
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi Jeremy,

In addition to my previous post:

The missing parameter is in .vmdk file (the virtual disk descriptor which can be downloaded via datastore browser accessible through vCenter/ESXi host web interface):

ddb.adapterType = "lsilogic"

If you add this parameter to corresponding .vmdk of the mounted VM then it should be vMotioned properly.

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

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi Jeremy,

It is .vmdk but not the large one (which contains data) - you should check the small .vmdk which has the same name and doesn't appear in standard datastore browser (from vSphere Client).

You can check it via Internet browser at https://[IP]/folder URL, where [IP] is vCenter or ESXi IP. This will redirect you to datastore browser. See attached screen shot where I show the difference. The modified .vmdk can be put back via SSH client connected to the host.

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

Attachment Size
135746-108703.png 149.64 KB
135746-108706.png 44.39 KB
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Yes, exactly! :)

You can read more at the following VMware KB article: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cm…