andoven
Contributor
Contributor

Error using VMconverter to import vm from vm-workstation to esx

I am recieivng the error 'GetResult failed: vim.vm.device.VirtualVMIROMOption' in the converter log while trying to import a vm from VM Workstation v6.5 to ESX 3.5. THe log is below:

Connected to stream:

Unsetting unknown path: /vmomi/

Authenticating user root

Logged in!

GetResult failed: vim.vm.device.VirtualVMIROMOption

============BEGIN FAILED METHOD CALL DUMP============

Invoking on

Arg key:

Arg host:

Fault has an empty message

============END FAILED METHOD CALL DUMP============

Shutting down VMDB service...

Unregistering callback...

...done

VmiImportTask::task step "create VM" 100% completed VmiImportTask::task step "create and clone to VM" 5% completed

VmiImportTask::task step "Clone VM" 5% completed VmiImportTask::task step "create VM" destroyed

Error during creation of target VM

VmiImportTask::task step "create and clone to VM" 100% completed VmiImportTask::task step "Clone VM" 100% completed

VmiImportTask::task step "create and clone to VM" destroyed VmiImportTask::task step "Clone VM" destroyed

Unable to remove file Windows Server 2003 Standard Edition-0.vmdk.lck

Unable to remove file Windows Server 2003 Standard Edition.vmdk.lck

VmiImportTask::task: Image processing task has failed with SystemError: "Internal error" VmiImportTask::task: SetState to error

object explicitly disposed: VmiImportTask::task Shutting down VMDB service... Unregistering callback... ...done object explicitly disposed: computer= Cleaning up computer's child objects Unregistring volume id=virtVol={computer=,0} Unregistring volume id=virtVol={computer={d713562da27b6af8aed5389bce6eb5f7307614cd},1} Unregistring disk id=disk= Unregistring disk id=disk= VmiImportTask::task being destroyed

0 Kudos
2 Replies
sflanders
Commander
Commander

Do you have a CD mounted on the VM? Switch the CD and Floppy options to client device or remove them entirely and try the conversion again.

Hope this helps! === If you find this information useful, please award points for "correct" or "helpful". ===
andoven
Contributor
Contributor

We started out using VMware Converter 3 standalone (the paid for version available in 2007) to do the import. We had originally used it to do some P to V conversions.

After we had problems, the decision was made to try the vCenter viclient to do the Import. We right clicked on an ESX server inside of vCenter (after installing the VMware Converter Enterprise 4.0.3 via PluginManager) and chose import. We configured all the import settings, and the import worked the first time. Maybe there was a media issue with the origianal software. But since vCenter worked, we never went back to find out. Thanks for your suggestion!

Andoven

0 Kudos