Converter will try to preserve the RAM from the source. If you want to change it, after the conversion completes, just edit the VM settings and change the RAM size there.
Basically Converter preserves the current state of the VM's disk. So all snapshots are collapsed to the current state and any branches are disregarded.
Everybody's favourite error message, here's the workaround: - 1) On the source host, open regedit 2) Navigate to HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\SERIALCOMM 3) Export the key for backup...
See more...
Everybody's favourite error message, here's the workaround: - 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
The .vsv file in the directory may be confusing VM Importer 2, it may be a stale file from a previous suspend/resume operation. Could you try deleting/moving the .vsv file from the VM's current d...
See more...
The .vsv file in the directory may be confusing VM Importer 2, it may be a stale file from a previous suspend/resume operation. Could you try deleting/moving the .vsv file from the VM's current directory and then doing the import?
By logging in do you mean you are trying to connect to the ESX 2.5 server with the VC 2.0 client? This will not work as they are incompatible. You will need to add the ESX 2.5 to a VC 2.0 server,...
See more...
By logging in do you mean you are trying to connect to the ESX 2.5 server with the VC 2.0 client? This will not work as they are incompatible. You will need to add the ESX 2.5 to a VC 2.0 server, then when importing, select Import from remote source (I think thats what the menu option says), give the VC server's address and login credentials and you should see the VM you want to import in the VC server inventory that shows up in the VM Importer GUI. An alternative to this is, use vmkfstools -e to export your ESX 2.5 VM to some shared storage, use WS/GSX/VM Server/VM Player to create a new VM and use the disk files that you have just exported. Once this is done power on the VM to make sure everything is ok. Then use VM Importer 2.0 to import this as a standalone VM and select the ESX server as the target. Hope this helps.
VM Importer 2 requires that this service be running before and during an import. You can set this service to start manually but ensure that its running before attempting an import