Hi there,
I couldn't find this issue in the known issue list so though i should share it:
When trying to convert a Microsoft Virtual PC 2004 image consist of a base image and a differencing disk the image could not be directly converted.
specs of the image:
Base image: Windows 2003 Server Standard Edition
Differencing disk: well.. just the differences. some applications, etc.
Basic installation, nothing else special (1 disk, 1 NIC, etc)
Possible, untested, workaround:
First merge the base and diffferencing disk using the disk wizard in Virtual PC.
Haven't tested this yet. Will do this later, when I got some spare time.
I just converted a 'normal' virtual PC image to VMWare client. This seems to work just fine!
Unfortunately VM Importer 2 does not support disks in differencing mode at this time.
I cannot get the Importer to Import a Virtual PC 2004 environment at all.
My host environment is WinXP Pro+SP2. The Virtual PC image is a 'standard' Win2K3 Server - Standard Edition.
I've tried rebooting, de-installing/re-installing the Importer, but it keeps on failing with the error "An internal error has occurred (sysimage.fault.ImageprocessingTaskFault)" .
Anybody know what is going wrong ?
I can start the Virtual PC no problem, so it's not my VPC config.
Derek :-?
Thanks for your feedback, we need some more information to diagnose your problem could you let us know the following: -
1) Are the disks in "differencing" mode?
2) Could you post here or email (vmi2-betafeedback@vmware.com) the .vmc file of the VPC image you are trying to import?
3) Also, what is the target product for your import?
I have figured out what is going wrong here - Virtual PC allows you to store the hard disk file in a separate drive/directory from the control file. What the importer is trying to do is save the VMware hard disk in the same location as the virtual PC control file - in my case there isn't enough disk space and it fails horribly.
Perhaps the importer should be more flexible in detecting the Virtual PC hard disk location, and use that directory by default instead of the location of the .VMC file.
Derek ...
If that's the case, simply move the disk image to a location with more storage space ![]()
We shouldn't really have a problem with disks being on another drive, could you post the .vmc file of your VM or email it to vmi2-betafeedback@vmware.com
Thanks,
Gautam
