We are in the process of converting all of our MS VM Servers to VM ESX.
I have been trying to use the VM Importer to do the conversion but when I run it always ends with the error that is was unsuccessful and the following message:
"A virtual machine cannot be imported while it is powered on or suspended. Please shutdown the virtual machine before importing it."[/i]
The VMs in question have been shutdown, not suspended. I have even stopped the MS VM Services wondering if they still had a hook into the machine or disk files causing the Import to be unable to access it.
Any help would be appreciated.
Thanks,
--Marshall
Here is the lst few lines of the importer log file that appear to reference the issue:
\[2006-08-01 21:07:11.541 'App' 5320 info] \[foundryParser,596] LocalVirtualDiskSpec: Name=
nl-eris\c$\Virtual Machines\NL-ERIS.LICS\drive-0.vmdk
\[2006-08-01 21:07:11.541 'App' 5320 verbose] \[slaveConnection,189] Creating local connection to the co-located slave
\[2006-08-01 21:07:11.837 'Ufa-foundry' 5320 verbose] Close vmHandle called
\[2006-08-01 21:07:11.853 'App' 4500 verbose] \[localImportSource,328] The VM is suspended:
nl-eris\c$\Virtual Machines\NL-ERIS.LICS\NL-ERIS-V1.vmc
\[2006-08-01 21:07:11.853 'App' 5320 verbose] \[disposable,109] object explicitly disposed: computer=\{31dea1891cf00874203e65519b48855d816fae0}
\[2006-08-01 21:07:11.853 'App' 5320 verbose] \[disposable,45] disposable object being destroyed: computer=\{31dea1891cf00874203e65519b48855d816fae0}
\[2006-08-01 21:07:11.853 'App' 5320 verbose] \[diskSet,118] Cleaning up computer's child objects
\[2006-08-01 21:07:11.853 'App' 5320 verbose] \[diskSet,144] Unregistring disk id=disk=\{c5667447677cf3f7466eaf3d8cfa79ec6a6d8fb}
\[2006-08-01 21:07:11.962 'App' 4500 verbose] \[imageProcessingTaskImpl,564] Image processing task has succeeded...
\[08/01/06 21:07:11] Status: (VmountDisk:237) disk
nl-eris\c$\Virtual Machines\NL-ERIS.LICS\drive-0.vmdk was opened
\[08/01/06 21:07:11] Status: (VmountDisk:440) disk
nl-eris\c$\Virtual Machines\NL-ERIS.LICS\drive-0.vmdk was closed
\[2006-08-01 21:07:11.322 'App' 3336 verbose] \[imageProcessingTaskWrapper,362] Waiting for updates...
\[2006-08-01 21:07:11.337 'App' 3336 verbose] \[imageProcessingTaskWrapper,362] Waiting for updates...
\[2006-08-01 21:07:11.962 'App' 872 verbose] \[imageProcessingTaskWrapper,701] Task completed.
\[2006-08-01 21:07:12.025 'App' 956 verbose] \[disposable,109] object explicitly disposed: VmiIsImportAcceptableTask::task\{5}
\[2006-08-01 21:07:12.025 'App' 956 verbose] \[disposable,45] disposable object being destroyed: VmiIsImportAcceptableTask::task\{5}
\[2006-08-01 21:07:12.041 'App' 5320 info] \[vmImporter,279] Found UFAD log at .\vmware-ufad.log-0.log
\[2006-08-01 21:07:12.041 'App' 5320 info] \[vmImporter,302] Found VMOUNT log at C:\WINDOWS\TEMP\vmware-vmount.log
I can post the entire log if that is helpful
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?
Could you post a list of files in the directory where the VPC image is located? Also, it seems like you are importing from a network share, could you try mapping the share to a drive letter and re-running the import?
Thanks,
Gautam
Dir of the two VMs I am currently working on importing:
Directory of C:\Virtual Machines\nl-eris-v2
08/01/2006 09:28 PM
.
08/01/2006 09:28 PM
..
08/01/2006 08:48 PM 17,171,512,832 NL-ERIS-V2.vhd[/b]
08/01/2006 08:48 PM 14,728 NL-ERIS-V2.vmc[/b]
05/30/2006 12:41 PM 134,789,236 NL-ERIS-V2.vsv[/b]
3 File(s) 17,306,316,796 bytes
2 Dir(s) 132,012,635,648 bytes free
Directory of C:\Virtual Machines\nl-eris.lics
08/01/2006 09:07 PM
.
08/01/2006 09:07 PM
..
08/01/2006 08:48 PM 14,886 NL-ERIS-V1.vmc[/b]05/30/2006 12:41 PM 196,193,388 NL-ERIS-V1.vsv[/b]
08/01/2006 08:48 PM 4,489,036,288 NL-ERIS.LICS.vhd[/b] 3 File(s) 4,685,244,562 bytes
2 Dir(s) 132,012,635,648 bytes free
Yes I was using a UNC path, based on your suggesting I mapped a drive to the same location and tried that with the same results. I then tried just installing the Imported on the host for the VMs so it was importing from a local drive, that too gave me the same results.
Thanks,
--Marshall
That was it... there were vsv files that appeared to be stale from the file date. I moved these to a different folder and the import is running right now.
Thanks for your questions they got me looking in the right direction.
--Marshall
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?