Hello,
I've been trying to P2V one of PE2650 running on Windows 2000 SP4 server but VMware converter 3.03 stops and check for the file called scsiport.sys. Converter will not pass the next screen and keep asking for this partuclar file (scsiport.sys) I pointed the file to c:\winnt\system32\driver\scsiport.sys but converter complained that the file is not stable for the machine...so, it will stop from this screen...Any idea? I have other boxes with similar hardware and OS but have no problem running P2V. One thing I notice is that, after installing Converter on this box, the system asked a reboot which doesn't happen on the other similar hardware configuration box (also PE2650)
Please have a look at this
http://www.techbytes.ca/techbyte158.html
Kind Regards,
Gerrit Lehr
If you found this or other information useful, please consider awarding points for "Correct" or "Helpful".
Make sure you have Windows 2000 SP4 rollup 1 installed on this machine. Check out http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1000719&sl...
Also, when the VMware Converter agent is installed on Windows 2000 or NT based machines, a reboot is neccessary and without the agent will not function correctly. This is by design of the Windows 2000 and NT operating systems. New software requires a reboot.
Regards,
Graham
Thanks for the post. I was able getting pass the screen that complained about the scsiport.sys by replacing another scsiport.sys. However, the conversion failed @ 2%. It keeps saying that it could not take the snapshot of the physcial machine. I tried several times but the same error came up everytime. I gave up using VMware Converter and tried vConverter from http://www.vizioncore.com/vConverter.html and it converted the box without any issue. Once thing I notice was that after the conversion is done, although I configued the VM with 2 vCPU, the VM booted up and could only see one vCPU.
Hi,
FYI for the next time.
VM converter installs a snapshot service, it may not be loaded or may require a reboot.
Try restarting the converter service.
Also unload as many non-essential serivces as possible like antivirus. Anything that creates disk activity is a potential issue.
I can not comment on vconverter product but with respect to our product, converter only changes the HAL for NT4 machines as NT4 VMs can only have 1 CPU under ESX. Everything else gets downsized to 2 CPUs if they have more and 1 CPU if that is how it is setup to begin with. You should verify what the HAL reports on your newly created 1 CPU VM.