Hi,
I`m trying to convert Win 2K3 SE SP2 to VM with VMware vCenter Converter Standalone (ver. 4.0.1), but the conversion process allways stops at 95% of whole operation, and there is only information: "FAILED: Unable to reconfigure the target virtual machine" Error screenshot.
The host is based on VMware ESXi 4.0.
I`ve found information, that changing SCSI controller type before starting conversion process should help, but It did not, and I`ve been trying all of SCSI type I could choose.
I have no idea, what else can I change to make it work, but maybe Logs
will be helpful for someone...
Oh, and maybe the information about partition structure is important.
There is a little partition, EISA Configuration (I don`k know what it is). Maybe it is the rason of fails?
Thanks for any clues.
One thing you have to keep in mind is that ESXi is free. You get what you pay for, I would not support a production (Needs to be up 24x7) on a Free product or a Demo. Whether VMware is the leader depends on what your preference is, I have worked with ESX and other VMware products for 4 years and love them.
On your Blue screen of the Converted Machine, one more thing you could try, is to install VMware tools on the host server before conversion. It is blue screening because drivers are not being recongized.
D
Guys,
I was trying to configure this unlucky machine, one more time. It still ends with the same failure message, but now, during the configuration process there are two new messages:
1. Warning: The source has 8 CPUs, but the target does not support the same number of virtual CPUs.
2. The memory allocated for the destination machine has been set to the maximum supported for the guest operating system by the target host.
The allocated memory is less than the source memory setting.
You can see them here: http://pokazywarka.pl/uxhot3-2/
The source machine has only one CPU with two cores.. I don't know why there is warning that the source has 8 CPUs
I neither don't understand the second message. My physical server has 8 GB RAM, but Windows 2003 32-bit can see only 4GB.
Maybe this two warnings causes my problems with migration?
Moving to the VMware Converter forum
If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points
Tom Howarth VCP / vExpert
VMware Communities User Moderator
Blog: www.planetvm.net
Contributing author on "[VMware vSphere and Virtual Infrastructure Security: Securing ESX and the Virtual Environment|http://www.amazon.co.uk/VMware-VSphere-Virtual-Infrastructure-Security/dp/0137158009/ref=sr_1_1?ie=UTF8&s=books&qid=1256146240&sr=1-1]”.
Contributing author on "[VCP VMware Certified Professional on VSphere 4 Study Guide: Exam VCP-410|http://www.amazon.co.uk/VMware-Certified-Professional-VSphere-Study/dp/0470569611]”.
I have found a solution.
Here it is:
To copy the appropriate disk controller driver from a working virtual machine with Windows 2003 installed:
1.Power on the source for the conversion. The source can be physical or virtual.
2.Power on a working virtual machine running Windows 2003.
3.Copy the LSI Logic disk controller driver file located in %systemroot%\system32\drivers\symmpi.sys to the source for the conversion.
4.Copy the VMware SCSI disk controller device driver file, if present, located in %systemroot%\system32\drivers\vmscsi.sys to the source for the conversion.
5.Click Start > Run.
6.Type regedit and press Enter.
7.Browse to and export the following registry keys:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\symmpi
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_1000&dev_0030
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\vmscsi
Note: The vmscsi service registry key may not exist if VMware Tools is not installed on the virtual machine.
8.Import the registry keys from step 6 on to the conversion source.
9.Restart the source to complete installation.
10.Perform another conversion with VMware Converter.
Guys, thanks for all your replies. Thanks them I increase my knowledge about VMware.
Hi fenioo
most of the steps you listed are not necessary - you do not need the vmscsi-driver at all for 2003.
The lsilogic driver exists in all 2003 I have seen - enable the driver in registry and make sure you use scsi0.virtualDev = "lsilogic" in the vmx file
___________________________________
VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook
Ulli Hankeln wrote:
most of the steps you listed are not necessary - you do not need the vmscsi-driver at all for 2003.
The lsilogic driver exists in all 2003 I have seen - enable the driver in registry and make sure you use scsi0.virtualDev = "lsilogic" in the vmx file
Could you explain in more details how to enable LSI logic drivers in Windows Server 2003 registry please.
VM I P2V'ed blue screens:
"a problem has been detected....
Check for viruses on your computer. Remove any newly installed hard drives"
I also cannot run VM re-configuration.
Use converter 4.3...I know it sounds odd but the older version does seem to work better for older equipment.
Brian (hotmail) wrote:
Use converter 4.3...I know it sounds odd but the older version does seem to work better for older equipment.
I am using Vmware Converter Standalone 4.3.0 build 292238.
OK, I managed to resolve the problem.
Converted VM blue screened after Windows start up: "Please remove recently addded hard drivers or controllers..."
I just copied symmpi.sys and vmscsi.sys to C:\Windows\System32\Drivers folder on the source server and ran Converter again.
I've attached these files and also registry files mentioned by @fenioo.