vcenter convertor agent - wont start, error 1053

[ukitsupportpixe]

hi all,

so im in the process of migrating my vms of xen to vcenter and so far so good on the linux machines, but windows im getting stuck

i have installed the vcenter convertor agent on the local machine and its installed but i cant get it to start in the services (see pic)

so i then changed this in the reg

also

thanks,

rob

[Scott Vessey]

Moderator: Moved to Converter Standalone

[Rosen Tomov]

See first issue here: VMware vCenter Converter Standalone 6.2.0.1 Release Notes

HTH

[ukitsupportpixe]

ive done that in my last screenshot but it doesnt work

[Rosen Tomov]

On your image ServicesPipeTimeout is 35000 which is far behind 300000 (~10 times), also you need to reboot Windows in order to take effect.

You can run service in elevated command prompt, by removing parameter '-s' from command line of the Agent service. Can you share results of such execution? Keep in mind that Agent must be run as service in order to execute privileged commands for conversion.

[ukitsupportpixe]

ok so its looking good

but now when i go on the vmware vcenter converter pc to try and convert the actual vm in question (the one that im struggling with starting the agent), it says

connecting to source machine...

permission to perform this operation was denied

[Rosen Tomov]

This is firewall problem, check the ports required and enable them.

[ukitsupportpixe]

what ports does it need?

[ukitsupportpixe]

ok its now running but im still having same problem, ie permission is denied on the vcenter converter pc

[ukitsupportpixe]

right, i have done it another way, installed vcenter standalone converter locally on the source vm and its working

[ukitsupportpixe]

great so it worked

shut down the source vm and started the dest vm and now i get a blue screen of death :smileysad:

cant even run cmd to do a repair disk

any ideas guys

[Rosen Tomov]

You can edit VM's settings and allow entering in BIOS/UEFI settings, then you can enter in repair functionality.

HTH

[ukitsupportpixe]

ok so i booted windows and went to recovery mode and started cmd, did a -

chkdsk D: /r

found no problems on the windows partition

do you think i need to change the SCSI controller to another one ie -

[Rosen Tomov]

You probably need to run bootrec/rebuildbcd in recovery mode. see https://support.microsoft.com/en-us/help/927392/use-bootrec-exe-in-the-windows-re-to-troubleshoot-startup-issues 

You need to change the controller type *before* conversion in appropriate disk-tab.

HTH

[ukitsupportpixe]

i will probably choose SATA

[Rosen Tomov]

More or less this depends on the guest OS (available drivers, ability to attach/move disk(s) to controller, etc), however you can try it.

[ukitsupportpixe]

cant find my windows installation but when i do a dir of d:\Users, i can see all my users on the pc, so i dont know why it cant find any windows installations?

[Rosen Tomov]

Instead of guessing can you upload log bundle for check?

[ukitsupportpixe]

here you go POCEH

if its not the right please let me know

[ukitsupportpixe]

quick google on this

error: class Vmacore::TimeoutException(Operation timed out)

its saying th vm helper is out of memory

[Rosen Tomov]

The timeout exception is nothing with any/helper's memory.

Also - helper iso is for Linux conversions and nothing with Windows conversions.

[ukitsupportpixe]

heres the worker

[ukitsupportpixe]

couple of errors at the bottom of the log -

ERROR 2 opening key mntApi6658894730797151\Objects\{9dea862c-5cdd-4e70-acc1-f32b344d4795}\Elements\12000002

ERROR: Error 2 reading CSDVersion value from key mntApi68987535230797151\Microsoft\Windows NT\CurrentVersion

ERROR 2 reading SP information

ERROR: Error reading from mntApi84925111230797151\ControlSet001\Services\vmxnet - 2.

ERROR 2 getting vmxnet information, assuming vmxnet is not installed

Error 2 reading 'startType' for .NET CLR Data

Error 2 reading 'Type' for .NET CLR Data

Error 2 reading string/dword value Service from Control\CriticalDeviceDatabase\primary_ide_channel

Error 2 (opening key) saving registry key mntApi95800214930797151\ControlSet001\Services\rhelfltr into \\.\vstor2-mntapi20-shared-27FACF8500004024000000000A000000\Windows\$Reconfig$\mntApi95800214930797151-ControlSet001-Services-rhelfltr-reg

[Rosen Tomov]

Not a real errors, don't breaks reconfiguration and not affects conversion.

[ukitsupportpixe]

right i did another conversion, this time i made the dest vm use IDE

it tries to boot up but goes straight to blue screen

i then went in bios changed the first boot to cd and the 2nd boot to hard drive

i loaded the windows iso and booted from that

once it rebooted i did a system recovery cmd

i made volume 1 active as this is the mbr and volume 2 is windows

also i ran this

bcdboot d:\Windows

still no joy!!!

[Rosen Tomov]

Looking again in worker's log I've found that your OS is not configured in standard way for IDE channels and probably you need to do some manual steps.

(Your IDE controller if not standard and need to be changed to the Windows' one somehow). look for Control\CriticalDeviceDatabase\primary_ide_channel and secondary_ide_channel in log

Also you need to google howto do conversion of QEMU HARDDISK to VMDK.

HTH

EDIT:

Probably not worth to remove Microsoft Hyper-V Guest Infrastructure services too.

[ukitsupportpixe]

thanks POCEH!!!!

good how to

https://chariotsolutions.com/blog/post/convert-citrix-xenserver-xva-image-to-kvm/

also as another test i installed fog, captured the source image then deployed it to a new vm and it still failed

https://fogproject.org/download

[Rosen Tomov]

I've googled "Control\CriticalDeviceDatabase\primary_ide_channel"  and found a small registry patch for (re)registering IDE adapters, as a wild guess you can try to do this patch in repair console.

HTH

[ukitsupportpixe]

do you mean this POCEH -

https://lists.xenproject.org/archives/html/xen-users/2009-09/msg00187.html

[Rosen Tomov]

Could compare with registry hack for windows vm migration · GitHub

[ukitsupportpixe]

thanks POCEH

i will make a script to add the reg keys

https://www.windowscentral.com/how-edit-registry-using-command-prompt-windows-10

[Rosen Tomov]

Ok, your source controller is IDE, why you try to change it? it is not trivial task and result is not runable VM.

2020-02-27T10:06:15.203Z info vmware-converter-worker[09004] [Originator@6876 sub=task-2] Disk: \\.\PhysicalDrive0 has adapter type IDE

2020-02-27T10:06:15.203Z info vmware-converter-worker[09004] [Originator@6876 sub=task-2] Disk: \\.\PhysicalDrive0 has serial QM00001, firmware 0.10.2, model QEMU HARDDISK

So, choose IDE for destination disk controller and try again.

HTH

[Rosen Tomov]

Unfortunately the worker's logs a more important.

[althafphussain]

Running in elevated mode will fix this issue, since i encountered similar error. Hope this helps!

[ukitsupportpixe]

you mean running the converter in elevated mode?

[Rosen Tomov]

Absolutely irrelevant comment!

[ukitsupportpixe]

i imported the reg keys (see attachment named reg)

i then restarted the vm and once restarted i started the conversion on the local machine, i chose IDE for the destination VM

it did it and i have made sure the destination is IDE (see attachment named ide)

but im still getting the blue screen

[Rosen Tomov]

What the BSOD code is? Could be happens in other place not for storage controllers...

[ukitsupportpixe]

tbh with you POCEH, i gave up and installed windows again from scratch on the new esxi server

as i spent more time troubleshooting it and in that time i coould had built tens of them lol