- VMware Technology Network
- :
- Cloud & SDDC
- :
- vCenter
- :
- Converter Standalone Discussions
- :
- Converting Windows 2000 and resolving Inaccessible...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Converting Windows 2000 and resolving Inaccessible Boot Device
This should be considered also request for adding features.
I had an old PC with AMD CPU, VIA KT333 chipset and with Windows 2000 Professional dual/triple booting Windows 98 and kubuntu. I tried to convert Windows 2000:
1. Installed VMware vCenter Converter Standalone 4.0.1 on my new PC with kubuntu. It detected that my old PC with Windows 2000 started has no agent installed by trying to connect to TCP port 9089 and then asked to deploy agent. After waiting about 1-2 minutes deployment failed. I checked with Wireshark - no one IP packet was sent to the remote PC. Bug #1: Linux version of VMware vCenter Converter Standalone 4.0.1 doesn't try to install agent on the remote machine.
2. Downloaded VMware vCenter Converter Standalone 4.0.1 for Windows and manually installed agent. After starting the service, agent listened only on 127.0.0.1 (localhost). I had to manually edit a Other fix #1: D:\Documents and Settings\All Users\Application Data\VMware\VMware vCenter Converter Standalone\converter-agent.xml file and to change Config/plugins/ufa_agent/enableRemoteAccess to true.
3. I connected to the agent but conversion failed after 2 hours at reconfiguration stage. There was a warning that I have no sysprep tools. I downloaded them and copied them where needed but after 2 hours the conversion failed again.
4. I installed VMware vCenter Converter Standalone 4.0.1 server and client on the old PC and converted local machine. Conversion again failed. Then I found that I have to look for agent logs about the reason - Other fix # 2: had to increase manually the maximum registry size with 20 MB.
5. After another 2 hours conversion was finally successful! But the virtual Windows failed to start - it gave "Inaccessible boot device". I tried to "Configure machine" with the button, but received "unable to locate system volume". I converted both C: (boot partition) and 😧 (system partition) successfully but anyway the converter cannot find 😧 (???). Also I found http://communities.vmware.com/thread/219778 where I found "If this was a dual boot setup, then I don't think it's supported.", written by VMware vExpert 2009.
6. I found following KB article in MS site, strangely written only in Dutch: http://support.microsoft.com/kb/271965/nl Thanks to google it is readable in English here: http://translate.google.com/translate?hl=en&sl=nl&u=http://support.microsoft.com/kb/271965/nl&ei=owv...
There is a very simple solution to the problem - Bug #2 (most important): had to import following in the registry before conversion:
Windows Registry Editor Version 5.00
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"
"ClassGUID"="{4D36E967-E325-11CE-BFC1-08002BE10318}"
"Service"="disk"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"
"Service"="pciide"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"
;Add driver for Atapi (requires atapi.sys in drivers directory)
"ErrorControl"=dword:00000001
"Group"="SCSI miniport"
"Start"=dword:00000000
"Tag"=dword:00000019
"Type"=dword:00000001
"DisplayName"="Standard IDE/ESDI Hard Disk Controller"
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\ 52,00,49,00,56,00,45,00,52,00,53,00,5c,00,61,00,74,00,61,00,70,00,69,00,2e,\
00,73,00,79,00,73,00,00,00
;Add driver for intelide (requires intelide.sys in drivers directory)
"ErrorControl"=dword:00000001
"Group"="System Bus Extender"
"Start"=dword:00000000
"Tag"=dword:00000004
"Type"=dword:00000001
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\ 52,00,49,00,56,00,45,00,52,00,53,00,5c,00,69,00,6e,00,74,00,65,00,6c,00,69,\
00,64,00,65,00,2e,00,73,00,79,00,73,00,00,00
;Add driver for pciide (requires pciide.sys and pciidex.sys in drivers directory)
"ErrorControl"=dword:00000001
"Group"="System Bus Extender"
"Start"=dword:00000000
"Tag"=dword:00000003
"Type"=dword:00000001
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\ 52,00,49,00,56,00,45,00,52,00,53,00,5c,00,70,00,63,00,69,00,69,00,64,00,65,\
00,2e,00,73,00,79,00,73,00,00,00
Also had to extract following 4 files from %System Root%\Driver Cache\i386\driver.cab to %System Root%\system32\drivers:
Atapi.sys, Intelide.sys, Pciide.sys and Pciidex.sys.
After this and another 2 hours of conversion everything works perfectly on the virtual machine!!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
for Windows 2000 with servicepack 4 Converter 3.0.3 is really worth a try - easiest way often is to install it directly on the machine you want to P2V
With servicepack or earlier we have to do it manually - converter will not install on that systems
_________________________
VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook
________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks so much for that link. I used qemu-img under linux to make a vmdk from a disk I have with multiple partitions that dual boots Win98/Win2K. The Win98 worked fine. Win2K gave me the Inaccessible Boot Device. I used ERD Commander to apply those reg entries to my Win2K installation and it worked!
Thanks again!