Discussion moved from VMware vSphere™ to Converter Standalone
Re: VMware vCenter Converter Standalone Migration Speed
Re: VMware vCenter Converter Standalone Migration Speed
There are many factors affecting transfer speed, from the source host and its load, to the target host and its load.
What transfer speed you observe and why you think it is low?
Re: VMware vCenter Converter Standalone Migration Speed
You can easily migrate your Hyper-V VMs to VMware by using converter plugin on the vCenter server, try using the standalone converter. Treat the Hyper- V VM as a Physical VM i.e. power it on and then use the converter
Download link for converter :
Links of the KB article’s below which would help you to increase the performance of the converter and speed up the process.
Best practices for using and troubleshooting VMware Converter (1004588) | VMware KB
Disabling SSL encryption on VMware Converter Standalone 5.x and 6.0 (2020517) | VMware KB
Ref:
Re: Conversion fails at 98%
Looks like I've asked this questions before. Not exactly the same scenario as I am running VMware Converter to use it the VM within Workstation instead of ESXI but running the reconfigure task on the VMX and only leaving the last box checked did the trick. Boot sup fine now
Re: Convert virtual machine hyper-v (Windows 2012R2) to VMware
Hi guys
I have resolved the problem with a Storage Migration on Hyper-v.
I have changed the CSV where the VM running and after this the convert task not failed.
Re: FAILED: Unable to obtain the lock on virtual disks
It´s very simple: Add permission r/w for user "__VMware_Conv_SA__" to destination folder.
Getting unsupported protocol error
Converting Physical Windows Server 2012 R2 Server to ESXI Virtual Machine
Hey all.
I want to copy my existing physical server that is at my workplace to a new esxi server, now on this physical server we have lots of programs and work related stuff.
My question is will I need to do anything after the copy is complete?
As we speak I'm currently copying the server, so I've already went through the vConverter without any problems.
Will I be able to turn off the physical server and power on the new ESXI Virtual Machine and continue working as always?
Do I have to re-join the work computers to the domain?
What other steps do I have to take to be able to take down the physical server completely and start working on the new virtual machine?
Thank you.
Re: Getting unsupported protocol error
Try this solution:
Keep in mind that services need to be restarted as well as UI.
Re: Getting unsupported protocol error
I just checked, the server is ESXi 5.0.0, the standalone converter is 6.2.0, the OS of the machine to be converted/moved is Win 7 Enterprise. I have searched for the following files on my computer (which has the stand alone converter installed):
converter-server.xml Not found
converter-worker.xml Not found
converter-agent.xml Not found
converter-client.xml Found, change made, computer re-booted
Still receiving the error
Re: Converting Physical Windows Server 2012 R2 Server to ESXI Virtual Machine
VMware P2V Converter Best Practices...Pre and Post conversion checklist
Information Sharing: VMware P2V Converter Best Practices...Pre and Post conversion checklist
Re: Getting unsupported protocol error
Try to look at %ProgramData%\Vmware\VMware vCenter Converter Standalone for your "missing" xml file.
HTH
Re: Converting Physical Windows Server 2012 R2 Server to ESXI Virtual Machine
Thanks, that helped alot.
Re: VMware vCenter Converter Standalone Migration Speed
Source Host is a Dell Blade Chassis with Hyper-V on it and a total of 12 VMs .
My destination host is HPE Simplivity DL 380 Gen 9 Nodes new installation.
Re: VMware vCenter Converter Standalone Migration Speed
Hi ranchuab,
I have already tried the steps you suggested.
Could you suggest me the estimate time and best practices to migrate my file server of size 600GB from Hyper-V to VMware infrastructure.
Thanks,
Karan.
Re: Converting an encrypted LUK in Redhat P2V
This seems to work thus far. I will update once the conversion completes successfully. Thanks for the help.
Unable to convert XP to a VM.
I've got ESXi running on a server, so I'm trying to clean up some rack space. I have an old XP installation that I have to keep around for an old application we still support. So I need to get this running XP installation converted to a VM so the program can still be enhanced and compiled, etc.
But, I can never get past 1%. I keep running into:
FAILED: Unable to create a VSS snapshot of the source volume(s). Error code: 2147754776 (0x80042318).
Now, I HAVE determined that in the event viewer I do see issues with the VSS system:
Volume Shadow Copy Service error: An internal inconsistency was detected in trying to contact shadow copy service writers. Please check to see that the Event Service and Volume Shadow Copy Service are operating properly.
And, I also see some COM+ errors as well:
The COM+ Event System failed to fire the RequestWriterInfo method on subscription {F865A9A1-1E43-4688-8742-18E82CAFAFE6}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000}. The subscriber returned HRESULT C0000005.
But, it seems that all of the links to Microsoft on how to fix this are now defunct. I've found a number of things including some registry edits, stop some services and re-registering a bunch of dlls, and more... but nothing has worked. And I can't do too much to this system, because it is a living environment with all of the right drivers and configurations to build the product.
So... looking for anyone who has had the same issue. Or, is there another process that can be used to get this physical installation into a VM? I've spent the last few days trying just about everything I can think of to make this work and keep ending up back in the same spot.
Anyone got some words of help and/or wisdom?
Rich
P.S. - Attached are the diagnostics from the most recent run, if anyone wants to peruse them. Also, running the latest Converter Standalone 6.2.0 build-7348398
Re: Unable to convert XP to a VM.
Converter Standalone 6.2.0 does not support windows XP guest operating system . see below VMware vCenter Converter Standalone 6.2 Release Notes
Re: Unable to convert XP to a VM.
I see "Bitdefender Virus Shield" as VSSERV service. Disable it or uninstall it and try again.
HTH
Re: Unable to convert XP to a VM.
Should I use a different version? I really need this machine to become a VM...