VMware Cloud Community
Atko
Enthusiast
Enthusiast

Issue when importing machine using VM Convertor

Get the following error message in Virtual Center when running VMWare converter to convert a physical machine to virtual.

Name: Create Virtual Machine

Status: Number of virtual devices exceeds the maximum for a given controller.

I have successfully used the VMWare Converter to migrate other machines.

Reply
0 Kudos
17 Replies
Guyver
Contributor
Contributor

Hi there. I just experienced the same problem with the Converter. My issue was resolved with rebooting the server. It seems that the Vmware Converter does not always or necessarily reboot the server you are converting. So I assume this has something to do with the Vmware UFAD service. When I rebooted my server and edited the configuration to run again all went smoothly. Hope this also works for you. I only experience this problem when coverting Windows 2003 machines.

Reply
0 Kudos
az-ueli
Contributor
Contributor

i have the same problem, i will try it with the reboot of the server.

thanks

steven

Reply
0 Kudos
chouse
Enthusiast
Enthusiast

Reply
0 Kudos
mhanson
Contributor
Contributor

i just had this happen to me today. unfortunately cannot access the link you have provided...gives me an access is denied.

Reply
0 Kudos
indymacbank
Contributor
Contributor

Same here... i have a support call open now, i'll try and post my findings once i'm done.

Reply
0 Kudos
acr
Champion
Champion

Yep, definately get permission denied..

I believe its out of beta now..

http://www.vmware.com/download/converter/

Reply
0 Kudos
kevingj
Contributor
Contributor

Come VMware please post some comments to this problem I have tried everything I know.

This problem seems to be knocking around for quite some time now.

Reply
0 Kudos
mstahl75
Virtuoso
Virtuoso

Is your problem still happening with the GA release of Converter?

Reply
0 Kudos
indymacbank
Contributor
Contributor

Yes this is with the new release of Converter. The case is still open with VMWare. The tech i talked to said there where a bunch of bugs it could have been in that forum post above. I wanted to have him give me the info in there but he wanted me to send in the logs and everything first, so much for fixing it myself.

Just makes me mad that this is supposed to be the release version and bugs from the beta still weren't fixed.

Reply
0 Kudos
itcs_dts
Contributor
Contributor

Anyone else found a resolution to this issue? I've got exactly the same problem when trying to convert a physical mahcine to an ESX Server.....

TIA

Adie

Reply
0 Kudos
kevingj
Contributor
Contributor

Yes we have had many failures with the same errors as above, went back to using P2V Assistant and Ultimate P2V very tools. VMware converter does look very good though and has successfully P2V machines without any problems. once the errors are fixed we will be using in anger.

Reply
0 Kudos
ploleary
Contributor
Contributor

Hey all, had this issue with my citrix server testing. Found this answer here:

Hope this all helps.

http://www.vmware.com/community/thread.jspa?messageID=564294򉱆;

One thread mentions this happening on a PC with Citrix installed. And that "Deleting the CcmPort3 thru CcmPort9 registry entries allowed the migration to complete".

Also in that thread is mentioned the following (how to actually DO the above):

Regarding the # of devices exceeding the max:

1) On the source host, open regedit

2) Navigate to HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\SERIALCOMM

3) Export the key for backup-archive-restore purposes

4) Delete CcmPort3 thru CcmPort9

5) Retry the migration

And retry with a different import name:

http://www.vmware.com/community/thread.jspa?threadID=70631

Message was edited by:

ploleary

Reply
0 Kudos
Acts-ssc
Contributor
Contributor

Has anyone got an answer to this problem. I have tried all of the ideas here with no luck. I also noted that ion the log files there was an issue with VSS I set that to manual. I am now getting tyhe same error with win 2000 boxes and any box with Citrix running...

Any help would be greatful

Anthony

Reply
0 Kudos
admin
Immortal
Immortal

Import to the ESX Host and Not VC.

Reply
0 Kudos
Rumple
Virtuoso
Virtuoso

I've resolved this error in the past by making sure all Serial port, parallel port and USB devices were disabled in the BIO and then removed from the O/S and then importing.

Worked fine for me after that. Only ones that are a problem are ones with logs of disks on them

Reply
0 Kudos
ealaqqad
Enthusiast
Enthusiast

If trying to convert to the host server directly instead of VC did not fix it, then you might want to try the resolution at my post:

UFAD Service is not running

I hope that help you fix it, if so please reward points,

Eiad Al-Aqqad

System X & Storage Technical Specialist

Virtualization Team Blog

Regards, Eiad Al-Aqqad Technology Consultant @ VMware b: http://www.VirtualizationTeam.com b: http://www.TSMGuru.com
Reply
0 Kudos
MauroBonder
VMware Employee
VMware Employee

ckeck it

**If you found this information useful, please consider awarding points for

"Correct" or "Helpful"**

*Please, don't forget the awarding points for "helpful" and/or "correct" answers. *Por favor, não esqueça de atribuir os pontos se a resposta foi útil ou resolveu o problema.* Thank you/Obrigado
Reply
0 Kudos